Whitepaper
What FACTA is, how a check works, where data goes and never goes, what it writes on chain, and what is live. Each section points to a page or a call that shows it.
1. Why FACTA
Agents and tokens on Robinhood Chain pay and trade with each other. Before an agent pays an address or buys a token, it needs facts about the other side that it does not have to take on trust: who controls an agent, whether its service answers, where its income comes from, whether a token is the one an issuer lists, how a trade was executed.
FACTA reads those facts from the chain and from the services agents declare, and publishes what it observed and against which threshold, with the reads behind each figure. It gives no verdict and no advice. A reader, a person or a program, decides.
2. Three desks, four calls
The questions, and the call that answers each
| Desk | Question | Call | What it answers |
|---|---|---|---|
Standing | Who are you dealing with? | check_agent | An identity's owner and wallets, its registration file, whether its declared services answer, its audit opinion and its charter status. |
Market | What are you trading? | check_market | A token's listing, its issuer and instrument, its market state, its pools and how organic their volume is. |
Execution | How well did you trade? | check_fill | A transaction's cost, split into pool fee, price impact, router fee and gas, against the price before it. |
Standing | Who is behind an address? | check_address | The identities on file that own an address or name it as their agent wallet, each with its role. |
Each call answers over REST, over MCP and over A2A with the same envelope, and each answer has a page on this site. The developers page shows each with an example.
3. How a check works
- Read. FACTA reads the registries and contracts listed on the trust page through public endpoints of the chain, and the registration files and services agents declare. Each read keeps its block or its time.
- Compute. Each figure comes from a public method with a version and its thresholds: the methods. A changed method is a new version, and a result names the version it used.
- Name. Each result is one term of a fixed vocabulary, with what the term means: the vocabulary. Nothing outside it is ever returned.
- Answer. The answer carries every figure with the reads behind it, and the line "Observed facts and stated thresholds. Not investment advice."
- Publish. A report is a JSON document named by the SHA-256 of its bytes. /verify hashes one in your browser, and the daily anchor puts the day's hashes on chain (section 5).
4. Where data goes, and never goes
Where data goes, and where it never goes
| Data | Where it goes | Where it never goes |
|---|---|---|
Your network address | Counted for the current minute, to apply the limits of calls without a key. | Not written to FACTA's database. |
Your wallet's address and signature, if you sign in | Two public RPC operators, which check the signature. FACTA keeps the address, with the keys you create. | No transaction, no approval, no funds: signing in asks the wallet for a signature and nothing else. |
An API key | Shown to you once, when it is made. FACTA keeps a hash of its secret. | The secret itself is never stored. |
A file you hash on /verify | Your browser, which computes its SHA-256. | Sent nowhere. |
Your visit | Two cookies, and only when you sign in: one for the attempt, one for the session. | No analytics, no tracking script, no script from another site. |
An agent's registration file and declared services | FACTA's crawler reads them, at most ten requests a minute to one host, with a User-Agent that names it. | What it reads about an agent that did not file stays on this site, never on chain. |
The privacy page says the same in full, and the crawler section says what the crawler fetches and how to make it stop.
5. What goes on chain
FACTA deploys no contract. It writes two things on chain, both from one attester address:
- Status entries in the ERC-8004 Reputation Registry, for an agent that filed for a charter, each naming its status document by its hash.
- One anchor a day: a transaction from the attester to its own address that calls no contract and moves no funds. Its data is the line
FACTA anchor 1 <day> <count> <root>, the Merkle root of the SHA-256 of every document stored that UTC day. Anyone can then show, from the chain alone, that a document existed no later than that transaction's block, and has not changed since.
An anchor names no agent and no token, and an agent that did not file gets no entry. The trust page says how to check both, and the developers page gives the two calls that read an anchor.
6. The rules FACTA keeps
- Payment buys a check, never a result. A paid check is published whatever it finds, and the one who paid cannot edit, delay or withdraw it.
- No status can be bought. No payment, token balance or vote leads to a status: no field of the data model connects one to the other.
- Every figure can be rebuilt. Each method is public, with its version and its thresholds, and each figure names the reads it rests on.
- Corrections are public. A corrected result keeps its history and says what changed: the corrections.
- The publisher is checked the same way. An agent or a token of the publisher carries the label "operated by the publisher of FACTA".
- FACTA never holds or moves anyone's funds, deploys a contract, or places, builds or routes a trade: the full list.
7. What is live, and what is next
What is live, and what comes next
| What | State | Where to see it |
|---|---|---|
The checks over REST, MCP and A2A, and the OpenAPI document | Live | |
Agents' files, their liveness, the directory and the badge | Live | |
Audits, the agent income report, clean volume and the router ranking | Live | |
The charter program, the rulebook and the roll | Live | |
Status entries on chain | Built, not yet on chain | |
The daily anchor | Built, not yet on chain | |
The code, with the scripts that rebuild each figure from the chain | Next |
Every release, with where to see it: what shipped.
8. Connect in a minute
No account and no key are needed to start. Add FACTA to an MCP client, here Claude Code:
claude mcp add --transport http facta https://factahq.xyz/mcpOr ask about an agent over REST:
curl https://factahq.xyz/v1/check/agent/437Or point an A2A client at the Agent Card: https://factahq.xyz/.well-known/agent-card.json. Every way in, step by step, with the facta command for a terminal, is under Start in a minute.