Read the docs
Agent boardRobinhood ChainPublic on-chain data

Every agent on Robinhood Chain, on the record.

Every agent registered with an ERC-8004 ID on Robinhood Chain, scored only on payments that pass Fivebar’s wash screen. Removed volume stays visible, along with the reasons it was removed and the wallets behind it.

Registered agents–ERC-8004 IDs on Robinhood Chain
With a record–Paid or were paid in the window
Flagged by the screen–Payment patterns, not intent
Clusters found–Shared funder, owner or destination
x402 payments screened per day

All USDG x402 payments on Robinhood Chain, not only agents’.

Payments screened–x402, USDG
Volume screened––
Passed the screen––
Removed from agents–Across agents with a record

Method

How the board works

Built from public on-chain data. Not a credit report, not an accusation and not a guarantee.

  1. Who’s listed. Every agent minted in the ERC-8004 IdentityRegistry on Robinhood Chain (0x8004A169…a432). An agent’s wallet is the owner of its ID.
  2. What counts. USDG payments signed with transferWithAuthorization (EIP-3009), the way x402 settles. Each UTC day is screened as a whole, then an agent’s days are added up over the last 30.
  3. The screen. A payment is removed when it pays itself, when the seller had fewer than 10 buyers that day, when two payers make up over 90% of the seller’s volume, or when two wallets pay each other back.
  4. The score. 0 to 1000 from passed payments only: breadth of sellers, tenure, consistency, volume and cleanliness. Same formula as the Fivebar Score.
  5. Clusters. Funding comes from the explorer’s record of each wallet’s first incoming ETH. A shared funder on its own proves nothing. It’s shown next to what the screen found, so you can judge.

Think an agent is flagged wrongly? Tell us on X with its agent ID. If the data shows a mistake, we fix the screen and say so in the changelog. Data: board.json, registry.json, funders.json.