0x383b…9e3c
Paid $8.00 of the $261.45M Roundhouse has indexed across 717,524 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (8)
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% | $8.00 | 8 | 2 |
$4.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; for 1 of 2 the amount paid narrows the list to the ones listed at that price.
- 0x0fe8…9393 · last paid 319d ago$4.004 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x6042…eebf · last paid 334d ago$4.004 calls
▸1 of 1 catalogued endpoints list a price this agent paid
- /mintPrice match$1.00 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 | |
|---|---|---|---|---|---|
| 0x0fe8…9393 | $4.00 | $0.00 | 4 | 319d ago | Graph |
| 0x6042…eebf | $4.00 | $0.00 | 4 | 334d 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 8 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x383b…9e3c0x0fe8…9393 | Base | $1.00 | 100% | coinbase | 319d ago | 0x620cbc…426841 |
| 0x383b…9e3c0x0fe8…9393 | Base | $1.00 | 100% | coinbase | 319d ago | 0x7b5bc8…832ce1 |
| 0x383b…9e3c0x0fe8…9393 | Base | $1.00 | 100% | coinbase | 319d ago | 0x193755…827cd7 |
| 0x383b…9e3c0x0fe8…9393 | Base | $1.00 | 100% | coinbase | 319d ago | 0xccf969…816fae |
| 0x383b…9e3c0x6042…eebf | Base | $1.00 | 100% | payAI | 334d ago | 0xa4f3a7…be7920 |
| 0x383b…9e3c0x6042…eebf | Base | $1.00 | 100% | payAI | 334d ago | 0x5ed73d…710718 |
| 0x383b…9e3c0x6042…eebf | Base | $1.00 | 100% | payAI | 334d ago | 0xbb369d…d2bc92 |
| 0x383b…9e3c0x6042…eebf | Base | $1.00 | 100% | payAI | 334d ago | 0xbddb39…56e0de |
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 0x383b…9e3c has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x383bf8c7615cf5334a8809188db2570465b19e3c
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: 0x383b…9e3c curl -s 'https://api.roundhouseai.io/v0/agents/0x383bf8c7615cf5334a8809188db2570465b19e3c' curl -s 'https://api.roundhouseai.io/v0/entities/0x383bf8c7615cf5334a8809188db2570465b19e3c/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.