0x5c72…9c5f
Paid $0.03 of the $261.91M Roundhouse has indexed across 718,351 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (3)
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 | 3 | 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 1 of 1 the amount paid narrows the list to the ones listed at that price.
- 0xecb6…ee4d · last paid 285d ago$0.033 calls
▸2 of 8 catalogued endpoints list a price this agent paid
- /api/get_portfolioPrice match$0.01 listed
- /api/get_swap_quotePrice match$0.01 listed
- /api/submit_transaction_hash$0.005 listed
- /api/get_transaction_status$0.001 listed
- /api/execute_swap$0.02 listed
- /api/search_token$0.001 listed
- /api/get_balances$0.005 listed
- /api/get_token_price$0.002 listed
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0xecb6…ee4d | $0.03 | $0.00 | 3 | 285d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 3 observed settlements.
Organic volume $0.03 of $0.03 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x5c72…9c5f0xecb6…ee4d | Base | $0.01 | 100% | coinbase | 285d ago | 0x540e78…167f26 |
| 0x5c72…9c5f0xecb6…ee4d | Base | $0.01 | 100% | coinbase | 285d ago | 0x690686…d35c17 |
| 0x5c72…9c5f0xecb6…ee4d | Base | $0.01 | 100% | coinbase | 285d ago | 0xccee19…cdf543 |
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 0x5c72…9c5f has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x5c725538c9a16aa1c52d707499ad72fe026b9c5f
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: 0x5c72…9c5f curl -s 'https://api.roundhouseai.io/v0/agents/0x5c725538c9a16aa1c52d707499ad72fe026b9c5f' curl -s 'https://api.roundhouseai.io/v0/entities/0x5c725538c9a16aa1c52d707499ad72fe026b9c5f/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.