0x0e10…c7c3
Paid $50.58 of the $3066.17M Roundhouse has indexed across 1,400,092 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (400)
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% | $50.58 | 400 | 2 |
$34.41 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.
- 0xbcbd…820c · last paid 162d ago$34.412 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xe903…1abf · last paid 162d ago$16.17398 calls
▸1 of 200 catalogued endpoints list a price this agent paid
- /api/v1/images/image2imagePrice match$0.02 listed
- /api/v1/chat/completionsText completion$0.002 listed
- /api/v1/exa/answerText completion$0.01 listed
- /api/v1/messages$0.01 listed
- /api/v1/exa/searchWeb search$0.01 listed
- /api/v1/exa/contents$0.003 listed
- /api/v1/images/generations$0.04 listed
- /api/v1/videos/generations$0.40 listed
192 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 | |
|---|---|---|---|---|---|
| 0xbcbd…820c | $34.41 | $0.00 | 2 | 162d ago | Graph |
| 0xe903…1abf | $16.17 | $0.00 | 398 | 162d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
68% of observed volume is with a single counterparty, in all 400 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 0x0e10…c7c3 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x0e1031f3a1a8c3d8feae71b478752707ac50c7c3
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: 0x0e10…c7c3 curl -s 'https://api.roundhouseai.io/v0/agents/0x0e1031f3a1a8c3d8feae71b478752707ac50c7c3' curl -s 'https://api.roundhouseai.io/v0/entities/0x0e1031f3a1a8c3d8feae71b478752707ac50c7c3/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.