0x0479…8069
Paid $70.00 of the $3060.46M Roundhouse has indexed across 1,398,118 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (1000)
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 |
|---|---|---|---|---|
| Web & Content | 83% | $4.99 | 999 | 1 |
| Not in any catalogue | 17% | $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.
- 0x836b…9ee2 · last paid 7d ago$4.99999 calls
▸200 of 200 catalogued endpoints list a price this agent paid
- /api/codes/searchPrice matchWeb search$0.005 listed
- /api/calc/canriskPrice match$0.005 listed
- /api/calc/qidsPrice match$0.005 listed
- /api/calc/chipPrice match$0.005 listed
- /api/calc/rome_iv_chsPrice match$0.005 listed
- /api/calc/rome_iv_child_ibsPrice match$0.005 listed
- /api/calc/rtsPrice match$0.005 listed
- /api/calc/scarfPrice match$0.005 listed
192 further catalogued endpoints not listed.
- 0x4020…0003 · last paid 27d 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.
Folded from this wallet's 1,000 most recent settlements of 12,384 lifetime, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not. 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 | |
|---|---|---|---|---|---|
| 0x836b…9ee2 | $4.99 | $0.00 | 999 | 7d ago | Graph |
| 0x4020…0003 | $1.00 | $0.00 | 1 | 27d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
83% of observed volume is with a single counterparty, in the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap).
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 0x0479…8069 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x04796b9cfd140310b6c11608eb70f60e504b8069
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: 0x0479…8069 curl -s 'https://api.roundhouseai.io/v0/agents/0x04796b9cfd140310b6c11608eb70f60e504b8069' curl -s 'https://api.roundhouseai.io/v0/entities/0x04796b9cfd140310b6c11608eb70f60e504b8069/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.