0x4229…6ec8
Paid $16.31 of the $3061.41M Roundhouse has indexed across 1,398,509 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (20)
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% | $16.30 | 19 | 3 |
| Web & Content | <1% | $0.01 | 1 | 1 |
$4.30 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 4 the amount paid narrows the list to the ones listed at that price.
- 0x955d…54cb · last paid 380d ago$12.0012 calls
- 0xb828…75fd · last paid 381d ago$4.004 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x5d6b…ea27 · last paid 381d ago$0.303 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xfbd7…5ad0 · last paid 381d ago$0.011 call
▸5 of 5 catalogued endpoints list a price this agent paid
- /api/x402/kalshi/events/specificPrice match$0.01 listed
- /api/x402/polymarket/searchPrice matchWeb search$0.01 listed
- /api/uploadPrice match$0.01 listed
- /api/x402/kalshi/markets/searchPrice matchWeb search$0.01 listed
- /api/x402/polymarket/tagsPrice match$0.01 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 | |
|---|---|---|---|---|---|
| 0x955d…54cb | $12.00 | $0.00 | 12 | 380d ago | Graph |
| 0xb828…75fd | $4.00 | $0.00 | 4 | 381d ago | Graph |
| 0x5d6b…ea27 | $0.30 | $0.00 | 3 | 381d ago | Graph |
| 0xfbd7…5ad0 | $0.01 | $0.00 | 1 | 381d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
74% of observed volume is with a single counterparty, in all 20 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 0x4229…6ec8 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x4229e06694429d43e8014bd3ed6c55bd7db16ec8
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: 0x4229…6ec8 curl -s 'https://api.roundhouseai.io/v0/agents/0x4229e06694429d43e8014bd3ed6c55bd7db16ec8' curl -s 'https://api.roundhouseai.io/v0/entities/0x4229e06694429d43e8014bd3ed6c55bd7db16ec8/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.