0xb8dd…8457
Paid $0.013 of $3.26B indexed (less than 0.0001%).
Chains (from the recent scan): Base (2)
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 |
|---|---|---|---|---|
| Reference Data | 77% | $0.01 | 1 | 1 |
| Crypto Markets | 23% | $0.003 | 1 | 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.
- 0xe373…668d · last paid 3h ago$0.011 call
▸41 of 76 catalogued endpoints list a price this agent paid
- /ftse-indexPrice match$0.01 listed
- /us30y-yieldPrice match$0.01 listed
- /sol-pricePrice match$0.01 listed
- /btc-block-sizePrice match$0.01 listed
- /btc-difficultyPrice match$0.01 listed
- /btc-pricePrice match$0.01 listed
- /hangseng-index$0.05 listed
- /crypto-snapshot$0.05 listed
68 further catalogued endpoints not listed.
- 0xe903…1abf · last paid 3h ago$0.0031 call
▸18 of 200 catalogued endpoints list a price this agent paid
- /api/v1/exa/contentsPrice match$0.003 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/images/generations$0.04 listed
- /api/v1/images/image2image$0.02 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.
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0xe373…668d | $0.01 | $0.00 | 1 | 3h ago | Graph |
| 0xe903…1abf | $0.003 | $0.00 | 1 | 3h ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
77% of volume with one counterparty.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xb8dd…84570xe903…1abf | Base | $0.003 | 100% | coinbase | 3h ago | 0xbdfdb4…bbd187 |
| 0xb8dd…84570xe373…668d | Base | $0.01 | 100% | coinbase | 3h ago | 0xd7cdaf…7ee0e8 |
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 0xb8dd…8457 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xb8dda08d66dcb2d89a4fd5f89e45f1ea38d28457
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: 0xb8dd…8457 curl -s 'https://api.roundhouseai.io/v0/agents/0xb8dda08d66dcb2d89a4fd5f89e45f1ea38d28457' curl -s 'https://api.roundhouseai.io/v0/entities/0xb8dda08d66dcb2d89a4fd5f89e45f1ea38d28457/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.