0x448d…c5ed
Paid $3.85 of the $3060.21M Roundhouse has indexed across 1,397,717 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (135)
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 | 76% | $2.93 | 87 | 1 |
| Not in any catalogue | 24% | $0.92 | 48 | 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.
- 0x23fc…c75d · last paid 50d ago$2.9387 calls
▸70 of 77 catalogued endpoints list a price this agent paid
- /web/v1/crawlPrice matchPage to markdown$0.01 listed
- /v1/meeting-slotsPrice match$0.10 listed
- /tasks/v1/crawlPrice matchPage to markdown$0.02 listed
- /paid/meeting-slotsPrice match$0.10 listed
- /paid/crawlPrice matchPage to markdown$0.10 listed
- /web/v1/scrape/batch$0.004 listed
- /web/v1/session$0.007 listed
- /tasks/v1/scrape/batch$0.004 listed
69 further catalogued endpoints not listed.
- 0xf41d…fecf · last paid 73d ago$0.9248 calls
▸1 of 1 catalogued endpoints list a price this agent paid
- /paid/find-meeting-slotsPrice match$0.02 listed
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 | |
|---|---|---|---|---|---|
| 0x23fc…c75d | $2.93 | $0.00 | 87 | 50d ago | Graph |
| 0xf41d…fecf | $0.92 | $0.00 | 48 | 73d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
76% of observed volume is with a single counterparty, in all 135 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 0x448d…c5ed has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x448d4734f9949c1cdbcf68b084efdc6d2335c5ed
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: 0x448d…c5ed curl -s 'https://api.roundhouseai.io/v0/agents/0x448d4734f9949c1cdbcf68b084efdc6d2335c5ed' curl -s 'https://api.roundhouseai.io/v0/entities/0x448d4734f9949c1cdbcf68b084efdc6d2335c5ed/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.