0xa048…4c3d
Paid $0.26 of the $3058.83M Roundhouse has indexed across 1,396,904 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (35)
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 | 84% | $0.22 | 31 | 1 |
| AI & Media | 16% | $0.04 | 4 | 1 |
Every merchant paid publishes at least one catalogued endpoint.
Services it paid
A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; for 2 of 2 the amount paid narrows the list to the ones listed at that price.
- 0x9c0e…5fd0 · last paid 17d ago$0.2231 calls
▸8 of 8 catalogued endpoints list a price this agent paid
- /v1/evidencePrice matchWeather forecast$0.01 listed
- /v1/weather/forecastPrice matchWeather forecast$0.01 listed
- /v1/weather/alertsPrice matchWeather forecast$0.01 listed
- /v1/weather/forecastPrice matchWeather forecast$0.01 listed
- /v1/weather/alertsPrice matchWeather forecast$0.01 listed
- /v1/evidencePrice matchWeather forecast$0.01 listed
- /weather/mcpPrice matchWeather forecast$0.01 listed
- /mcpPrice matchWeather forecast$0.01 listed
- 0x9f8b…73a2 · last paid 20d ago$0.044 calls
▸9 of 200 catalogued endpoints list a price this agent paid
- /api/v1/x402/imagePrice matchImage generation$0.01 listed
- /api/v1/x402/speechText to speech$0.002 listed
- /api/v1/x402/video-draft$0.03 listed
- /api/v1/x402/token-estimate$0.001 listed
- /api/v1/x402/weather-forecastWeather forecast$0.001 listed
- /api/v1/x402/http-codes$0.001 listed
- /api/v1/x402/uuid$0.001 listed
- /api/v1/x402/usdc-to-raw$0.001 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 | |
|---|---|---|---|---|---|
| 0x9c0e…5fd0 | $0.22 | $0.00 | 31 | 17d ago | Graph |
| 0x9f8b…73a2 | $0.04 | $0.00 | 4 | 20d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
84% of observed volume is with a single counterparty, in all 35 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 0xa048…4c3d has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xa048c5439ccbb64ed3e54fccf292b2d375154c3d
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: 0xa048…4c3d curl -s 'https://api.roundhouseai.io/v0/agents/0xa048c5439ccbb64ed3e54fccf292b2d375154c3d' curl -s 'https://api.roundhouseai.io/v0/entities/0xa048c5439ccbb64ed3e54fccf292b2d375154c3d/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.