0x06c6…da0d
Paid $2.33 of the $3066.17M Roundhouse has indexed across 1,400,092 wallets — less than 0.0001% of it.
Whole-history totals from the index rollup, which can be up to 30 minutes behind.
Chains (from the recent scan): Base (233)
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 |
|---|---|---|---|---|
| Reference Data | 100% | $2.33 | 233 | 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.
- 0x548e…c5f6 · last paid 63d ago$2.33233 calls
▸132 of 132 catalogued endpoints list a price this agent paid
- /getWeatherPrice match$0.01 listed
- /getCurrencyRatePrice matchCurrency conversion$0.01 listed
- /generateFakeAddressPrice match$0.01 listed
- /generateFakePhoneNumberPrice match$0.01 listed
- /generateFakeNamePrice match$0.01 listed
- /isEmailPrice match$0.01 listed
- /alcoholSavingsCalculatorPrice match$0.01 listed
- /generateChecksumFormatPrice match$0.01 listed
124 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 | |
|---|---|---|---|---|---|
| 0x548e…c5f6 | $2.33 | $0.00 | 233 | 63d 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 233 observed settlements.
Organic volume $2.33 of $2.33 total.
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 0x06c6…da0d has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x06c60edb0c276eac21bc855c95984f82574bda0d
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: 0x06c6…da0d curl -s 'https://api.roundhouseai.io/v0/agents/0x06c60edb0c276eac21bc855c95984f82574bda0d' curl -s 'https://api.roundhouseai.io/v0/entities/0x06c60edb0c276eac21bc855c95984f82574bda0d/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.