0x94d6…f3c0
Paid $854.35 of the $258.65M Roundhouse has indexed across 713,540 wallets — 0.0003% 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% | $854.35 | 3 | 2 |
$854.35 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.
- 0xedfe…6675 · last paid 37d ago$613.432 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x07f3…bbb5 · last paid 37d ago$240.921 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 | |
|---|---|---|---|---|---|
| v3.linkdrop.eth | $613.43 | $0.00 | 2 | 37d ago | Graph |
| 0x07f3…bbb5 | $240.92 | $0.00 | 1 | 37d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
72% of observed volume is with a single counterparty, in all 3 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x94d6…f3c00x07f3…bbb5 | Base | $240.92 | 70% | 0xa923…c9ac | 37d ago | 0x96cfef…812af1 |
| 0x94d6…f3c0v3.linkdrop.eth | Base | $324.01 | 70% | 0xa923…c9ac | 37d ago | 0x0575a6…267a1e |
| 0x94d6…f3c0v3.linkdrop.eth | Base | $289.42 | 70% | 0x5f34…bdc0 | 37d ago | 0x63dd7a…174719 |
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 0x94d6…f3c0 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x94d61c29e934c845f68826e298356bc25fbaf3c0
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: 0x94d6…f3c0 curl -s 'https://api.roundhouseai.io/v0/agents/0x94d61c29e934c845f68826e298356bc25fbaf3c0' curl -s 'https://api.roundhouseai.io/v0/entities/0x94d61c29e934c845f68826e298356bc25fbaf3c0/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.