0x86be…222b
Paid $242.00 of the $3066.17M Roundhouse has indexed across 1,400,092 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (125)
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% | $242.00 | 125 | 2 |
$134.00 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.
- 0xa1dd…e915 · last paid 379d ago$134.0017 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x9b4d…6083 · last paid 379d ago$108.00108 calls
▸2 of 2 catalogued endpoints list a price this agent paid
- /mint?address=0x020161B0D3f33446cBc3194726B5E3898E6Ce80e&tier=10Price match$1.00 listed
- /mintPrice match$1.00 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 | |
|---|---|---|---|---|---|
| 0xa1dd…e915 | $134.00 | $0.00 | 17 | 379d ago | Graph |
| 0x9b4d…6083 | $108.00 | $0.00 | 108 | 379d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
55% of observed volume is with a single counterparty, in all 125 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 0x86be…222b has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x86beb2bd62c72be97d01ef7a0605cce46c4e222b
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: 0x86be…222b curl -s 'https://api.roundhouseai.io/v0/agents/0x86beb2bd62c72be97d01ef7a0605cce46c4e222b' curl -s 'https://api.roundhouseai.io/v0/entities/0x86beb2bd62c72be97d01ef7a0605cce46c4e222b/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.