Skip to content
liveclaimed agents · last 24 hours

0

no change vs yesterday

operators
0
agent txs 24h
0
usdg moved 24h
$0.00
top framework
—
unclaimed ids
0

Agents label their transactions; Recensus counts them.

the label · RECENSUS-1

Twenty-four bytes on the end of the calldata.

byte 024 bytes total · end of calldata
  • works with any wallet
  • costs ~400 gas
  • read by tail, no ABI

magic 0x50554C53 · always the last four bytes · RECENSUS-1 spec

adoption · 7 days

Who is building agents here.

all frameworks →
  • 0x0001

    Recensus MCP

    0agents

  • 0x0003

    Recensus SDK (Python)

    0agents

  • 0x0002

    Recensus SDK (TypeScript)

    0agents

  • 0x0010

    Trading runner (external adopter)

    0agents

  • 0x0000

    Unknown / custom

    0agents

  • unclaimed

    Nobody has claimed these IDs

    0ids

every code in the registry · a code with no agents is shown as zero, not hidden

live

Every labelled transaction, as it lands.

the whole feed →

No labelled transactions yet.

The feed fills the moment an agent sends one. Be the first.

integrate

Get counted in two minutes.

$ npx -y @recensus/mcp

{
  "mcpServers": {
    "recensus": {
      "command": "npx",
      "args": ["-y", "@recensus/mcp"],
      "env": {
        "RPC_HTTP": "https://rpc.mainnet.chain.robinhood.com",
        "PRIVATE_KEY": "0x...",
        "AGENT_NAME": "my-assistant",
        "AUTONOMOUS": "false",
        "SPEND_LIMIT_USD_PER_DAY": "50"
      }
    }
  }
}
what it does
Gives your assistant the chain as tools, and labels every transaction it sends.
what it never does
No keys leave your machine. Recensus holds no funds and signs nothing.
where the label goes
Twenty-four bytes on the end of the calldata. The call itself is unchanged.
afterwards
Claim your ID to attribute those transactions to you and see your own dashboard.

verify

Check any agent ID against the chain.

Claimed or not, which senders are bound to it, what tier it holds, when it was last seen. The same answer the agent-lane middleware gets.

roadmap

exit conditions, and what is not planned →
  1. Stage 0·live·Standard and scoreboard
  2. Stage 1·in progress·Operators and apps
  3. Stage 2·planned·$RECENSUS and verified labels
  4. Stage 3·planned·Ecosystem
  5. Stage 4·planned·Sustain

the token

RCNS is what an agent will stake behind its ID to make its label verified, what sponsors will fund campaigns with, and what votes on the standard. Nothing on Recensus is paid for in it — fees, where they exist, are in USDG — and it is not required to be counted, to use the API, the SDKs or the dashboard. Staking goes live when the contract is deployed and audited. Until then the token exists and does nothing else, and we say so.

contract launches soon · token page