0xa8e1003fa3b754bc023427784f64f0708ee603bd
Paid $8.58 of the $3058.83M Roundhouse has indexed across 1,396,904 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (16)
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 |
|---|---|---|---|---|
| Company & People | 76% | $6.48 | 15 | 1 |
| Not in any catalogue | 24% | $2.10 | 1 | 1 |
$2.10 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.
- 0x9fb3…1d9a · last paid 163d ago$6.4815 calls
▸83 of 109 catalogued endpoints list a price this agent paid
- /v1/tools/web-readPrice match$0.002 listed
- /v1/tools/enrich/profilePrice match$0.005 listed
- /v1/tools/enrich/companyPrice matchCompany enrichment$0.005 listed
- /v1/tools/enrich/emailPrice matchEmail verification$0.005 listed
- /v1/tools/research/peoplePrice matchPeople search$0.01 listed
- /v1/tools/verify/emailEmail verification$0.001 listed
- /v1/tools/searchWeb search$0.001 listed
- /v1/tools/research/person$0.05 listed
101 further catalogued endpoints not listed.
- 0x8000…efeb · last paid 163d ago$2.101 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.
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x9fb3…1d9a | $6.48 | $0.00 | 15 | 163d ago | Graph |
| 0x8000…efeb | $2.10 | $0.00 | 1 | 163d 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 16 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 0xa8e1003fa3b754bc023427784f64f0708ee603bd has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xa8e1003fa3b754bc023427784f64f0708ee603bd
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: 0xa8e1003fa3b754bc023427784f64f0708ee603bd curl -s 'https://api.roundhouseai.io/v0/agents/0xa8e1003fa3b754bc023427784f64f0708ee603bd' curl -s 'https://api.roundhouseai.io/v0/entities/0xa8e1003fa3b754bc023427784f64f0708ee603bd/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.