0xcd1d…df91
Paid $0.001 of the $3116.99M Roundhouse has indexed across 1,417,718 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (1)
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 |
|---|---|---|---|---|
| Crypto Markets | 100% | $0.001 | 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 1 of 1 the amount paid narrows the list to the ones listed at that price.
- 0x7dd5…2629 · last paid 56d ago$0.0011 call
▸8 of 128 catalogued endpoints list a price this agent paid
- /api/crypto/pricePrice matchCrypto spot price$0.001 listed
- /api/crypto/trendingPrice match$0.001 listed
- /api/ens/resolvePrice match$0.001 listed
- /api/ens/reversePrice matchGeocoding$0.001 listed
- /api/tts/elevenlabs$0.02 listed
- /api/travel/flights$0.02 listed
- /api/llm/kat-coder-pro-v2.5$0.01 listed
- /api/travel/hotels$0.02 listed
120 further catalogued endpoints not listed.
One merchant publishes more endpoints than a single catalogue read returns; its list is partial.
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x7dd5…2629 | $0.001 | $0.00 | 1 | 56d 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 1 observed settlement.
Organic volume $0.001 of $0.001 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xcd1d…df910x7dd5…2629 | Base | $0.001 | 100% | coinbase | 56d ago | 0x9fd4aa…7d3ced |
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 0xcd1d…df91 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xcd1da66c413c5edc5943cf19176d106f1a2fdf91
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: 0xcd1d…df91 curl -s 'https://api.roundhouseai.io/v0/agents/0xcd1da66c413c5edc5943cf19176d106f1a2fdf91' curl -s 'https://api.roundhouseai.io/v0/entities/0xcd1da66c413c5edc5943cf19176d106f1a2fdf91/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.