0x3428…29b3
Paid $0.003 of the $3066.17M Roundhouse has indexed across 1,400,092 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (51)
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 |
|---|---|---|---|---|
| Crypto Markets | 100% | $0.003 | 3 | 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.
- 0xf47b…512e · last paid 12d ago$0.0033 calls
▸14 of 93 catalogued endpoints list a price this agent paid
- /api/uuidPrice match$0.001 listed
- /api/verdictPrice match$0.001 listed
- /api/honeypotPrice match$0.001 listed
- /api/coin-convert$0.002 listed
- /api/ai-chat$0.002 listed
- /api/ai-extract$0.10 listed
- /api/weatherWeather forecast$0.002 listed
- /api/base64$0.002 listed
85 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 | |
|---|---|---|---|---|---|
| 0x35fe…c030 | $0.00 | $0.52 | 9 | 1d ago | Graph |
| 0x8ec9…9d15 | $0.00 | $0.23 | 7 | 2d ago | Graph |
| 0xaa34…1db3 | $0.00 | $0.23 | 7 | 1d ago | Graph |
| 0x73cc…1ea4 | $0.00 | $0.22 | 6 | 2d ago | Graph |
| 0xa1d1…1978 | $0.00 | $0.02 | 2 | 4d ago | Graph |
| 0x8237…5a46 | $0.00 | $0.02 | 16 | 6d ago | Graph |
| 0xf47b…512e | $0.003 | $0.00 | 3 | 12d ago | Graph |
| 0xc9c7…1670 | $0.00 | $0.001 | 1 | 7d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
No concentration or self-dealing patterns detected in all 51 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 0x3428…29b3 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x3428e33aac2677c519036280257fb090062229b3
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: 0x3428…29b3 curl -s 'https://api.roundhouseai.io/v0/agents/0x3428e33aac2677c519036280257fb090062229b3' curl -s 'https://api.roundhouseai.io/v0/entities/0x3428e33aac2677c519036280257fb090062229b3/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.