0x5be9…e138
Paid $0.03 of the $834.02M Roundhouse has indexed across 1,300,437 wallets — less than 0.0001% of it.
Counted from this wallet’s own settlements. The index rollup has no row for it yet, which is normal for an address first seen in the last half hour.
Chains (from the recent scan): Base (2)
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 | 100% | $0.03 | 2 | 2 |
$0.03 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; no listed price matches an amount this agent paid, so nothing narrows them.
- 0xab9c…cd1c · last paid 2d ago$0.021 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x0a72…020e · last paid 2d ago$0.011 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0xab9c…cd1c | $0.02 | $0.00 | 1 | 2d ago | Graph |
| 0x0a72…020e | $0.01 | $0.00 | 1 | 2d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
60% of observed volume is with a single counterparty, in all 2 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x5be9…e1380xab9c…cd1c | Base | $0.02 | 100% | coinbase | 2d ago | 0x754215…faa215 |
| 0x5be9…e1380x0a72…020e | Base | $0.01 | 100% | coinbase | 2d ago | 0xb9d85d…a8c06e |
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 0x5be9…e138 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x5be92dc11a5eea6c4e0f3851d65550f7f31de138
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: 0x5be9…e138 curl -s 'https://api.roundhouseai.io/v0/agents/0x5be92dc11a5eea6c4e0f3851d65550f7f31de138' curl -s 'https://api.roundhouseai.io/v0/entities/0x5be92dc11a5eea6c4e0f3851d65550f7f31de138/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.