0x392a…ca48
Paid $0.02 of the $259.08M Roundhouse has indexed across 714,004 wallets — less than 0.0001% of it.
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 |
|---|---|---|---|---|
| Web & Content | 100% | $0.02 | 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; for 1 of 1 the amount paid narrows the list to the ones listed at that price.
- 0xc3d0…97cb · last paid 2d ago$0.022 calls
▸11 of 15 catalogued endpoints list a price this agent paid
- /api/v1/signalsPrice match$0.01 listed
- /api/v1/markets/searchPrice matchWeb search$0.01 listed
- /api/v1/markets/lookupPrice match$0.005 listed
- /api/v1/signals/featuredPrice match$0.005 listed
- /api/v1/assetsPrice match$0.005 listed
- /api/v1/marketsPrice matchPrediction market odds$0.005 listed
- /api/v1/assets/searchPrice matchWeb search$0.01 listed
- /api/v1/markets/mispriced$0.02 listed
7 further catalogued endpoints not 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 | |
|---|---|---|---|---|---|
| 0xc3d0…97cb | $0.02 | $0.00 | 2 | 2d 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 2 observed settlements.
Organic volume $0.02 of $0.02 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x392a…ca480xc3d0…97cb | Base | $0.01 | 100% | coinbase | 2d ago | 0xc490da…ec0545 |
| 0x392a…ca480xc3d0…97cb | Base | $0.005 | 100% | coinbase | 2d ago | 0x9302fd…96c180 |
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 0x392a…ca48 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x392ae8d2f9b5da0d3f2939c84cbc0d8d6193ca48
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: 0x392a…ca48 curl -s 'https://api.roundhouseai.io/v0/agents/0x392ae8d2f9b5da0d3f2939c84cbc0d8d6193ca48' curl -s 'https://api.roundhouseai.io/v0/entities/0x392ae8d2f9b5da0d3f2939c84cbc0d8d6193ca48/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.