0x1c82…8611
Paid $1.14 of the $3220.73M Roundhouse has indexed across 1,447,963 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 | 100% | $1.14 | 2 | 2 |
| Onchain Data | <1% | $0.002 | 1 | 1 |
$0.14 went to wallets that publish no endpoint in any catalogue we crawl — spend we can see and cannot describe.
Services it paid
A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; for 1 of 3 the amount paid narrows the list to the ones listed at that price.
- 0x6b7b…a4e5 · last paid 7h ago$1.001 call
▸3 catalogued endpoints, none priced at an amount this agent paid
- /x402/decode$0.005 listed
- /x402/decode$0.005 listed
- /native/evm/encode-call$0.002 listed
- 0x69dd…4cd1 · last paid 7h ago$0.141 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x6293…f800 · last paid 7h ago$0.0021 call
▸43 of 200 catalogued endpoints list a price this agent paid
- /weather/forecastPrice matchWeather forecast$0.002 listed
- /weatherPrice matchWeather forecast$0.002 listed
- /wikipediaPrice match$0.002 listed
- /hyperliquid/indicators$0.05 listed
- /newsNews search$0.01 listed
- /pack/web-researchWeb search$0.01 listed
- /pack/news-sentimentNews search$0.01 listed
- /ai/sentimentSentiment analysis$0.01 listed
192 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 | |
|---|---|---|---|---|---|
| 0x6b7b…a4e5 | $1.00 | $0.00 | 1 | 7h ago | Graph |
| 0x69dd…4cd1 | $0.14 | $0.00 | 1 | 7h ago | Graph |
| 0x6293…f800 | $0.002 | $0.00 | 1 | 7h ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
88% of observed volume is with a single counterparty, in all 3 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x1c82…86110x69dd…4cd1 | Base | $0.14 | 100% | coinbase | 7h ago | 0xa3a546…f703e4 |
| 0x1c82…86110x6b7b…a4e5 | Base | $1.00 | 100% | coinbase | 7h ago | 0x19cb00…a0ab4a |
| 0x1c82…86110x6293…f800 | Base | $0.002 | 100% | coinbase | 7h ago | 0xa1a81a…c87c9e |
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 0x1c82…8611 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x1c82799b1f513c9b8e443331bd4c228abcf08611
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: 0x1c82…8611 curl -s 'https://api.roundhouseai.io/v0/agents/0x1c82799b1f513c9b8e443331bd4c228abcf08611' curl -s 'https://api.roundhouseai.io/v0/entities/0x1c82799b1f513c9b8e443331bd4c228abcf08611/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.