0x4d54…3052
Paid $0.19 of the $3105.74M Roundhouse has indexed across 1,408,383 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (22)
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 |
|---|---|---|---|---|
| AI & Media | 89% | $0.17 | 17 | 1 |
| Onchain Data | 11% | $0.02 | 5 | 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 1 of 2 the amount paid narrows the list to the ones listed at that price.
- 0x6302…ad57 · last paid 155d ago$0.1717 calls
▸33 of 53 catalogued endpoints list a price this agent paid
- /api/v1/location/searchPrice match$0.01 listed
- /createTaskPrice match$0.01 listed
- /v1/simplePrice match$0.01 listed
- /listings/salePrice match$0.01 listed
- /properties/randomPrice match$0.01 listed
- /api/v1/location/:locationId/detailsPrice match$0.01 listed
- /take$0.02 listed
- /v2/queryWeb search$0.02 listed
45 further catalogued endpoints not listed.
- 0x7dd5…2629 · last paid 155d ago$0.025 calls
▸128 catalogued endpoints, none priced at an amount this agent paid
- /api/tts/elevenlabs$0.02 listed
- /api/crypto/priceCrypto spot price$0.001 listed
- /api/travel/flights$0.02 listed
- /api/llm/kat-coder-pro-v2.5$0.01 listed
- /api/crypto/trending$0.001 listed
- /api/travel/hotels$0.02 listed
- /api/ens/resolve$0.001 listed
- /api/ens/reverseGeocoding$0.001 listed
120 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 | |
|---|---|---|---|---|---|
| 0x6302…ad57 | $0.17 | $0.00 | 17 | 155d ago | Graph |
| 0x7dd5…2629 | $0.02 | $0.00 | 5 | 155d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
89% of observed volume is with a single counterparty, in all 22 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 0x4d54…3052 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x4d54ab4ba96ee65027d48eb40c4caecdb42d3052
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: 0x4d54…3052 curl -s 'https://api.roundhouseai.io/v0/agents/0x4d54ab4ba96ee65027d48eb40c4caecdb42d3052' curl -s 'https://api.roundhouseai.io/v0/entities/0x4d54ab4ba96ee65027d48eb40c4caecdb42d3052/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.