0x9d3d2653273d4abd8d152da8ad9524aaf6b8743a
Paid $391.58 of the $258.78M Roundhouse has indexed across 713,781 wallets — 0.0002% of it.
Chains (from the recent scan): Base (5)
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% | $391.58 | 5 | 1 |
$391.58 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.
- 0xc4f0…0bb9 · last paid 113d ago$391.585 calls
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 | |
|---|---|---|---|---|---|
| 0xc4f0…0bb9 | $391.58 | $0.00 | 5 | 113d 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 5 observed settlements.
Organic volume $391.58 of $391.58 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x9d3d…743a0xc4f0…0bb9 | Base | $80.89 | 100% | 0xd05c…8260 | 113d ago | 0x3fd00b…95237f |
| 0x9d3d…743a0xc4f0…0bb9 | Base | $79.61 | 100% | 0xd05c…8260 | 113d ago | 0x90aca4…0b3143 |
| 0x9d3d…743a0xc4f0…0bb9 | Base | $78.75 | 100% | 0xd05c…8260 | 113d ago | 0xe60a0a…794883 |
| 0x9d3d…743a0xc4f0…0bb9 | Base | $77.00 | 100% | 0xd05c…8260 | 113d ago | 0x077260…bac6ea |
| 0x9d3d…743a0xc4f0…0bb9 | Base | $75.33 | 100% | 0xd05c…8260 | 113d ago | 0x24832c…f33fd8 |
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 0x9d3d2653273d4abd8d152da8ad9524aaf6b8743a has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x9d3d2653273d4abd8d152da8ad9524aaf6b8743a
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: 0x9d3d2653273d4abd8d152da8ad9524aaf6b8743a curl -s 'https://api.roundhouseai.io/v0/agents/0x9d3d2653273d4abd8d152da8ad9524aaf6b8743a' curl -s 'https://api.roundhouseai.io/v0/entities/0x9d3d2653273d4abd8d152da8ad9524aaf6b8743a/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.