0x1c9e…39c2
Paid $1.00 of the $258.60M Roundhouse has indexed across 713,391 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (1)
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.00 | 1 | 1 |
$1.00 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.
- 0x98c2…cf44 · last paid 44d ago$1.001 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x98c2…cf44 | $1.00 | $0.00 | 1 | 44d 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 1 observed settlement.
Organic volume $1.00 of $1.00 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x1c9e…39c20x98c2…cf44 | Base | $1.00 | 100% | 0x98c2…cf44 | 44d ago | 0x1d1eb8…484f6c |
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 0x1c9e…39c2 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x1c9e7662e016548809c7eaca3059342ef14239c2
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: 0x1c9e…39c2 curl -s 'https://api.roundhouseai.io/v0/agents/0x1c9e7662e016548809c7eaca3059342ef14239c2' curl -s 'https://api.roundhouseai.io/v0/entities/0x1c9e7662e016548809c7eaca3059342ef14239c2/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.