0x28b2…df8e
Paid $5.68 of the $3059.45M Roundhouse has indexed across 1,397,282 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (194)
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 |
|---|---|---|---|---|
| Web & Content | 65% | $3.68 | 191 | 1 |
| Not in any catalogue | 35% | $2.00 | 3 | 2 |
$0.002 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 2 of 3 the amount paid narrows the list to the ones listed at that price.
- 0x63ae…cddc · last paid 5d ago$3.68191 calls
▸14 of 15 catalogued endpoints list a price this agent paid
- /api/v1/readPrice matchPage to markdown$0.002 listed
- /api/v2/datasetPrice match$0.35 listed
- /api/v1/read/jsPrice match$0.005 listed
- /api/v2/signal/entity-formations/latestPrice match$0.005 listed
- /api/v2/signal/film-incentives/latestPrice match$0.005 listed
- /api/v2/signal/ai-news/latestPrice match$0.005 listed
- /api/v2/signal/studio-jobs/latestPrice match$0.005 listed
- /api/v2/readPrice matchPage to markdown$0.002 listed
7 further catalogued endpoints not listed.
- 0x6797…e3a2 · last paid 142d ago$2.002 calls
▸1 of 1 catalogued endpoints list a price this agent paid
- /runPrice match$1.00 listed
- 0xcccc…9eb6 · last paid 138d ago$0.0021 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
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 | |
|---|---|---|---|---|---|
| 0x63ae…cddc | $3.68 | $0.00 | 191 | 5d ago | Graph |
| MiroShark | $2.00 | $0.00 | 2 | 142d ago | Graph |
| 0xcccc…9eb6 | $0.002 | $0.00 | 1 | 138d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
65% of observed volume is with a single counterparty, in all 194 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 0x28b2…df8e has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x28b20ad2570f2cce9976577b68ecdd13f084df8e
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: 0x28b2…df8e curl -s 'https://api.roundhouseai.io/v0/agents/0x28b20ad2570f2cce9976577b68ecdd13f084df8e' curl -s 'https://api.roundhouseai.io/v0/entities/0x28b20ad2570f2cce9976577b68ecdd13f084df8e/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.