0xa0eb…b24c
Paid $1.08 of the $259.50M Roundhouse has indexed across 714,807 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% | $1.08 | 2 | 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; no listed price matches an amount this agent paid, so nothing narrows them.
- 0x0695…cbdb · last paid 73d ago$1.082 calls
▸9 catalogued endpoints, none priced at an amount this agent paid
- /api/real-time-amazon-data$0.17 listed
- /api/extract-keywords$0.11 listed
- /api/bin-ip-checker$0.17 listed
- /api/code-explain$0.19 listed
- /api/governance$0.11 listed
- /api/gas-estimate$0.11 listed
- /api/pro-social$0.07 listed
- /api/ig-downloader-v2$0.13 listed
1 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 | |
|---|---|---|---|---|---|
| 0x0695…cbdb | $1.08 | $0.00 | 2 | 73d ago | Graph |
| 0xc49a…9d2f | $0.00 | $0.98 | 1 | 73d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
52% of observed volume is with a single counterparty, in all 3 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xa0eb…b24c0x0695…cbdb | Base | $0.98 | 100% | fluxa | 73d ago | 0xc8a6b4…c90c96 |
| 0xc49a…9d2f0xa0eb…b24c | Base | $0.98 | 100% | fluxa | 73d ago | 0xd11bec…725ec1 |
| 0xa0eb…b24c0x0695…cbdb | Base | $0.10 | 100% | fluxa | 86d ago | 0xff08d1…7641ba |
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 0xa0eb…b24c has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xa0eb1442ab34a667c5d1f0f04c1b92865e88b24c
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: 0xa0eb…b24c curl -s 'https://api.roundhouseai.io/v0/agents/0xa0eb1442ab34a667c5d1f0f04c1b92865e88b24c' curl -s 'https://api.roundhouseai.io/v0/entities/0xa0eb1442ab34a667c5d1f0f04c1b92865e88b24c/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.