0xcf9e…72e1
Paid $0.82 of the $846.65M Roundhouse has indexed across 1,329,967 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (28)
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 |
|---|---|---|---|---|
| Company & People | 88% | $0.72 | 18 | 1 |
| Web & Content | 12% | $0.10 | 10 | 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 2 the amount paid narrows the list to the ones listed at that price.
- 0xade0…89ab · last paid 5d ago$0.7218 calls
▸2 catalogued endpoints, none priced at an amount this agent paid
- /api/person/from-email$0.12 listed
- /api/company/enrichCompany enrichment$0.10 listed
- 0x325b…d430 · last paid 12d ago$0.1010 calls
▸18 of 68 catalogued endpoints list a price this agent paid
- /api/exa/searchPrice matchWeb search$0.01 listed
- /api/exa/contents$0.002 listed
- /api/firecrawl/searchWeb search$0.03 listed
- /api/apollo/people-enrichPeople search$0.05 listed
- /api/pdl/people-enrichPeople search$0.28 listed
- /api/fullenrich/people-searchPeople search$0.15 listed
- /api/clado/contacts-enrichPeople search$0.20 listed
- /api/reddit/searchWeb search$0.02 listed
60 further catalogued endpoints not listed.
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 | |
|---|---|---|---|---|---|
| 0xade0…89ab | $0.72 | $0.00 | 18 | 5d ago | Graph |
| 0x325b…d430 | $0.10 | $0.00 | 10 | 12d 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 28 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 0xcf9e…72e1 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xcf9e9eb7094bee63460f89b57b0323ed390472e1
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: 0xcf9e…72e1 curl -s 'https://api.roundhouseai.io/v0/agents/0xcf9e9eb7094bee63460f89b57b0323ed390472e1' curl -s 'https://api.roundhouseai.io/v0/entities/0xcf9e9eb7094bee63460f89b57b0323ed390472e1/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.