0xbbd0…8d67
Paid $50.78 of the $259.63M Roundhouse has indexed across 715,161 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (31)
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% | $50.78 | 31 | 3 |
$45.78 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; no listed price matches an amount this agent paid, so nothing narrows them.
- 0x9d11…3546 · last paid 326d ago$45.6829 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x4e9b…5edb · last paid 330d ago$5.001 call
▸7 catalogued endpoints, none priced at an amount this agent paid
- /token/gems-list$0.01 listed
- /token/leaderboard$0.01 listed
- /twitter/@canza_io$0.10 listed
- /token/gems-list$0.01 listed
- /token/leaderboard$0.01 listed
- /twitter/@canza_io$1.00 listed
- /token/address$0.10 listed
- 0x45a3…44a7 · last paid 328d ago$0.101 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
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 | |
|---|---|---|---|---|---|
| 0x9d11…3546 | $45.68 | $0.00 | 29 | 326d ago | Graph |
| 0x4e9b…5edb | $5.00 | $0.00 | 1 | 330d ago | Graph |
| 0x45a3…44a7 | $0.10 | $0.00 | 1 | 328d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
90% of observed volume is with a single counterparty, in all 31 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 0xbbd0…8d67 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xbbd0ef58c6752c17986852bab7ef034a346f8d67
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: 0xbbd0…8d67 curl -s 'https://api.roundhouseai.io/v0/agents/0xbbd0ef58c6752c17986852bab7ef034a346f8d67' curl -s 'https://api.roundhouseai.io/v0/entities/0xbbd0ef58c6752c17986852bab7ef034a346f8d67/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.