0xcaf5…26b8
Paid $0.07 of the $3059.84M Roundhouse has indexed across 1,397,496 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (3)
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 | 73% | $0.05 | 1 | 1 |
| Company & People | 27% | $0.02 | 2 | 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.
- 0x66d7…83bc · last paid 61d ago$0.051 call
▸75 of 196 catalogued endpoints list a price this agent paid
- /x402/weather-lookupPrice match$0.05 listed
- /x402/translatePrice matchTranslation$0.05 listed
- /x402/fear-greed-indexFear and greed index$0.02 listed
- /x402/mx-lookup$0.02 listed
- /x402/v2/base64-encode-url$0.02 listed
- /x402/exchange-rate$0.02 listed
- /x402/domain-age-check$0.03 listed
- /x402/uptime-check$0.02 listed
188 further catalogued endpoints not listed.
- 0xae66…e31f · last paid 61d ago$0.022 calls
▸1 of 1 catalogued endpoints list a price this agent paid
- /v1/companyPrice matchCompany enrichment$0.01 listed
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 | |
|---|---|---|---|---|---|
| 0x66d7…83bc | $0.05 | $0.00 | 1 | 61d ago | Graph |
| 0xae66…e31f | $0.02 | $0.00 | 2 | 61d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
73% of observed volume is with a single counterparty, in all 3 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xcaf5…26b80xae66…e31f | Base | $0.01 | 100% | payAI | 61d ago | 0x2c8ced…bbcf8e |
| 0xcaf5…26b80xae66…e31f | Base | $0.01 | 100% | payAI | 61d ago | 0xfcaf72…900358 |
| 0xcaf5…26b80x66d7…83bc | Base | $0.05 | 100% | coinbase | 61d ago | 0xd53b43…6851fd |
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 0xcaf5…26b8 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xcaf50de7471fb118a3ee5b4a951b594a1fa226b8
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: 0xcaf5…26b8 curl -s 'https://api.roundhouseai.io/v0/agents/0xcaf50de7471fb118a3ee5b4a951b594a1fa226b8' curl -s 'https://api.roundhouseai.io/v0/entities/0xcaf50de7471fb118a3ee5b4a951b594a1fa226b8/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.