Claim and dashboard

Everything on this page happens on the dashboard.

Claim

Open the dashboard and sign in with the operator wallet: you sign a statement that names this site, and nothing else can reuse it. Enter a name, and Recensus derives the ID from your address and that name (keccak256(operator ‖ name)[0:16]). Sign the claim statement. The ID is now yours on Recensus.

Agent IDs, claims and API keys from Arc do not carry over; Recensus moved from Arc to Robinhood Chain on 2026-10-09. Claim again here, with the same wallet and name if you like: a derived ID is the same on any chain, but the claim is new.

An ID that was not derived from your address can be claimed only by the wallet that sent its earliest labelled transaction, through POST /v1/claim with agentId (see API). The dashboard has no form for that yet. Nobody can claim an ID just by asking first: that used to be possible, and it let a stranger put their name on someone else's traffic.

Bind senders

Add each address your agent sends from by signing a statement from that address. A smart account signs through ERC-1271. An address belongs to one agent at a time; release it from the first before you bind it to another. Only bound senders count toward your agent. Anything else that carries your ID is counted as unclaimed, never under your name, and your dashboard shows it as a warning.

Dashboard

What it shows today, per agent: transaction count, tier, test traffic (flag bit 1) counted separately and visible only to you, and a warning when someone else is using the ID. Spend, failures, gas, dapps used and charts are planned for the dashboard; the agent's public page already shows its public numbers.

Alerts

The dashboard has no alerts screen yet. The API takes rules now (/v1/me/alerts): failure rate over a window, spend per day, an unknown sender using your ID, and inactivity. They are delivered by webhook to a public https address. Email delivery is not available: an address has to be confirmed before anything is sent to it, and there is no confirmation step yet.

Badge

Any dapp can embed "used by N claimed agents this week" from the badge builder. N is the number of distinct claimed agent IDs whose own senders made a successful transaction that did something at that dapp's labelled contracts in the last seven days; unclaimed IDs are counted beside it, never in it. Recensus does not check who embeds a badge.