0xc5d0…823c
Paid $0.05 of the $3220.73M Roundhouse has indexed across 1,447,963 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (16)
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 |
|---|---|---|---|---|
| Onchain Data | 58% | $0.03 | 13 | 1 |
| Web & Content | 31% | $0.01 | 2 | 1 |
| Not in any catalogue | 11% | $0.005 | 1 | 1 |
$0.005 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 2 of 3 the amount paid narrows the list to the ones listed at that price.
- 0x6293…f800 · last paid 5h ago$0.0313 calls
▸43 of 200 catalogued endpoints list a price this agent paid
- /weather/forecastPrice matchWeather forecast$0.002 listed
- /weatherPrice matchWeather forecast$0.002 listed
- /wikipediaPrice match$0.002 listed
- /hyperliquid/indicators$0.05 listed
- /newsNews search$0.01 listed
- /pack/web-researchWeb search$0.01 listed
- /pack/news-sentimentNews search$0.01 listed
- /ai/sentimentSentiment analysis$0.01 listed
192 further catalogued endpoints not listed.
- 0x6d6e…9192 · last paid 6h ago$0.012 calls
▸2 of 3 catalogued endpoints list a price this agent paid
- /searchPrice matchWeb search$0.007 listed
- /pay/agent_exa_aiPrice match$0.007 listed
- /contents$0.001 listed
- 0x0a5c…6418 · last paid 5h ago$0.0051 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
One merchant publishes more endpoints than a single catalogue read returns; its list is partial.
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x6293…f800 | $0.03 | $0.00 | 13 | 5h ago | Graph |
| 0x6d6e…9192 | $0.01 | $0.00 | 2 | 6h ago | Graph |
| 0x0a5c…6418 | $0.005 | $0.00 | 1 | 5h ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
58% of observed volume is with a single counterparty, in all 16 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 0xc5d0…823c has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xc5d00ba9de55a77315b70d2d8f73d0edc0e1823c
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: 0xc5d0…823c curl -s 'https://api.roundhouseai.io/v0/agents/0xc5d00ba9de55a77315b70d2d8f73d0edc0e1823c' curl -s 'https://api.roundhouseai.io/v0/entities/0xc5d00ba9de55a77315b70d2d8f73d0edc0e1823c/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.