0xd4b8…db32
Paid $0.005198 of the $260.92M Roundhouse has indexed across 716,778 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (5)
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% | $0.005198 | 5 | 3 |
$0.005198 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.
- 0x94d0…f73c · last paid 317d ago$0.004311 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x239c…a17b · last paid 306d ago$0.0005422 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x4944…4bf3 · last paid 306d ago$0.0003462 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
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 | |
|---|---|---|---|---|---|
| 0x94d0…f73c | $0.00431 | $0.00 | 1 | 317d ago | Graph |
| 0x239c…a17b | $0.000542 | $0.00 | 2 | 306d ago | Graph |
| 0x4944…4bf3 | $0.000346 | $0.00 | 2 | 306d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
83% of observed volume is with a single counterparty, in all 5 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xd4b8…db320x239c…a17b | Base | $0.000326 | 100% | questflow | 306d ago | 0x17e543…a21056 |
| 0xd4b8…db320x4944…4bf3 | Base | $0.000208 | 100% | questflow | 306d ago | 0x4570da…1303e0 |
| 0xd4b8…db320x94d0…f73c | Base | $0.00431 | 100% | questflow | 317d ago | 0x5342c0…5102ee |
| 0xd4b8…db320x239c…a17b | Base | $0.000216 | 100% | questflow | 317d ago | 0x0720e0…eb331a |
| 0xd4b8…db320x4944…4bf3 | Base | $0.000138 | 100% | questflow | 317d ago | 0x7b5eff…0c3d87 |
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 0xd4b8…db32 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xd4b8a2238959434f60b144c9b397248e8365db32
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: 0xd4b8…db32 curl -s 'https://api.roundhouseai.io/v0/agents/0xd4b8a2238959434f60b144c9b397248e8365db32' curl -s 'https://api.roundhouseai.io/v0/entities/0xd4b8a2238959434f60b144c9b397248e8365db32/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.