0xa4b6…3a2e
Paid $12.53 of the $3053.48M Roundhouse has indexed across 1,395,044 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (313)
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 | 80% | $10.00 | 1 | 1 |
| Reference Data | 20% | $2.53 | 312 | 1 |
$10.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.
- 0x7a23…b7f6 · last paid 93d ago$10.001 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xe73d…1114 · last paid 5h ago$2.53312 calls
▸195 of 200 catalogued endpoints list a price this agent paid
- /api/lorem-ipsumPrice match$0.001 listed
- /api/base64-hex-codecPrice match$0.001 listed
- /api/jsonpath-extractPrice match$0.001 listed
- /api/unit-convertPrice match$0.001 listed
- /api/v1/uuid-ulid-genPrice match$0.001 listed
- /api/v1/base64-hex-codecPrice match$0.001 listed
- /api/v1/uuid-generatePrice match$0.001 listed
- /api/uuid-generatePrice match$0.001 listed
192 further catalogued endpoints not listed.
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 | |
|---|---|---|---|---|---|
| 0x7a23…b7f6 | $10.00 | $0.00 | 1 | 93d ago | Graph |
| 0xe73d…1114 | $2.53 | $0.00 | 312 | 5h ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
80% of observed volume is with a single counterparty, in all 313 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 0xa4b6…3a2e has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xa4b6d209c3a129832a81d3ad8ea256c5019f3a2e
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: 0xa4b6…3a2e curl -s 'https://api.roundhouseai.io/v0/agents/0xa4b6d209c3a129832a81d3ad8ea256c5019f3a2e' curl -s 'https://api.roundhouseai.io/v0/entities/0xa4b6d209c3a129832a81d3ad8ea256c5019f3a2e/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.