0xd38a…eb0a
Paid $2.30 of the $3060.46M Roundhouse has indexed across 1,398,118 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (488)
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% | $2.30 | 488 | 2 |
Every merchant paid publishes at least one catalogued endpoint.
Services it paid
A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; for 2 of 2 the amount paid narrows the list to the ones listed at that price.
- 0xa09a…6030 · last paid 20d ago$2.26440 calls
▸1 of 1 catalogued endpoints list a price this agent paid
- /v1/mdPrice match$0.005 listed
- 0x52e2…f3ea · last paid 20d ago$0.0548 calls
▸6 of 98 catalogued endpoints list a price this agent paid
- /api/chain/block-numberPrice match$0.001 listed
- /api/chain/block-numberPrice match$0.001 listed
- /api/chain/erc20-balance$0.003 listed
- /deepstate/v1/book/:book$0.005 listed
- /deepstate/v1/candles/:bookCrypto price history$0.005 listed
- /deepstate/v1/stats/:book$0.005 listed
- /api/chain/live-balance$0.003 listed
- /api/chain/erc20-transfers$0.005 listed
90 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 | |
|---|---|---|---|---|---|
| 0xa09a…6030 | $2.26 | $0.00 | 440 | 20d ago | Graph |
| 0x52e2…f3ea | $0.05 | $0.00 | 48 | 20d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
98% of observed volume is with a single counterparty, in all 488 observed settlements.
Organic volume $2.30 of $2.30 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 0xd38a…eb0a has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xd38a5307ca677b2d0cd766d400d48e3f2984eb0a
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: 0xd38a…eb0a curl -s 'https://api.roundhouseai.io/v0/agents/0xd38a5307ca677b2d0cd766d400d48e3f2984eb0a' curl -s 'https://api.roundhouseai.io/v0/entities/0xd38a5307ca677b2d0cd766d400d48e3f2984eb0a/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.