0xbe35…b64c
Paid $17.22 of the $258.56M Roundhouse has indexed across 713,267 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (31)
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 |
|---|---|---|---|---|
| AI & Media | 54% | $9.38 | 1 | 1 |
| Not in any catalogue | 46% | $7.85 | 30 | 2 |
$7.85 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.
- 0xfbd4…852f · last paid 306d ago$9.381 call
▸6 catalogued endpoints, none priced at an amount this agent paid
- /api/cloud-eval$0.005 listed
- /api/user$0.001 listed
- /chatText completion$0.10 listed
- /chatText completion$0.10 listed
- /api/masters$0.003 listed
- /api/puzzle/daily$0.001 listed
- 0x0341…1b0f · last paid 317d ago$7.8529 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xdc40…4b66 · last paid 317d ago$0.0011 call
▸1 of 3 catalogued endpoints list a price this agent paid
- /api/fortunePrice match$0.001 listed
- /api/comment$0.002 listed
- /api/post$0.01 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 | |
|---|---|---|---|---|---|
| 0xfbd4…852f | $9.38 | $0.00 | 1 | 306d ago | Graph |
| 0x0341…1b0f | $7.85 | $0.00 | 29 | 317d ago | Graph |
| mas0n.eth | $0.001 | $0.00 | 1 | 317d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
54% of observed volume is with a single counterparty, in all 31 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 0xbe35…b64c has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xbe359e1a4970cb424ec193f24f61ed4590d8b64c
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: 0xbe35…b64c curl -s 'https://api.roundhouseai.io/v0/agents/0xbe359e1a4970cb424ec193f24f61ed4590d8b64c' curl -s 'https://api.roundhouseai.io/v0/entities/0xbe359e1a4970cb424ec193f24f61ed4590d8b64c/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.