0x5b4b…6801
Paid $0.26 of the $846.93M Roundhouse has indexed across 1,330,416 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (50)
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% | $0.26 | 34 | 3 |
$0.24 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 3 the amount paid narrows the list to the ones listed at that price.
- 0x4ccb…9ebf · last paid 9d ago$0.1817 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x3f5f…9757 · last paid 9d ago$0.062 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xc751…86a1 · last paid 9d ago$0.0215 calls
▸9 of 50 catalogued endpoints list a price this agent paid
- /api/v1/twitter/searchWeb search$0.005 listed
- /api/v1/web/fetchPage to markdown$0.002 listed
- /api/v1/twitter/users/:ref/tweets$0.004 listed
- /api/v1/twitter/tweets/searchWeb search$0.005 listed
- /api/v1/web/searchWeb search$0.01 listed
- /api/v1/reddit/searchWeb search$0.01 listed
- /api/v1/twitter/users/searchWeb search$0.004 listed
- /api/v1/github/searchWeb search$0.002 listed
42 further catalogued endpoints not listed.
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x4ccb…9ebf | $0.18 | $0.23 | 28 | 9d ago | Graph |
| 0x3f5f…9757 | $0.06 | $0.17 | 7 | 9d ago | Graph |
| 0xc751…86a1 | $0.02 | $0.00 | 15 | 9d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
63% of observed volume is with a single counterparty, in all 50 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 0x5b4b…6801 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x5b4bd44b6daacd6b5710fab98c6cc2f4c7696801
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: 0x5b4b…6801 curl -s 'https://api.roundhouseai.io/v0/agents/0x5b4bd44b6daacd6b5710fab98c6cc2f4c7696801' curl -s 'https://api.roundhouseai.io/v0/entities/0x5b4bd44b6daacd6b5710fab98c6cc2f4c7696801/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.