0x617d…cc9f
Paid $5.50 of the $258.78M Roundhouse has indexed across 713,781 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (1511)
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% | $0.20 | 1,000 | 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.
- 0x2880…4e5e · last paid 11d ago$0.201,000 calls
▸147 of 200 catalogued endpoints list a price this agent paid
- /feiertagePrice match$0.001 listed
- /demo/paid-samplePrice match$0.001 listed
- /predict/negative-pricePrice match$0.001 listed
- /v1/anti-cheat-scanPrice match$0.004 listed
- /stackPrice match$0.003 listed
- /product/compare$0.01 listed
- /inverter-load-check$0.002 listed
- /ensembleWeather forecast$0.005 listed
192 further catalogued endpoints not listed.
Folded from this wallet's 1,511 most recent settlements of 4,313 lifetime, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not. 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 | |
|---|---|---|---|---|---|
| 0x2880…4e5e | $0.20 | $2.00 | 1,003 | 11d ago | Graph |
| 0x7406…db83 | $0.00 | $0.51 | 508 | 20d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
81% of observed volume is with a single counterparty, in the 1511 most recent settlements scanned (its history is longer than the 2000-row scan cap).
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 0x617d…cc9f has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x617df6d675425ab4bc3a71e67d1915e026edcc9f
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: 0x617d…cc9f curl -s 'https://api.roundhouseai.io/v0/agents/0x617df6d675425ab4bc3a71e67d1915e026edcc9f' curl -s 'https://api.roundhouseai.io/v0/entities/0x617df6d675425ab4bc3a71e67d1915e026edcc9f/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.