0x417d…0d58
Paid $0.01 of the $3200.11M Roundhouse has indexed across 1,437,441 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (1010)
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.01 | 10 | 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.
- 0xc59c…6235 · last paid 62d ago$0.0110 calls
▸47 catalogued endpoints, none priced at an amount this agent paid
- /v1/tools/iban-check/call$0.005 listed
- /v1/tools/pre-disbursement-guard/call$0.005 listed
- /v1/tools/balance-check/call$0.005 listed
- /v1/tools/tx-activity/call$0.005 listed
- /v1/tools/lei-check/call$0.005 listed
- /v1/tools/vat-mod97-check/call$0.005 listed
- /v1/tools/context-distill/call$0.01 listed
- /v1/tools/calculate-fx-savings/call$0.01 listed
39 further catalogued endpoints not listed.
Folded from this wallet's 1,010 most recent settlements of 1,151 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.
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 | |
|---|---|---|---|---|---|
| 0xe594…9462 | $0.00 | $0.98 | 977 | 47d ago | Graph |
| 0xefd4…404f | $0.00 | $0.11 | 22 | 46d ago | Graph |
| 0xc59c…6235 | $0.01 | $0.00 | 10 | 62d ago | Graph |
| 0x7e6b…2b1c | $0.00 | $0.005 | 1 | 46d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
89% of observed volume is with a single counterparty, in the 1010 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 0x417d…0d58 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x417da74cdc0d3babf6adc851b6e5c638574c0d58
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: 0x417d…0d58 curl -s 'https://api.roundhouseai.io/v0/agents/0x417da74cdc0d3babf6adc851b6e5c638574c0d58' curl -s 'https://api.roundhouseai.io/v0/entities/0x417da74cdc0d3babf6adc851b6e5c638574c0d58/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.