0x0ca3…aa3e
Paid $0.60 of the $834.22M Roundhouse has indexed across 1,300,907 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (246)
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 |
|---|---|---|---|---|
| Web & Content | 88% | $0.69 | 237 | 1 |
| AI & Media | 12% | $0.09 | 9 | 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 2 of 2 the amount paid narrows the list to the ones listed at that price.
- 0xb849…eafa · last paid 3d ago$0.69237 calls
▸199 of 200 catalogued endpoints list a price this agent paid
- /api/fxPrice matchCurrency conversion$0.001 listed
- /api/domainPrice matchDomain and DNS lookup$0.002 listed
- /api/ibanPrice match$0.001 listed
- /api/email-checkPrice matchEmail verification$0.001 listed
- /api/vatPrice matchCompany registry lookup$0.002 listed
- /api/readPrice matchPage to markdown$0.002 listed
- /api/transcribePrice matchTranscription$0.01 listed
- /api/sitemapPrice match$0.002 listed
192 further catalogued endpoints not listed.
- 0xaca9…35da · last paid 17d ago$0.099 calls
▸2 of 3 catalogued endpoints list a price this agent paid
- /api/imagePrice matchImage generation$0.005 listed
- /api/auditPrice match$0.02 listed
- /api/transcribeTranscription$0.01 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 | |
|---|---|---|---|---|---|
| 0xb849…eafa | $0.69 | $0.00 | 237 | 3d ago | Graph |
| 0xaca9…35da | $0.09 | $0.00 | 9 | 17d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
88% of observed volume is with a single counterparty, in all 246 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 0x0ca3…aa3e has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x0ca3ad7154c1b2b813ce16794d5eb0a78394aa3e
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: 0x0ca3…aa3e curl -s 'https://api.roundhouseai.io/v0/agents/0x0ca3ad7154c1b2b813ce16794d5eb0a78394aa3e' curl -s 'https://api.roundhouseai.io/v0/entities/0x0ca3ad7154c1b2b813ce16794d5eb0a78394aa3e/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.