0xcb7a…10a0
Paid $3.35 of the $3068.58M Roundhouse has indexed across 1,402,396 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (603)
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 |
|---|---|---|---|---|
| AI & Media | 100% | $3.35 | 534 | 1 |
Every merchant paid publishes at least one catalogued endpoint.
Services it paid
A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; for 1 of 1 the amount paid narrows the list to the ones listed at that price.
- 0xf47b…512e · last paid 5d ago$3.35534 calls
▸90 of 91 catalogued endpoints list a price this agent paid
- /api/coin-convertPrice match$0.002 listed
- /api/uuidPrice match$0.001 listed
- /api/verdictPrice match$0.001 listed
- /api/ai-extractPrice match$0.10 listed
- /api/ai-chatPrice match$0.002 listed
- /api/weatherPrice matchWeather forecast$0.002 listed
- /api/honeypotPrice match$0.001 listed
- /api/colorPrice match$0.002 listed
83 further catalogued endpoints not listed.
One merchant publishes more endpoints than a single catalogue read returns; its list is partial.
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 | |
|---|---|---|---|---|---|
| 0xf47b…512e | $3.35 | $3.06 | 545 | 5d ago | Graph |
| 0xaa34…1db3 | $0.00 | $0.76 | 14 | 1d ago | Graph |
| 0x8ec9…9d15 | $0.00 | $0.36 | 10 | 2d ago | Graph |
| 0x35fe…c030 | $0.00 | $0.24 | 8 | 2d ago | Graph |
| 0x73cc…1ea4 | $0.00 | $0.14 | 7 | 2d ago | Graph |
| 0xa1d1…1978 | $0.00 | $0.02 | 2 | 4d ago | Graph |
| 0x8237…5a46 | $0.00 | $0.02 | 16 | 7d ago | Graph |
| 0xc9c7…1670 | $0.00 | $0.001 | 1 | 7d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
81% of observed volume is with a single counterparty, in all 603 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 0xcb7a…10a0 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xcb7a729840872818568ee97b16bf42108cf810a0
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: 0xcb7a…10a0 curl -s 'https://api.roundhouseai.io/v0/agents/0xcb7a729840872818568ee97b16bf42108cf810a0' curl -s 'https://api.roundhouseai.io/v0/entities/0xcb7a729840872818568ee97b16bf42108cf810a0/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.