0xff7d…38dd
Paid $50.00 of the $3214.08M Roundhouse has indexed across 1,444,054 wallets — less than 0.0001% of it.
Chains (from the recent scan): Ethereum (1)
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% | $50.00 | 1 | 1 |
$50.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.
- 0xe283…4a70 · last paid 135d ago$50.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 | |
|---|---|---|---|---|---|
| 0xe283…4a70 | $50.00 | $0.00 | 1 | 135d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 1 observed settlement.
Organic volume $50.00 of $50.00 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xff7d…38dd0xe283…4a70 | Ethereum | $50.00 | 70% | 0xbb67…9bc4 | 135d ago | 0xb18d5c…7b1e27 |
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 0xff7d…38dd has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xff7d102d48df7e0846b0621f317066b5e1ce38dd
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: 0xff7d…38dd curl -s 'https://api.roundhouseai.io/v0/agents/0xff7d102d48df7e0846b0621f317066b5e1ce38dd' curl -s 'https://api.roundhouseai.io/v0/entities/0xff7d102d48df7e0846b0621f317066b5e1ce38dd/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.