0x8d0e…5e1c
Paid $46.18 of the $3067.00M Roundhouse has indexed across 1,400,982 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (64)
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% | $46.18 | 64 | 3 |
$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 2 of 3 the amount paid narrows the list to the ones listed at that price.
- 0x8785…67cc · last paid 381d ago$46.0046 calls
▸2 of 3 catalogued endpoints list a price this agent paid
- /api/presalePrice match$1.00 listed
- /api/presalePrice match$1.00 listed
- /api/balance$0.001 listed
- 0x3c72…212f · last paid 381d ago$0.1111 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x43c8…7cb4 · last paid 380d ago$0.077 calls
▸2 of 4 catalogued endpoints list a price this agent paid
- /x402/v1/airdropPrice match$0.01 listed
- /x402/airdrop/v1Price match$0.01 listed
- /x402/airdrop/v1/xxxl$100.00 listed
- /x402/airdrop/v1/xl$1.00 listed
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 | |
|---|---|---|---|---|---|
| 0x8785…67cc | $46.00 | $0.00 | 46 | 381d ago | Graph |
| 0x3c72…212f | $0.11 | $0.00 | 11 | 381d ago | Graph |
| 0x43c8…7cb4 | $0.07 | $0.00 | 7 | 380d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
100% of observed volume is with a single counterparty, in all 64 observed settlements.
Organic volume $46.18 of $46.18 total.
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 0x8d0e…5e1c has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x8d0ea9b99330e57048848a88c66f5627e9f15e1c
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: 0x8d0e…5e1c curl -s 'https://api.roundhouseai.io/v0/agents/0x8d0ea9b99330e57048848a88c66f5627e9f15e1c' curl -s 'https://api.roundhouseai.io/v0/entities/0x8d0ea9b99330e57048848a88c66f5627e9f15e1c/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.