0x5ba7…d3b1
Paid $2.72 of the $3060.21M Roundhouse has indexed across 1,397,618 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (246)
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 |
|---|---|---|---|---|
| Crypto Markets | 100% | $2.72 | 246 | 1 |
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 1 of 1 the amount paid narrows the list to the ones listed at that price.
- 0xdfd0…7a45 · last paid 4h ago$2.72246 calls
▸200 of 200 catalogued endpoints list a price this agent paid
- /v1/predictiondata/marketsPrice match$0.005 listed
- /v1/cryptodata/on-chain/exchange-flows/spike-alertsPrice match$0.01 listed
- /v1/cryptodata/indicators/catalogPrice match$0.01 listed
- /v1/cryptodata/hyperliquid/copy-signalsPrice match$0.01 listed
- /v1/cryptodata/event/calendarPrice match$0.008 listed
- /v1/cryptodata/sentiment/macroPrice match$0.01 listed
- /v1/cryptodata/liquidity/depthPrice match$0.01 listed
- /v1/cryptodata/indicators/heatmapPrice match$0.01 listed
192 further catalogued endpoints not listed.
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 | |
|---|---|---|---|---|---|
| 0xdfd0…7a45 | $2.72 | $0.00 | 246 | 4h 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; all observed volume is with one counterparty, in all 246 observed settlements.
Organic volume $2.72 of $2.72 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 0x5ba7…d3b1 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x5ba787f5a649b4cf2d409bde2010d8b54830d3b1
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: 0x5ba7…d3b1 curl -s 'https://api.roundhouseai.io/v0/agents/0x5ba787f5a649b4cf2d409bde2010d8b54830d3b1' curl -s 'https://api.roundhouseai.io/v0/entities/0x5ba787f5a649b4cf2d409bde2010d8b54830d3b1/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.