0xac35…cdb7
Paid $0.45 of the $258.70M Roundhouse has indexed across 713,651 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (334)
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% | $0.45 | 334 | 2 |
$0.11 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.
- 0xe903…1abf · last paid 109d ago$0.34331 calls
▸84 of 200 catalogued endpoints list a price this agent paid
- /api/v1/chat/completionsText completion$0.002 listed
- /api/v1/messages$0.01 listed
- /api/v1/exa/answerText completion$0.01 listed
- /api/v1/exa/searchWeb search$0.01 listed
- /api/v1/exa/contents$0.003 listed
- /api/v1/images/generations$0.04 listed
- /api/v1/searchWeb search$0.26 listed
- /api/v1/stocks/us/price/AAPL$0.002 listed
192 further catalogued endpoints not listed.
- 0x1b09…5e99 · last paid 196d ago$0.113 calls
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 | |
|---|---|---|---|---|---|
| 0xe903…1abf | $0.34 | $0.00 | 331 | 109d ago | Graph |
| 0x1b09…5e99 | $0.11 | $0.00 | 3 | 196d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
76% of observed volume is with a single counterparty, in all 334 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 0xac35…cdb7 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xac35871231ffec8d5b401d9239acfdaf9088cdb7
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: 0xac35…cdb7 curl -s 'https://api.roundhouseai.io/v0/agents/0xac35871231ffec8d5b401d9239acfdaf9088cdb7' curl -s 'https://api.roundhouseai.io/v0/entities/0xac35871231ffec8d5b401d9239acfdaf9088cdb7/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.