0x17b3…869b
Paid $0.06 of the $259.56M Roundhouse has indexed across 714,983 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (4)
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.06 | 4 | 2 |
$0.04 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; for 1 of 2 the amount paid narrows the list to the ones listed at that price.
- 0xdb5a…0671 · last paid 72d ago$0.042 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xed61…39b6 · last paid 71d ago$0.022 calls
▸1 of 1 catalogued endpoints list a price this agent paid
- /v1/geoPrice match$0.01 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 | |
|---|---|---|---|---|---|
| 0xdb5a…0671 | $0.04 | $0.00 | 2 | 72d ago | Graph |
| 0xed61…39b6 | $0.02 | $0.00 | 2 | 71d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
67% of observed volume is with a single counterparty, in all 4 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x17b3…869b0xed61…39b6 | Base | $0.01 | 100% | coinbase | 71d ago | 0xc59f6e…260982 |
| 0x17b3…869b0xed61…39b6 | Base | $0.01 | 100% | coinbase | 71d ago | 0x3b879b…4dc28d |
| 0x17b3…869b0xdb5a…0671 | Base | $0.02 | 100% | coinbase | 72d ago | 0xd3d375…118d5b |
| 0x17b3…869b0xdb5a…0671 | Base | $0.02 | 100% | coinbase | 72d ago | 0x0c8148…868e98 |
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 0x17b3…869b has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x17b3ecbe8f24a04d717e7e8b99c4fe291b01869b
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: 0x17b3…869b curl -s 'https://api.roundhouseai.io/v0/agents/0x17b3ecbe8f24a04d717e7e8b99c4fe291b01869b' curl -s 'https://api.roundhouseai.io/v0/entities/0x17b3ecbe8f24a04d717e7e8b99c4fe291b01869b/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.