0x3a0e…0e34
Paid $0.36 of the $3116.99M Roundhouse has indexed across 1,419,966 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (24)
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 | 100% | $0.36 | 24 | 2 |
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; no listed price matches an amount this agent paid, so nothing narrows them.
- 0x8b29…721d · last paid 5m ago$0.2412 calls
▸2 catalogued endpoints, none priced at an amount this agent paid
- /shop/x402/buy$1.99 listed
- /x402/cheap-health$0.001 listed
- 0x7284…299c · last paid 5m ago$0.1212 calls
▸3 catalogued endpoints, none priced at an amount this agent paid
- /api/dashboard/q-verdict/resource$0.02 listed
- /api/dashboard/q-verdict/resource$0.02 listed
- /api/dashboard/q-verdict/resource$0.02 listed
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x8b29…721d | $0.24 | $0.00 | 12 | 5m ago | Graph |
| 0x7284…299c | $0.12 | $0.00 | 12 | 5m ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
67% of observed volume is with a single counterparty, in all 24 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 0x3a0e…0e34 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x3a0e5f6e424b0b48ce1039cb7dc4a13adc2b0e34
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: 0x3a0e…0e34 curl -s 'https://api.roundhouseai.io/v0/agents/0x3a0e5f6e424b0b48ce1039cb7dc4a13adc2b0e34' curl -s 'https://api.roundhouseai.io/v0/entities/0x3a0e5f6e424b0b48ce1039cb7dc4a13adc2b0e34/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.