0x2066…b865
Paid $0.32 of the $3053.48M Roundhouse has indexed across 1,395,044 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (4)
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 |
|---|---|---|---|---|
| Web & Content | 78% | $0.25 | 3 | 1 |
| Not in any catalogue | 22% | $0.07 | 1 | 1 |
$0.07 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 2 the amount paid narrows the list to the ones listed at that price.
- 0x367f…1a03 · last paid 12h ago$0.253 calls
▸20 of 169 catalogued endpoints list a price this agent paid
- /trek/api/queryPrice matchWeb search$0.05 listed
- /feeds/api/queryPrice matchWeb search$0.05 listed
- /sportsbook/api/betPrice match$0.10 listed
- /diav/api/validatePrice match$0.05 listed
- /api/agentworld/agents/ranked$0.001 listed
- /agent/translateTranslation$0.002 listed
- /tollbooth/api/readPage to markdown$0.01 listed
- /api/directory/searchWeb search$0.001 listed
161 further catalogued endpoints not listed.
- 0xbe9f…0061 · last paid 11h ago$0.071 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
One merchant publishes more endpoints than a single catalogue read returns; its list is partial.
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 | |
|---|---|---|---|---|---|
| 0x367f…1a03 | $0.25 | $0.00 | 3 | 12h ago | Graph |
| 0xbe9f…0061 | $0.07 | $0.00 | 1 | 11h ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
78% of observed volume is with a single counterparty, in all 4 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x2066…b8650xbe9f…0061 | Base | $0.07 | 70% | 0x2772…8c17 | 11h ago | 0x467395…f1b6ce |
| 0x2066…b8650x367f…1a03 | Base | $0.10 | 100% | coinbase | 12h ago | 0x3259ef…4b5a94 |
| 0x2066…b8650x367f…1a03 | Base | $0.05 | 100% | coinbase | 12h ago | 0xaa38d0…d20bdd |
| 0x2066…b8650x367f…1a03 | Base | $0.10 | 100% | coinbase | 17h ago | 0x6f0980…29a4c7 |
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 0x2066…b865 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x20667da73222867b61f2940be40baeaccd5cb865
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: 0x2066…b865 curl -s 'https://api.roundhouseai.io/v0/agents/0x20667da73222867b61f2940be40baeaccd5cb865' curl -s 'https://api.roundhouseai.io/v0/entities/0x20667da73222867b61f2940be40baeaccd5cb865/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.