0xdeac…2357
Paid $3.00 of the $3066.54M Roundhouse has indexed across 1,400,689 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (3)
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% | $3.00 | 3 | 2 |
$3.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.
- 0xcce3…4139 · last paid 445d ago$2.002 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x10ad…1bda · last paid 440d ago$1.001 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
ERC-8004 registration
- Declares 4 endpoints, none of them in any catalogue we crawl
Card follows eips.ethereum.org/EIPS/eip-8004#registration-v1
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 | |
|---|---|---|---|---|---|
| 0xcce3…4139 | $2.00 | $0.00 | 2 | 445d ago | Graph |
| 0x10ad…1bda | $1.00 | $0.00 | 1 | 440d 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 3 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xdeac…23570x10ad…1bda | Base | $1.00 | 70% | 0x4337…7a5d | 440d ago | 0xa4afe5…094d59 |
| 0xdeac…23570xcce3…4139 | Base | $1.00 | 70% | 0x4337…5393 | 445d ago | 0x21ef91…4cc961 |
| 0xdeac…23570xcce3…4139 | Base | $1.00 | 70% | 0x4337…9f26 | 445d ago | 0x877cf3…b6a567 |
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 0xdeac…2357 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xdeacde6ec27fd0cd972c1232c4f0d4171dda2357
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: 0xdeac…2357 curl -s 'https://api.roundhouseai.io/v0/agents/0xdeacde6ec27fd0cd972c1232c4f0d4171dda2357' curl -s 'https://api.roundhouseai.io/v0/entities/0xdeacde6ec27fd0cd972c1232c4f0d4171dda2357/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.