0x975d…3e17
Paid $5.66 of the $3110.54M Roundhouse has indexed across 1,414,059 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (857)
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 |
|---|---|---|---|---|
| Risk & Compliance | 100% | $5.66 | 857 | 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.
- 0x2bb7…ac6d · last paid 146d ago$5.66857 calls
▸178 of 200 catalogued endpoints list a price this agent paid
- /proxy/supply-chain-finance-score-api-3c9435Price match$0.005 listed
- /proxy/transition-finance-score-api-ddb242Price match$0.005 listed
- /proxy/refinance-calculator-api-9ebfbfPrice match$0.005 listed
- /proxy/refinance-breakeven-calculator-api-bd92dcPrice match$0.005 listed
- /proxy/email-free-provider-a95057Price match$0.005 listed
- /proxy/campaign-update-score-api-2a1281Price match$0.005 listed
- /proxy/on-chain-volume-score-api-7e996bPrice match$0.01 listed
- /proxy/project-finance-score-api-fb6470$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 | |
|---|---|---|---|---|---|
| 0x2bb7…ac6d | $5.66 | $0.00 | 857 | 146d 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 857 observed settlements.
Organic volume $5.66 of $5.66 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 0x975d…3e17 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x975de0ec7ab87b7959f6a15e3efd05a38aa73e17
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: 0x975d…3e17 curl -s 'https://api.roundhouseai.io/v0/agents/0x975de0ec7ab87b7959f6a15e3efd05a38aa73e17' curl -s 'https://api.roundhouseai.io/v0/entities/0x975de0ec7ab87b7959f6a15e3efd05a38aa73e17/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.