0x17c9…355c
Paid $0.02 of the $3061.41M Roundhouse has indexed across 1,398,509 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (3)
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 |
|---|---|---|---|---|
| Not in any catalogue | 91% | $0.02 | 2 | 1 |
| Reference Data | 9% | $0.002 | 1 | 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 2 of 2 the amount paid narrows the list to the ones listed at that price.
- 0xe01c…c167 · last paid 52d ago$0.022 calls
▸2 of 2 catalogued endpoints list a price this agent paid
- /api/data-purchasePrice match$0.01 listed
- /api/data-check-paidPrice match$0.01 listed
- 0xe73d…1114 · last paid 50d ago$0.0021 call
▸65 of 200 catalogued endpoints list a price this agent paid
- /api/v1/uuid-ulid-gen$0.001 listed
- /api/lorem-ipsum$0.001 listed
- /api/base64-hex-codec$0.001 listed
- /api/jsonpath-extract$0.001 listed
- /api/v1/uuid-generate$0.001 listed
- /api/unit-convert$0.001 listed
- /api/v1/base64-hex-codec$0.001 listed
- /api/uuid-generate$0.001 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 | |
|---|---|---|---|---|---|
| 0xe01c…c167 | $0.02 | $0.00 | 2 | 52d ago | Graph |
| 0xe73d…1114 | $0.002 | $0.00 | 1 | 50d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
91% of observed volume is with a single counterparty, in all 3 observed settlements.
Organic volume $0.02 of $0.02 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x17c9…355c0xe73d…1114 | Base | $0.002 | 100% | coinbase | 50d ago | 0xcef941…64ae93 |
| 0x17c9…355c0xe01c…c167 | Base | $0.01 | 100% | coinbase | 52d ago | 0xd55b3d…abb6b2 |
| 0x17c9…355c0xe01c…c167 | Base | $0.01 | 100% | coinbase | 53d ago | 0x9a93ca…48f9ba |
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 0x17c9…355c has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x17c96ee84e07174114cb00d533105b6e2e82355c
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: 0x17c9…355c curl -s 'https://api.roundhouseai.io/v0/agents/0x17c96ee84e07174114cb00d533105b6e2e82355c' curl -s 'https://api.roundhouseai.io/v0/entities/0x17c96ee84e07174114cb00d533105b6e2e82355c/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.