0x5235…d933
Paid $0.68 of the $3058.83M Roundhouse has indexed across 1,396,904 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (28)
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 | 51% | $0.35 | 8 | 1 |
| Reference Data | 49% | $0.33 | 20 | 1 |
$0.35 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 2 the amount paid narrows the list to the ones listed at that price.
- 0x66d7…057c · last paid 247d ago$0.358 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x692d…07dd · last paid 32d ago$0.3320 calls
▸10 of 10 catalogued endpoints list a price this agent paid
- /api/pricePrice match$0.01 listed
- /api/gasPrice matchGas price$0.01 listed
- /api/renderPrice matchScreenshot$0.05 listed
- /api/balancePrice matchWallet balances$0.02 listed
- /api/blockPrice match$0.01 listed
- /api/token-pricePrice match$0.02 listed
- /api/svg2pngPrice match$0.02 listed
- /api/json2excelPrice match$0.01 listed
2 further catalogued endpoints not 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 | |
|---|---|---|---|---|---|
| 0x66d7…057c | $0.35 | $0.00 | 8 | 247d ago | Graph |
| 0x692d…07dd | $0.33 | $0.00 | 20 | 32d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
51% of observed volume is with a single counterparty, in all 28 observed settlements.
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 0x5235…d933 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x52357b5344902ebadccdf738264451f70b25d933
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: 0x5235…d933 curl -s 'https://api.roundhouseai.io/v0/agents/0x52357b5344902ebadccdf738264451f70b25d933' curl -s 'https://api.roundhouseai.io/v0/entities/0x52357b5344902ebadccdf738264451f70b25d933/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.