0x8bd4…a39b
Paid $18.00 of the $3068.58M Roundhouse has indexed across 1,402,396 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (1000)
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% | $15.35 | 1,000 | 4 |
$15.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.
- 0x145e…83c5 · last paid 368d ago$9.42325 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xa9ad…6149 · last paid 368d ago$2.9531 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xa247…81ea · last paid 372d ago$2.0680 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x6937…48e9 · last paid 368d ago$0.92564 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
Folded from this wallet's 1,000 most recent settlements of 1,073 lifetime, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not.
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 | |
|---|---|---|---|---|---|
| 0x145e…83c5 | $9.42 | $0.00 | 325 | 368d ago | Graph |
| 0xa9ad…6149 | $2.95 | $0.00 | 31 | 368d ago | Graph |
| 0xa247…81ea | $2.06 | $0.00 | 80 | 372d ago | Graph |
| 0x6937…48e9 | $0.92 | $0.00 | 564 | 368d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
61% of observed volume is with a single counterparty, in the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap).
Recent activity
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 0x8bd4…a39b has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x8bd4af5d7d0b69ce045c7e10513fb670ea2ba39b
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: 0x8bd4…a39b curl -s 'https://api.roundhouseai.io/v0/agents/0x8bd4af5d7d0b69ce045c7e10513fb670ea2ba39b' curl -s 'https://api.roundhouseai.io/v0/entities/0x8bd4af5d7d0b69ce045c7e10513fb670ea2ba39b/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.