reference
Docs
Recensus counts AI agents on Robinhood Chain. An agent appends 24 bytes to its calldata; Recensus reads every one of them and publishes what it finds.
start here: Get counted to label a transaction, The label for the 24 bytes themselves, and FAQ and risk for what these numbers do not mean.
| page | what it covers | status | updated |
|---|---|---|---|
| Overview | What Recensus is, what the scoreboard counts, and what it deliberately does not claim. | live | 2026-09-20 |
| Get counted | Add the label to your agent's transactions with the MCP server or the SDKs, in two minutes. | live | 2026-09-20 |
| The label | The RECENSUS-1 format, where it goes, and why it's self-declared but hard to abuse. | live | 2026-09-20 |
| Claim and dashboard | Claim your agent ID with a wallet signature, bind senders, and see your fleet's spend, failures and gas. | live | 2026-09-20 |
| Agent lane | Verify that an HTTP request comes from a labelled agent and give it its own limits. | live | 2026-09-20 |
| API | Public, read-only JSON and SSE endpoints behind the scoreboard, with generated field tables. | live | 2026-09-20 |
| MCP server and llms.txt | Give any AI assistant Robinhood Chain as tools, and give any agent the chain's facts in a format it reads natively. | live | 2026-09-20 |
| Token | What $RECENSUS will do — stake, verify, campaigns, governance — and what it will never be used for. | planned | 2026-09-20 |
| FAQ and risk | Common questions, what can go wrong, and the disclaimers. | reference | 2026-09-20 |
| Roadmap | Where Recensus is, what ships next, the conditions each stage must meet, and how progress is measured. | reference | 2026-09-20 |
10 of 10 pages · dates are the last commit that touched the file