0x482a…9370
Paid $68.78 of the $3059.45M Roundhouse has indexed across 1,397,037 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (282)
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 |
|---|---|---|---|---|
| Reference Data | 100% | $68.78 | 282 | 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.
- 0x5d51…d60d · last paid 119d ago$68.78282 calls
▸199 of 199 catalogued endpoints list a price this agent paid
- /api/x402/get_crypto_correlation_benchmarkPrice match$0.02 listed
- /api/x402/salary-benchmarkPrice match$0.02 listed
- /api/x402/cre-acquisition-diligencePrice match$3.00 listed
- /api/x402/financial-deal-readinessPrice match$3.00 listed
- /api/x402/healthcare-vendor-gpo-diligencePrice match$3.00 listed
- /api/x402/vendor-onboarding-dossierPrice match$3.00 listed
- /api/x402/litigation-enforcement-snapshotPrice match$3.00 listed
- /api/x402/irs-industry-tax-statisticsPrice match$0.50 listed
191 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 | |
|---|---|---|---|---|---|
| 0x5d51…d60d | $68.78 | $0.00 | 282 | 119d 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 282 observed settlements.
Organic volume $68.78 of $68.78 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 0x482a…9370 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x482a161b0954bfd993dc7c78e7d46c57cd849370
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: 0x482a…9370 curl -s 'https://api.roundhouseai.io/v0/agents/0x482a161b0954bfd993dc7c78e7d46c57cd849370' curl -s 'https://api.roundhouseai.io/v0/entities/0x482a161b0954bfd993dc7c78e7d46c57cd849370/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.