0xbf7e…e01a
Paid $0.53 of the $259.59M Roundhouse has indexed across 715,064 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (4)
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 |
|---|---|---|---|---|
| AI & Media | 55% | $0.29 | 2 | 1 |
| Not in any catalogue | 45% | $0.24 | 2 | 1 |
$0.24 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.
- 0xb049…20ec · last paid 31d ago$0.292 calls
▸200 catalogued endpoints, none priced at an amount this agent paid
- /point-cloud-denoiser-mcp/api/process$0.35 listed
- /podcast-audio-transcriber-mcp/api/process$0.08 listed
- /pixar-usd-assembler-mcp/api/process$0.15 listed
- /ply-splat-compressor-mcp/api/process$0.35 listed
- /planar-tracker-mocha-mcp/api/process$0.25 listed
- /pitchdeck-auto-mcp/api/process$0.05 listed
- /platooning-convoy-mcp/api/process$0.22 listed
- /ashrae-compliance-mcp/api/process$0.10 listed
192 further catalogued endpoints not listed.
- 0xdb48…a74a · last paid 38d ago$0.242 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
One merchant publishes more endpoints than a single catalogue read returns; its list is partial.
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 | |
|---|---|---|---|---|---|
| 0xb049…20ec | $0.29 | $0.00 | 2 | 31d ago | Graph |
| 0xdb48…a74a | $0.24 | $0.00 | 2 | 38d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
55% of observed volume is with a single counterparty, in all 4 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xbf7e…e01a0xb049…20ec | Base | $0.15 | 70% | 0x930d…82c1 | 31d ago | 0x94a89a…c8a906 |
| 0xbf7e…e01a0xb049…20ec | Base | $0.15 | 70% | 0x930d…82c1 | 32d ago | 0xcfc76e…daafee |
| 0xbf7e…e01a0xdb48…a74a | Base | $0.12 | 70% | 0x930d…82c1 | 38d ago | 0xa64e41…7f0b8e |
| 0xbf7e…e01a0xdb48…a74a | Base | $0.12 | 70% | 0x930d…82c1 | 39d ago | 0x291877…720fd9 |
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 0xbf7e…e01a has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xbf7e0d10518fa3ceba855223bdbf7886bfcde01a
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: 0xbf7e…e01a curl -s 'https://api.roundhouseai.io/v0/agents/0xbf7e0d10518fa3ceba855223bdbf7886bfcde01a' curl -s 'https://api.roundhouseai.io/v0/entities/0xbf7e0d10518fa3ceba855223bdbf7886bfcde01a/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.