0x7057…b17c
Paid $3.52 of the $3104.66M Roundhouse has indexed across 1,404,591 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (161)
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 |
|---|---|---|---|---|
| Location & Weather | 72% | $2.52 | 160 | 1 |
| Not in any catalogue | 28% | $1.00 | 1 | 1 |
$1.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.
- 0x2880…4e5e · last paid 96d ago$2.52160 calls
▸144 of 200 catalogued endpoints list a price this agent paid
- /stackPrice match$0.005 listed
- /feiertagePrice match$0.001 listed
- /demo/paid-samplePrice match$0.001 listed
- /v1/memory/exportPrice match$0.005 listed
- /v1/baumarkt/mail/removal-reason-counts$0.004 listed
- /trades$0.002 listed
- /v1/sttTranscription$0.06 listed
- /batch/extract$0.008 listed
192 further catalogued endpoints not listed.
- 0x3562…4620 · last paid 130d ago$1.001 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
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 | |
|---|---|---|---|---|---|
| 0x2880…4e5e | $2.52 | $0.00 | 160 | 96d ago | Graph |
| 0x3562…4620 | $1.00 | $0.00 | 1 | 130d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
72% of observed volume is with a single counterparty, in all 161 observed settlements.
Recent activity
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 0x7057…b17c has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x70578a020964f89f3d28b5508a766a31dfb3b17c
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: 0x7057…b17c curl -s 'https://api.roundhouseai.io/v0/agents/0x70578a020964f89f3d28b5508a766a31dfb3b17c' curl -s 'https://api.roundhouseai.io/v0/entities/0x70578a020964f89f3d28b5508a766a31dfb3b17c/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.