0x802d…829f
Paid $0.50 of the $3060.21M Roundhouse has indexed across 1,397,717 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (81)
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 |
|---|---|---|---|---|
| Web & Content | 94% | $0.47 | 67 | 1 |
| Not in any catalogue | 6% | $0.03 | 14 | 1 |
Every merchant paid publishes at least one catalogued endpoint.
Services it paid
A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; for 2 of 2 the amount paid narrows the list to the ones listed at that price.
- 0x6d6e…9192 · last paid 109d ago$0.4767 calls
▸2 of 3 catalogued endpoints list a price this agent paid
- /searchPrice matchWeb search$0.007 listed
- /pay/agent_exa_aiPrice match$0.007 listed
- /contents$0.001 listed
- 0x108b…029f · last paid 111d ago$0.0314 calls
▸16 of 36 catalogued endpoints list a price this agent paid
- /v2/tagsPrice match$0.002 listed
- /v2/vaultsPrice match$0.002 listed
- /v2/curatorsPrice match$0.002 listed
- /v2/networksPrice match$0.002 listed
- /v2/assetsPrice match$0.002 listed
- /v2/historical/:network/:vaultId/apy$0.10 listed
- /v2/historical/asset-prices/:network/:assetAddress$0.10 listed
- /v2/detailed-vaults$0.30 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 | |
|---|---|---|---|---|---|
| 0x6d6e…9192 | $0.47 | $0.00 | 67 | 109d ago | Graph |
| 0x108b…029f | $0.03 | $0.00 | 14 | 111d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
94% of observed volume is with a single counterparty, in all 81 observed settlements.
Organic volume $0.50 of $0.50 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 0x802d…829f has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x802d184b320862d688e3bc18918ff6cbaae1829f
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: 0x802d…829f curl -s 'https://api.roundhouseai.io/v0/agents/0x802d184b320862d688e3bc18918ff6cbaae1829f' curl -s 'https://api.roundhouseai.io/v0/entities/0x802d184b320862d688e3bc18918ff6cbaae1829f/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.