0x083f…fb38
Paid $0.24 of the $258.78M Roundhouse has indexed across 713,781 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (6)
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.24 | 3 | 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.
- 0x159b…4908 · last paid 26d ago$0.243 calls
▸3 of 4 catalogued endpoints list a price this agent paid
- /goPrice match$0.10 listed
- /nftPrice match$0.10 listed
- /x402/nft-mint/api/verify-and-mintPrice match$0.10 listed
- /pay$0.01 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 | |
|---|---|---|---|---|---|
| 0x159b…4908 | $0.24 | $0.00 | 3 | 26d ago | Graph |
| 0xc1b3…aa1e | $0.00 | $0.24 | 3 | 32d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
50% of observed volume is with a single counterparty, in all 6 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x083f…fb380x159b…4908 | Base | $0.04 | 70% | 0x4af9…c956 | 26d ago | 0xa0dc81…9086af |
| 0xc1b3…aa1e0x083f…fb38 | Base | $0.04 | 100% | dexter | 32d ago | 0x9145a1…9d24a7 |
| 0x083f…fb380x159b…4908 | Base | $0.10 | 100% | dexter | 38d ago | 0xb1eb43…8e9221 |
| 0xc1b3…aa1e0x083f…fb38 | Base | $0.10 | 100% | dexter | 38d ago | 0x617102…e3c52c |
| 0x083f…fb380x159b…4908 | Base | $0.10 | 100% | dexter | 39d ago | 0xe435e8…ea9321 |
| 0xc1b3…aa1e0x083f…fb38 | Base | $0.10 | 100% | dexter | 39d ago | 0x0439e0…bd2490 |
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 0x083f…fb38 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x083f3f2acf41cf19d1143c9b985b1e66ac4bfb38
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: 0x083f…fb38 curl -s 'https://api.roundhouseai.io/v0/agents/0x083f3f2acf41cf19d1143c9b985b1e66ac4bfb38' curl -s 'https://api.roundhouseai.io/v0/entities/0x083f3f2acf41cf19d1143c9b985b1e66ac4bfb38/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.