0x5b95…1a96
Paid $30.00 of the $3058.83M Roundhouse has indexed across 1,396,716 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (2)
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 |
|---|---|---|---|---|
| Web & Content | 100% | $30.00 | 2 | 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; no listed price matches an amount this agent paid, so nothing narrows them.
- 0xec84…de28 · last paid 19d ago$30.002 calls
▸200 catalogued endpoints, none priced at an amount this agent paid
- /api/v1/micro/passage-hash-validation$0.004 listed
- /api/v1/micro/x402-challenge-sanity$0.0035 listed
- /api/v1/micro/source-coverage-drift$0.04 listed
- /api/v1/micro/evidence-budget-allocation$0.03 listed
- /api/v1/micro/digital-twin-config-diff$0.02 listed
- /api/v1/micro/tool-argument-validation$0.0045 listed
- /api/v1/micro/spatial-adjacency-check$0.03 listed
- /api/v1/micro/extraction-consistency$0.05 listed
192 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 | |
|---|---|---|---|---|---|
| 0xec84…de28 | $30.00 | $0.00 | 2 | 19d 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 2 observed settlements.
Organic volume $30.00 of $30.00 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x5b95…1a960xec84…de28 | Base | $10.00 | 100% | coinbase | 19d ago | 0x07ac8e…b9b397 |
| 0x5b95…1a960xec84…de28 | Base | $20.00 | 100% | coinbase | 44d ago | 0xa65221…ba0601 |
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 0x5b95…1a96 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x5b953a66eb0826c13ca2af80e0c36557cc6a1a96
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: 0x5b95…1a96 curl -s 'https://api.roundhouseai.io/v0/agents/0x5b953a66eb0826c13ca2af80e0c36557cc6a1a96' curl -s 'https://api.roundhouseai.io/v0/entities/0x5b953a66eb0826c13ca2af80e0c36557cc6a1a96/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.