0xbf3d…bfb6
Paid $7.30 of the $260.20M Roundhouse has indexed across 715,699 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (69)
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% | $7.30 | 67 | 3 |
$6.28 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; for 1 of 3 the amount paid narrows the list to the ones listed at that price.
- 0x1cc4…e566 · last paid 74d ago$6.002 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x687e…05e9 · last paid 62d ago$1.0251 calls
▸5 of 5 catalogued endpoints list a price this agent paid
- /citibike/dockPrice match$0.02 listed
- /bus/nearestPrice match$0.02 listed
- /subway/nearestPrice match$0.02 listed
- /subway/alertsPrice match$0.02 listed
- /citibike/nearestPrice match$0.02 listed
- 0xdb5a…0671 · last paid 63d ago$0.2814 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 | |
|---|---|---|---|---|---|
| 0x1cc4…e566 | $6.00 | $3.30 | 3 | 74d ago | Graph |
| 0x7a38…7369 | $0.00 | $4.00 | 1 | 74d ago | Graph |
| 0x687e…05e9 | $1.02 | $0.00 | 51 | 62d ago | Graph |
| 0xdb5a…0671 | $0.28 | $0.00 | 14 | 63d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
64% of observed volume is with a single counterparty, in all 69 observed settlements.
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 0xbf3d…bfb6 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xbf3d15a3d3e864b82b0eb971e631800ae811bfb6
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: 0xbf3d…bfb6 curl -s 'https://api.roundhouseai.io/v0/agents/0xbf3d15a3d3e864b82b0eb971e631800ae811bfb6' curl -s 'https://api.roundhouseai.io/v0/entities/0xbf3d15a3d3e864b82b0eb971e631800ae811bfb6/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.