0x5239…f64c
Paid $57.58 of the $3058.83M Roundhouse has indexed across 1,396,904 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% | $57.58 | 6 | 5 |
$38.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 5 the amount paid narrows the list to the ones listed at that price.
- 0x6374…e9c3 · last paid 127d ago$30.001 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x9ed1…c08f · last paid 159d ago$19.481 call
▸1 catalogued endpoints, none priced at an amount this agent paid
- /api/v1/graphs/queries$0.01 listed
- 0xf2ec…240a · last paid 149d ago$5.001 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xc43f…fa2a · last paid 149d ago$3.001 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xf121…431b · last paid 114d ago$0.102 calls
▸39 of 142 catalogued endpoints list a price this agent paid
- /api/locus-parcel-lookup$0.01 listed
- /api/locus-wikipedia-place-context$0.01 listed
- /api/locus-pfas-occurrence$0.01 listed
- /api/locus-appeal-window$0.01 listed
- /api/locus-wildfire-history$0.01 listed
- /api/locus-storm-events$0.01 listed
- /api/locus-nfip-claims$0.01 listed
- /api/locus-zoning$0.01 listed
134 further catalogued endpoints not listed.
One merchant publishes more endpoints than a single catalogue read returns; its list is partial.
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 | |
|---|---|---|---|---|---|
| 0x6374…e9c3 | $30.00 | $0.00 | 1 | 127d ago | Graph |
| 0x9ed1…c08f | $19.48 | $0.00 | 1 | 159d ago | Graph |
| 0xf2ec…240a | $5.00 | $0.00 | 1 | 149d ago | Graph |
| 0xc43f…fa2a | $3.00 | $0.00 | 1 | 149d ago | Graph |
| velinus.eth | $0.10 | $0.00 | 2 | 114d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
52% of observed volume is with a single counterparty, in all 6 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x5239…f64cvelinus.eth | Base | $0.05 | 100% | coinbase | 114d ago | 0xef479a…9bd39a |
| 0x5239…f64cvelinus.eth | Base | $0.05 | 100% | coinbase | 114d ago | 0xf948ef…858486 |
| 0x5239…f64c0x6374…e9c3 | Base | $30.00 | 70% | 0xa923…c9ac | 127d ago | 0xa5e248…82dba0 |
| 0x5239…f64c0xc43f…fa2a | Base | $3.00 | 70% | 0xa923…c9ac | 149d ago | 0x145836…7aa584 |
| 0x5239…f64c0xf2ec…240a | Base | $5.00 | 70% | 0xa923…c9ac | 149d ago | 0xb0f5ed…d9bce2 |
| 0x5239…f64c0x9ed1…c08f | Base | $19.48 | 70% | 0xa923…c9ac | 159d ago | 0x6c9c87…aaa14d |
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 0x5239…f64c has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x523912b84d41fc8cd4f66d65c8a6793843c2f64c
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: 0x5239…f64c curl -s 'https://api.roundhouseai.io/v0/agents/0x523912b84d41fc8cd4f66d65c8a6793843c2f64c' curl -s 'https://api.roundhouseai.io/v0/entities/0x523912b84d41fc8cd4f66d65c8a6793843c2f64c/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. Either pay over x402 (mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at https://roundhouseai.io/dashboard/connections. If you have neither, ask before going further. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.