0x8e4d…d5c8
Paid $0.17 of the $834.02M Roundhouse has indexed across 1,300,437 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (4)
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 | 77% | $0.13 | 2 | 2 |
| AI & Media | 23% | $0.04 | 2 | 1 |
$0.001 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 3 the amount paid narrows the list to the ones listed at that price.
- 0x07f0…a045 · last paid 10d ago$0.131 call
▸3 catalogued endpoints, none priced at an amount this agent paid
- /api/upload$0.01 listed
- /api/upload$0.01 listed
- /pay/agent_stablestudio_dev$0.01 listed
- 0xdd5f…1ba6 · last paid 10d ago$0.042 calls
▸10 of 76 catalogued endpoints list a price this agent paid
- /api/logo/generatePrice matchText completion$0.02 listed
- /api/report/:coinPrice match$0.02 listed
- /v1/messages$0.01 listed
- /api/generate-image$0.07 listed
- /api/wp/assess$0.005 listed
- /api/searchWeb search$0.01 listed
- /api/seo/site-audit$0.05 listed
- /api/qr$0.01 listed
68 further catalogued endpoints not listed.
- 0x5c33…6505 · last paid 6d ago$0.0011 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.
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 | |
|---|---|---|---|---|---|
| 0x07f0…a045 | $0.13 | $0.00 | 1 | 10d ago | Graph |
| 0xdd5f…1ba6 | $0.04 | $0.00 | 2 | 10d ago | Graph |
| 0x5c33…6505 | $0.001 | $0.00 | 1 | 6d 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 4 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x8e4d…d5c80x5c33…6505 | Base | $0.001 | 100% | coinbase | 6d ago | 0x105144…e01092 |
| 0x8e4d…d5c80xdd5f…1ba6 | Base | $0.02 | 100% | coinbase | 10d ago | 0xe36614…1599f4 |
| 0x8e4d…d5c80xdd5f…1ba6 | Base | $0.02 | 100% | coinbase | 10d ago | 0x95466b…4f975c |
| 0x8e4d…d5c80x07f0…a045 | Base | $0.13 | 100% | coinbase | 10d ago | 0x153001…960cb2 |
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 0x8e4d…d5c8 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x8e4d69c7a06aec749d3d3d8bb5f9963c5c90d5c8
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: 0x8e4d…d5c8 curl -s 'https://api.roundhouseai.io/v0/agents/0x8e4d69c7a06aec749d3d3d8bb5f9963c5c90d5c8' curl -s 'https://api.roundhouseai.io/v0/entities/0x8e4d69c7a06aec749d3d3d8bb5f9963c5c90d5c8/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.