0x7cb2…da6e
Paid $0.38 of the $3235.41M Roundhouse has indexed across 1,454,003 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 (38)
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 |
|---|---|---|---|---|
| Onchain Data | 97% | $0.37 | 37 | 1 |
| Not in any catalogue | 3% | $0.01 | 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.
- 0x6ff0…d474 · last paid 39m ago$0.3737 calls
▸7 of 7 catalogued endpoints list a price this agent paid
- /api/v1/tokenPrice matchToken metadata$0.01 listed
- /api/v1/blocklistPrice match$0.01 listed
- /api/v1/signaturePrice match$0.01 listed
- /api/v1/scanPrice match$0.01 listed
- /api/v1/payeePrice match$0.01 listed
- /api/v1/outcomesPrice match$0.01 listed
- /api/v1/launchPrice match$0.01 listed
- 0x9636…c397 · last paid 1h ago$0.011 call
▸2 of 2 catalogued endpoints list a price this agent paid
- /recommendPrice match$0.01 listed
- /recommendPrice match$0.01 listed
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 | |
|---|---|---|---|---|---|
| 0x6ff0…d474 | $0.37 | $0.00 | 37 | 39m ago | Graph |
| 0x9636…c397 | $0.01 | $0.00 | 1 | 1h ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
97% of observed volume is with a single counterparty, in all 38 observed settlements.
Organic volume $0.38 of $0.38 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 0x7cb2…da6e has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x7cb21a14f37ecf389623fbdc3394a96b6263da6e
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: 0x7cb2…da6e curl -s 'https://api.roundhouseai.io/v0/agents/0x7cb21a14f37ecf389623fbdc3394a96b6263da6e' curl -s 'https://api.roundhouseai.io/v0/entities/0x7cb21a14f37ecf389623fbdc3394a96b6263da6e/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.