0xfe4d…ca59
Paid $0.10 of the $259.14M Roundhouse has indexed across 714,236 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (1)
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.10 | 1 | 1 |
$0.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.
- 0xb7a1…5cde · last paid 49d ago$0.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 | |
|---|---|---|---|---|---|
| superboard.eth | $0.10 | $0.00 | 1 | 49d 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 1 observed settlement.
Organic volume $0.10 of $0.10 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xfe4d…ca59superboard.eth | Base | $0.10 | 100% | 0x22fa…9ace | 49d ago | 0xd58c4b…b6ab26 |
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 0xfe4d…ca59 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xfe4de2d1766a0e1b7e031a814465e51f3a82ca59
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: 0xfe4d…ca59 curl -s 'https://api.roundhouseai.io/v0/agents/0xfe4de2d1766a0e1b7e031a814465e51f3a82ca59' curl -s 'https://api.roundhouseai.io/v0/entities/0xfe4de2d1766a0e1b7e031a814465e51f3a82ca59/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.