What shipped
Every release of FACTA, newest first, each with where to see it for yourself: a page, a call, or a document by its hash. Follow it in a feed reader: RSS.
21 November 2026: Start in a minute: every command with a Copy button, and the facta command to download
- The developers page now opens with three ways in: FACTA in an AI agent over MCP, the facta command in a terminal, and a plain HTTP request. Each command has a Copy button.
- The facta command is served by this site at /facta.mjs, one file for Node.js 22 or later, with its size and SHA-256 on the developers page so a download can be checked before it runs.
- The bar's Check button puts the cursor in the check field on the home page, and leaves the address as it was.
See it: Start in a minute, The facta command.
21 November 2026: Menus in the bar, and every page at the foot of every page
- Each section of the bar opens a menu of its pages, in columns, each with a line on what it holds: the square beside the section's name opens it, and so does pointing at it.
- The foot of every page lists every page, by section.
- The headlines are set lighter and larger.
- The home page is laid out anew: a tile for each count, a card for each kind of check, a row for each of the four steps, and two columns, for builders and for agents that pay or trade.
See it: Any page, The developers page.
21 November 2026: The counts say when they were counted
- The counts of identities by liveness term are made at the end of each full pass of the crawler, and of each run of the liveness sweep, and can be older than the newest read the home page names. GET /v1/stats now gives countedAt, and the home page says "Counted" with that time under the counts.
- The terms of the identities checked since are on their own pages and in the directory.
See it: The counts, The directory.
21 November 2026: The whitepaper
- One page, in eight numbered sections: why FACTA, the calls and the questions they answer, how a check works, where data goes and never goes, what goes on chain, the rules FACTA keeps, what is live and what is next, and how to connect in a minute.
- Each section links the page or the call that shows what it says. The footer of every page links it.
See it: The whitepaper.
21 November 2026: Every published document, anchored on chain once a day
- Once a day the attester sends one transaction to its own address. It calls no contract and moves no funds: its data is one line, "FACTA anchor 1 <day> <count> <root>", the Merkle root of the SHA-256 of every document FACTA stored that UTC day.
- GET /v1/anchors/{day} lists the day's hashes with the line and its transaction; GET /v1/anchors/hash/{hash} gives one document's steps to the root. Both are in the OpenAPI document.
- The server stores an anchor only after it has read the transaction on chain and rebuilt the root from its own records. A day is anchored after it ends; a day with no document has none, and an anchor names no agent and no token.
See it: Checking a document against the chain, What FACTA writes.
21 November 2026: Agents can ask FACTA over A2A
- An Agent Card at /.well-known/agent-card.json, and an A2A server at /a2a: version 1.0, and 0.3 for a client that sends no version.
- Its skills are the checks: check_agent, check_market, check_address, and check_fill where it is open. Each answer is the same text and envelope as over MCP and REST, counted against the same limits.
See it: The Agent Card, Over A2A.
21 November 2026: The crawler reads faster, under the same limits
- The sweep that reads registration files and the one that asks declared services each take a step as often as every 100 seconds, where it was every four minutes at most, and up to 720 steps a day.
- Where one host holds the services of many agents, a step asks two of them where it asked one: an agent is asked when each of its hosts has room for one request per service.
- Unchanged: at most ten requests a minute to one host, and each file and each service read about once a week.
See it: How liveness is checked, How files are read, The crawler.
21 November 2026: Look up an address, check FACTA yourself, and this changelog
- An address answers too: the identities on file that own it or name it as their agent wallet, over REST, over MCP as check_address, and on its own page, for a caller that holds an address and not an agent ID.
- The developers page shows how an agent asks before it pays an address.
- A page that lists what FACTA never does, what it reads and writes on chain, and how to check each without FACTA, with a contact for reporting a problem.
- This changelog, with its feed.
See it: Look up an address, Before an agent pays, Check FACTA yourself, The feed.
21 November 2026: Verify a document, compare two agents, follow one subject
- A page that fetches a published document and hashes it in the reader’s browser, or hashes a file that is sent nowhere, and says whether it is the one its hash names.
- Two identities side by side, line by line, ranking neither.
- The notices of one agent or one token as an RSS feed, linked from its page.
- An OpenAPI 3.1 document of the public read calls.
- The domain is signed with DNSSEC.
See it: Verify, Compare, Agent 437’s notices as RSS, OpenAPI.
20 November 2026: The directory, the badge and the charter program
- A directory of the identities whose declared service answered as itself at the last probe, a page at a time, in ID order.
- A badge any builder can show in a README: FACTA’s words for an agent, linked to its file.
- A page for operators: what filing for a charter gives, what it asks and how to file, with a signature and no transaction.
- The site answers over HTTPS only, with TLS 1.2 or later, and its domain publishes a DMARC policy.
See it: The directory, The badge, File for a charter.
20 November 2026: The charter, Breach and factsheets
- An agent’s operator files for a charter; seven published rules are checked every day, and the status, with what each rule found, is on the agent’s page and on the roll.
- Notices of a status change, a failing rule, a broken pledge or a changed creator fee recipient.
- Breach: an operator invites anyone to attack its agent’s declared endpoints and wallets, for a prize it holds in its own wallet; FACTA checks each proof and payout from the chain, and never holds a prize.
- Factsheets of the vaults a filed agent links.
See it: The rulebook, The roll, The notices, The methods.
20 November 2026: Reports, audits and execution costs
- Published reports, each a document named by the SHA-256 of its bytes: agent income, clean volume of pools, and a weekly ranking of the routers’ all-in costs.
- Audit reports of agents’ income: who paid them, where the money went, and the opinion the published thresholds give.
- A pool’s daily check of its trading, and a check of how one transaction’s swaps were executed.
See it: The reports, The router ranking, revision 2, by its hash, The developers page.
20 November 2026: Its own domain, a contact and a new look
- The site moved to its own domain, with a public contact address.
- With the contact public, the crawler began to read the registration files owners set and to ask the services they declare.
- A new design for every page.
See it: The crawler, The home page.
17 November 2026: The two checks open
- check_agent: who are you dealing with. The file of every ERC-8004 identity on Robinhood Chain, read from the chain.
- check_market: what are you trading. Any address’s listing term, and for a listed stock token its instrument, multiplier, price feed, market state and pools.
- Both over REST and over MCP, with the same answer and the same limits, and free keys for higher limits.
See it: The agents, The instruments, Developers.