0x4c12…38ff
Paid $1.16 of the $3060.21M Roundhouse has indexed across 1,397,717 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (20)
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 | 99% | $1.15 | 18 | 2 |
| Reference Data | <1% | $0.01 | 2 | 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 2 of 3 the amount paid narrows the list to the ones listed at that price.
- 0x5da4…6c70 · last paid 52d 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.
- 0x5533…09b7 · last paid 50d ago$0.1517 calls
▸1 of 2 catalogued endpoints list a price this agent paid
- /api/whales/latestPrice match$0.009 listed
- /api/base-block$0.005 listed
- 0xabf4…a9d0 · last paid 50d ago$0.012 calls
▸36 of 200 catalogued endpoints list a price this agent paid
- /api/onchain-sql$0.04 listed
- /api/perp-basis$0.002 listed
- /api/perp-fundingPerp funding and open interest$0.002 listed
- /v1/metered/chat/completionsText completion$0.001 listed
- /api/hash$0.001 listed
- /api/weather-historyWeather forecast$0.002 listed
- /api/searchWeb search$0.01 listed
- /v1/nano/chat/completionsText completion$0.003 listed
192 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 | |
|---|---|---|---|---|---|
| 0x5da4…6c70 | $1.00 | $0.00 | 1 | 52d ago | Graph |
| 0x5533…09b7 | $0.15 | $0.00 | 17 | 50d ago | Graph |
| 0xabf4…a9d0 | $0.01 | $0.00 | 2 | 50d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
86% of observed volume is with a single counterparty, in all 20 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 0x4c12…38ff has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x4c1218b3e7dc80e709aa0b9c61171f7cd36138ff
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: 0x4c12…38ff curl -s 'https://api.roundhouseai.io/v0/agents/0x4c1218b3e7dc80e709aa0b9c61171f7cd36138ff' curl -s 'https://api.roundhouseai.io/v0/entities/0x4c1218b3e7dc80e709aa0b9c61171f7cd36138ff/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.