0x5ab0…e1e3
Paid $0.10 of the $260.82M Roundhouse has indexed across 716,570 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (10)
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 | 3 | 1 |
$0.003 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.
- 0x2670…293f · last paid 94d ago$0.0033 calls
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 | |
|---|---|---|---|---|---|
| 0x2670…293f | $0.003 | $0.00 | 3 | 94d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
7 self-dealing settlements (payer = payee) observed; all observed volume is with one counterparty, in all 10 observed settlements.
Organic volume $0.003 of $0.10 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x5ab0…e1e30x5ab0…e1e3 | Base | $0.000001 | 100% | Payer-submitted | 94d ago | 0xc9d464…4d4169 |
| 0x5ab0…e1e30x5ab0…e1e3 | Base | $0.01 | 100% | Payer-submitted | 94d ago | 0xd11ede…c9ecf8 |
| 0x5ab0…e1e30x5ab0…e1e3 | Base | $0.01 | 100% | Payer-submitted | 94d ago | 0x119acb…453e6d |
| 0x5ab0…e1e30x5ab0…e1e3 | Base | $0.01 | 100% | Payer-submitted | 94d ago | 0x85e5bf…b663ba |
| 0x5ab0…e1e30x5ab0…e1e3 | Base | $0.01 | 100% | Payer-submitted | 94d ago | 0xfc64da…51a031 |
| 0x5ab0…e1e30x5ab0…e1e3 | Base | $0.03 | 100% | Payer-submitted | 94d ago | 0x1e7715…e3ab85 |
| 0x5ab0…e1e30x5ab0…e1e3 | Base | $0.03 | 100% | Payer-submitted | 94d ago | 0x22199b…1c9609 |
| 0x5ab0…e1e30x2670…293f | Base | $0.001 | 100% | Payer-submitted | 94d ago | 0x2e248c…b0bc4f |
| 0x5ab0…e1e30x2670…293f | Base | $0.001 | 100% | Payer-submitted | 94d ago | 0x003039…a882a8 |
| 0x5ab0…e1e30x2670…293f | Base | $0.001 | 100% | Payer-submitted | 94d ago | 0xf020be…3968a6 |
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 0x5ab0…e1e3 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x5ab0b4ff56b1c25a548b0a7ad39980aa67b0e1e3
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: 0x5ab0…e1e3 curl -s 'https://api.roundhouseai.io/v0/agents/0x5ab0b4ff56b1c25a548b0a7ad39980aa67b0e1e3' curl -s 'https://api.roundhouseai.io/v0/entities/0x5ab0b4ff56b1c25a548b0a7ad39980aa67b0e1e3/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.