0x7b34…a7f5
Paid $295.00 of the $3052.78M Roundhouse has indexed across 1,394,551 wallets — less than 0.0001% of it.
Chains (from the recent scan): Ethereum (25) · Base (6)
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 | 93% | $273.00 | 25 | 1 |
| Web & Content | 7% | $22.00 | 6 | 1 |
$273.00 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.
- 0x5c7b…35c5 · last paid 53d ago$273.0025 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x8043…25a8 · last paid 90d ago$22.006 calls
▸43 catalogued endpoints, none priced at an amount this agent paid
- /api/x402/vibe-tools/twitter/users/searchWeb search$0.001 listed
- /api/x402/vibe-tools/data-provider/nansen/token-screener$0.06 listed
- /api/x402/vibe-tools/twitter/tweet/2060755920691384561/quote-tweets$0.005 listed
- /api/x402/vibe-tools/data-provider/nansen/who-bought-sold$0.06 listed
- /api/x402/vibe-tools/data-provider/nansen/balanceWallet balances$0.06 listed
- /api/x402/alpha/exodus$0.50 listed
- /api/x402/vibe-tools/twitter/trends$0.001 listed
- /api/x402/vibe-tools/twitter/counts$0.005 listed
35 further catalogued endpoints not listed.
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 | |
|---|---|---|---|---|---|
| 0x5c7b…35c5 | $273.00 | $0.00 | 25 | 53d ago | Graph |
| 0x8043…25a8 | $22.00 | $0.00 | 6 | 90d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
93% of observed volume is with a single counterparty, in all 31 observed settlements.
Organic volume $295.00 of $295.00 total.
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 0x7b34…a7f5 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x7b3403ec5a1ca8791b0aa358dd8a6efe5efea7f5
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: 0x7b34…a7f5 curl -s 'https://api.roundhouseai.io/v0/agents/0x7b3403ec5a1ca8791b0aa358dd8a6efe5efea7f5' curl -s 'https://api.roundhouseai.io/v0/entities/0x7b3403ec5a1ca8791b0aa358dd8a6efe5efea7f5/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.