0xe305…f3f6
Paid $66,813.99 of the $3061.41M Roundhouse has indexed across 1,398,667 wallets — 0.0022% of it.
Chains (from the recent scan): Ethereum (1) · Base (2)
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% | $66,813.99 | 2 | 1 |
$66,813.99 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.
- 0xdc56…78e2 · last paid 125d ago$66,813.992 calls
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 | |
|---|---|---|---|---|---|
| 0xdc56…78e2 | $66,813.99 | $0.00 | 2 | 125d ago | Graph |
| 0x1f16…f697 | $0.00 | $46,125.79 | 1 | 125d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
59% of observed volume is with a single counterparty, in all 3 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xe305…f3f60xdc56…78e2 | Ethereum | $20,688.21 | 70% | 0x8f85…0f92 | 125d ago | 0xc885e2…e98ade |
| 0xe305…f3f60xdc56…78e2 | Base | $46,125.78 | 70% | 0x8f85…0f92 | 125d ago | 0x3af685…ab0146 |
| 0x1f16…f6970xe305…f3f6 | Base | $46,125.79 | 70% | 0xa923…c9ac | 125d ago | 0xdeb26c…27ac34 |
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 0xe305…f3f6 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xe30510d6314bae8b1df1102fd67ef57b2419f3f6
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: 0xe305…f3f6 curl -s 'https://api.roundhouseai.io/v0/agents/0xe30510d6314bae8b1df1102fd67ef57b2419f3f6' curl -s 'https://api.roundhouseai.io/v0/entities/0xe30510d6314bae8b1df1102fd67ef57b2419f3f6/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.