0x4c5c…b4f0
Paid $74.10 of the $847.23M Roundhouse has indexed across 1,330,946 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (3)
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% | $74.10 | 2 | 2 |
$74.10 went to wallets that publish no endpoint in any catalogue we crawl — spend we can see and cannot describe.
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.
- 0xa9ed…804a · last paid 503d ago$40.001 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0xbf84…2dff · last paid 503d ago$34.101 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0xa9ed…804a | $40.00 | $0.00 | 1 | 503d ago | Graph |
| 0x9f46…35f5 | $0.00 | $40.00 | 1 | 503d ago | Graph |
| 0xbf84…2dff | $34.10 | $0.00 | 1 | 503d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
No concentration or self-dealing patterns detected in all 3 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x4c5c…b4f00xa9ed…804a | Base | $40.00 | 70% | 0xe890…f632 | 503d ago | 0xc57779…0b6f79 |
| 0x4c5c…b4f00xbf84…2dff | Base | $34.10 | 70% | 0xe890…f632 | 503d ago | 0x955a73…8b25b6 |
| 0x9f46…35f50x4c5c…b4f0 | Base | $40.00 | 70% | 0xe890…f632 | 503d ago | 0x9bd24c…9ef84f |
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 0x4c5c…b4f0 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x4c5c9f894b633ae4b9fee763ab7e37a7cf79b4f0
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: 0x4c5c…b4f0 curl -s 'https://api.roundhouseai.io/v0/agents/0x4c5c9f894b633ae4b9fee763ab7e37a7cf79b4f0' curl -s 'https://api.roundhouseai.io/v0/entities/0x4c5c9f894b633ae4b9fee763ab7e37a7cf79b4f0/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.