0xb4cb…f73d
Paid $0.001 of the $3218.84M Roundhouse has indexed across 1,447,009 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (2)
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 | 100% | $0.001 | 2 | 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; no listed price matches an amount this agent paid, so nothing narrows them.
- 0x7c65…6c40 · last paid 131d ago$0.0012 calls
▸126 catalogued endpoints, none priced at an amount this agent paid
- /api/run/brave/searchWeb search$0.01 listed
- /api/run/firecrawl/scrapePage to markdown$0.01 listed
- /api/run/serper/searchWeb search$0.01 listed
- /api/run/firecrawl/searchWeb search$0.01 listed
- /api/run/fal/generateText completion$0.40 listed
- /api/run/fal/upload$0.01 listed
- /api/run/tavily/searchWeb search$0.01 listed
- /api/run/openfunnel/tech-companies$0.40 listed
118 further catalogued endpoints not listed.
One merchant publishes more endpoints than a single catalogue read returns; its list is partial.
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x7c65…6c40 | $0.001 | $0.00 | 2 | 131d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 2 observed settlements.
Organic volume $0.001 of $0.001 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xb4cb…f73d0x7c65…6c40 | Base | $0.0005 | 5% | 0x6f92…3187 | 131d ago | 0x939ea2…bcbf96 |
| 0xb4cb…f73d0x7c65…6c40 | Base | $0.0005 | 5% | 0x6f92…3187 | 131d ago | 0xa3c9f3…ab7193 |
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 0xb4cb…f73d has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xb4cb403241b84963c6206d0fe552942c1661f73d
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: 0xb4cb…f73d curl -s 'https://api.roundhouseai.io/v0/agents/0xb4cb403241b84963c6206d0fe552942c1661f73d' curl -s 'https://api.roundhouseai.io/v0/entities/0xb4cb403241b84963c6206d0fe552942c1661f73d/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.