0x1bdd…5a0f
Paid $0.003 of the $3060.21M Roundhouse has indexed across 1,397,717 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (26)
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 | 100% | $0.003 | 1 | 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 1 the amount paid narrows the list to the ones listed at that price.
- 0x9f8b…73a2 · last paid 67d ago$0.0031 call
▸3 of 200 catalogued endpoints list a price this agent paid
- /api/v1/x402/speechText to speech$0.002 listed
- /api/v1/x402/imageImage generation$0.01 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/usdc-to-raw$0.001 listed
- /api/v1/x402/uuid$0.001 listed
- /api/v1/x402/http-codes$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 | |
|---|---|---|---|---|---|
| 0xf32b…d721 | $0.00 | $0.25 | 16 | 19d ago | Graph |
| 0xa1d1…1978 | $0.00 | $0.02 | 2 | 9d ago | Graph |
| 0x54e1…f4e0 | $0.00 | $0.02 | 2 | 20d ago | Graph |
| 0x7e6b…2b1c | $0.00 | $0.02 | 1 | 54d ago | Graph |
| 0x7722…5e4a | $0.00 | $0.01 | 1 | 16d ago | Graph |
| 0xc9c7…1670 | $0.00 | $0.01 | 1 | 40d ago | Graph |
| 0xec2a…d034 | $0.00 | $0.01 | 1 | 40d ago | Graph |
| 0x7706…4121 | $0.00 | $0.01 | 1 | 50d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
71% of observed volume is with a single counterparty, in all 26 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 0x1bdd…5a0f has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x1bdd0cf6c2457765afeb717bc1e5d74b27d45a0f
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: 0x1bdd…5a0f curl -s 'https://api.roundhouseai.io/v0/agents/0x1bdd0cf6c2457765afeb717bc1e5d74b27d45a0f' curl -s 'https://api.roundhouseai.io/v0/entities/0x1bdd0cf6c2457765afeb717bc1e5d74b27d45a0f/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.