0xbe0a5ced1b40c140260efc2a8a333a205159eb52
Paid $2.20 of the $258.70M Roundhouse has indexed across 713,651 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (36)
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 | 89% | $1.96 | 32 | 1 |
| Web & Content | 11% | $0.24 | 4 | 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.
- 0xb5a0…032d · last paid 103d ago$1.9632 calls
▸1 of 1 catalogued endpoints list a price this agent paid
- /api/agents/:id/runPrice match$0.10 listed
- 0xcfa2…4dbe · last paid 102d ago$0.244 calls
▸58 of 58 catalogued endpoints list a price this agent paid
- /api/sc/instagram/user/reelsPrice match$0.06 listed
- /api/sc/facebook/adLibrary/company/adsPrice match$0.06 listed
- /api/sc/github/userPrice match$0.06 listed
- /api/sc/tiktok/profilePrice match$0.06 listed
- /api/sc/spotify/artistPrice match$0.06 listed
- /api/sc/soundcloud/artistPrice match$0.06 listed
- /api/sc/google/company/adsPrice match$0.06 listed
- /api/sc/github/trending/repositoriesPrice match$0.06 listed
50 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 | |
|---|---|---|---|---|---|
| 0xb5a0…032d | $1.96 | $0.00 | 32 | 103d ago | Graph |
| 0xcfa2…4dbe | $0.24 | $0.00 | 4 | 102d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
89% of observed volume is with a single counterparty, in all 36 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 0xbe0a5ced1b40c140260efc2a8a333a205159eb52 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xbe0a5ced1b40c140260efc2a8a333a205159eb52
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: 0xbe0a5ced1b40c140260efc2a8a333a205159eb52 curl -s 'https://api.roundhouseai.io/v0/agents/0xbe0a5ced1b40c140260efc2a8a333a205159eb52' curl -s 'https://api.roundhouseai.io/v0/entities/0xbe0a5ced1b40c140260efc2a8a333a205159eb52/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.