0xe3f0…8ed8
Paid $567,273.00 of the $3210.96M Roundhouse has indexed across 1,442,756 wallets — 0.02% of it.
Chains (from the recent scan): Ethereum (4)
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% | $567,273.00 | 4 | 2 |
$567,273.00 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; no listed price matches an amount this agent paid, so nothing narrows them.
- 0xfd78…d002 · last paid 15d ago$467,273.003 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x5c7b…35c5 · last paid 15d ago$100,000.001 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0xfd78…d002 | $467,273.00 | $0.00 | 3 | 15d ago | Graph |
| 0x5c7b…35c5 | $100,000.00 | $0.00 | 1 | 15d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
82% of observed volume is with a single counterparty, in all 4 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xe3f0…8ed80xfd78…d002 | Ethereum | $267,273.00 | 70% | 0xe748…9a11 | 15d ago | 0x479173…fce7a4 |
| 0xe3f0…8ed80xfd78…d002 | Ethereum | $100,000.00 | 70% | 0xe748…9a11 | 15d ago | 0x68995a…3a8914 |
| 0xe3f0…8ed80xfd78…d002 | Ethereum | $100,000.00 | 70% | 0xe748…9a11 | 15d ago | 0xa7195e…21cb34 |
| 0xe3f0…8ed80x5c7b…35c5 | Ethereum | $100,000.00 | 70% | 0x07ae…0e67 | 15d ago | 0x33f477…5ebad5 |
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 0xe3f0…8ed8 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xe3f0037e3c7f9cdea8fcbe76ef3cbcf33cad8ed8
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: 0xe3f0…8ed8 curl -s 'https://api.roundhouseai.io/v0/agents/0xe3f0037e3c7f9cdea8fcbe76ef3cbcf33cad8ed8' curl -s 'https://api.roundhouseai.io/v0/entities/0xe3f0037e3c7f9cdea8fcbe76ef3cbcf33cad8ed8/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.