0xcbb5…c5c8
Paid $1,112.40 of the $847.69M Roundhouse has indexed across 1,331,639 wallets — 0.0001% of it.
Chains (from the recent scan): Base (377)
What it buys
Grouped by the capability each merchant's catalogue is mostly about. A merchant counts once, in one group — nothing records which of its endpoints a payment bought.
| Group | Share | Spent | Calls | Sellers |
|---|---|---|---|---|
| Not in any catalogue | 100% | $1,112.40 | 377 | 2 |
$952.30 went to wallets that publish no endpoint in any catalogue we crawl — spend we can see and cannot describe.
Services it paid
A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; for 1 of 2 the amount paid narrows the list to the ones listed at that price.
- 0xac2e…3862 · last paid 5d ago$952.30121 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x7a48…6a61 · last paid 10m ago$160.10256 calls
▸3 of 3 catalogued endpoints list a price this agent paid
- /products/resume-effect-reconciliation/verdictPrice match$0.005 listed
- /products/resume-effect-reconciliation/subscribePrice match$9.00 listed
- /products/context-crossmatch-compatibility-typing/checkPrice match$0.005 listed
ERC-8004 registration
- Declares 3 endpoints, and 3 are in a public catalogue
Card follows eips.ethereum.org/EIPS/eip-8004#registration-v1
Funds flow over time
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0xac2e…3862 | $952.30 | $0.00 | 121 | 5d ago | Graph |
| 0x7a48…6a61 | $160.10 | $0.00 | 256 | 10m ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
86% of observed volume is with a single counterparty, in all 377 observed settlements.
Recent activity
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will check what 0xcbb5…c5c8 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xcbb53f9998b9e1dee12662f79b769ad3e1edc5c8
Show the promptHide the prompt
Using Roundhouse, vet this agent for me: what is it, what has it paid for, and does its on-chain record support what its card claims? Agent: 0xcbb5…c5c8 curl -s 'https://api.roundhouseai.io/v0/agents/0xcbb53f9998b9e1dee12662f79b769ad3e1edc5c8' curl -s 'https://api.roundhouseai.io/v0/entities/0xcbb53f9998b9e1dee12662f79b769ad3e1edc5c8/settlements' Roundhouse indexes public chain data and does not vouch for any agent's claims — treat the card as a claim and the settlements as the evidence. The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Either pay over x402 (mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at https://roundhouseai.io/dashboard/connections. If you have neither, ask before going further. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.