0x7bb2…e639
Paid $0.82 of the $3218.17M Roundhouse has indexed across 1,446,394 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (140)
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 |
|---|---|---|---|---|
| Crypto Markets | 95% | $0.78 | 29 | 1 |
| Not in any catalogue | 5% | $0.04 | 111 | 2 |
$0.04 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.
- 0x7dd5…2629 · last paid 155d ago$0.7829 calls
▸17 of 128 catalogued endpoints list a price this agent paid
- /api/crypto/pricePrice matchCrypto spot price$0.001 listed
- /api/crypto/trendingPrice match$0.001 listed
- /api/ens/resolvePrice match$0.001 listed
- /api/ens/reversePrice matchGeocoding$0.001 listed
- /api/tts/elevenlabs$0.02 listed
- /api/travel/flights$0.02 listed
- /api/llm/kat-coder-pro-v2.5$0.01 listed
- /api/travel/hotels$0.02 listed
120 further catalogued endpoints not listed.
- 0xc26f…8fa9 · last paid 108d ago$0.0315 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x8fea…9bdd · last paid 73d ago$0.00648196 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 | |
|---|---|---|---|---|---|
| 0x7dd5…2629 | $0.78 | $0.00 | 29 | 155d ago | Graph |
| 0xc26f…8fa9 | $0.03 | $0.00 | 15 | 108d ago | Graph |
| 0x8fea…9bdd | $0.006481 | $0.00 | 96 | 73d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
95% of observed volume is with a single counterparty, in all 140 observed settlements.
Organic volume $0.82 of $0.82 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 0x7bb2…e639 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x7bb201564697794d7b7b468a436a9432dda2e639
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: 0x7bb2…e639 curl -s 'https://api.roundhouseai.io/v0/agents/0x7bb201564697794d7b7b468a436a9432dda2e639' curl -s 'https://api.roundhouseai.io/v0/entities/0x7bb201564697794d7b7b468a436a9432dda2e639/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.