0x82d7…7e22
Paid $50.26 of the $3053.48M Roundhouse has indexed across 1,395,044 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (19)
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 | 90% | $45.01 | 10 | 2 |
| AI & Media | 10% | $5.25 | 9 | 1 |
$45.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; for 2 of 3 the amount paid narrows the list to the ones listed at that price.
- 0x2670…293f · last paid 98d ago$45.009 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x0a84…d358 · last paid 93d ago$5.259 calls
- 0x2ec4…be71 · last paid 106d ago$0.011 call
▸34 of 36 catalogued endpoints list a price this agent paid
- /api/x402/facilitators/statsPrice match$0.01 listed
- /api/x402/merchantsPrice match$0.01 listed
- /api/x402/merchants/:address/statsPrice match$0.01 listed
- /api/x402/facilitatorsPrice match$0.01 listed
- /api/x402/resourcesPrice match$0.01 listed
- /api/x402/merchants/:solana_address/transactionsPrice match$0.01 listed
- /api/data/wallets/:address/statsPrice match$0.01 listed
- /api/x402/resources/searchWeb search$0.02 listed
28 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 | |
|---|---|---|---|---|---|
| 0x2670…293f | $45.00 | $0.00 | 9 | 98d ago | Graph |
| 0x0a84…d358 | $5.25 | $0.00 | 9 | 93d ago | Graph |
| 0x2ec4…be71 | $0.01 | $0.00 | 1 | 106d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
90% of observed volume is with a single counterparty, in all 19 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 0x82d7…7e22 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x82d71c2c52e49972feeda8a6d8f84e4ca2f07e22
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: 0x82d7…7e22 curl -s 'https://api.roundhouseai.io/v0/agents/0x82d71c2c52e49972feeda8a6d8f84e4ca2f07e22' curl -s 'https://api.roundhouseai.io/v0/entities/0x82d71c2c52e49972feeda8a6d8f84e4ca2f07e22/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.