0xb3a4…e63e
Paid $250.74 of the $846.98M Roundhouse has indexed across 1,330,524 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% | $250.74 | 2 | 2 |
$250.74 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.
- 0x27ab…4b64 · last paid 420d ago$127.161 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x588c…8e1c · last paid 420d ago$123.581 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 | |
|---|---|---|---|---|---|
| 0x588c…8e1c | $123.58 | $127.16 | 2 | 420d ago | Graph |
| 0x27ab…4b64 | $127.16 | $0.00 | 1 | 420d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
66% of observed volume is with a single counterparty, in all 3 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xb3a4…e63e0x588c…8e1c | Base | $123.58 | 70% | 0xe890…f632 | 420d ago | 0x7c9152…17ea4b |
| 0xb3a4…e63e0x27ab…4b64 | Base | $127.16 | 70% | 0xe890…f632 | 420d ago | 0xf278f5…05afc2 |
| 0x588c…8e1c0xb3a4…e63e | Base | $127.16 | 70% | 0xe890…f632 | 420d ago | 0x0cd283…5f6f81 |
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 0xb3a4…e63e has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xb3a444072f3b4a639d084abc1540bc570099e63e
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: 0xb3a4…e63e curl -s 'https://api.roundhouseai.io/v0/agents/0xb3a444072f3b4a639d084abc1540bc570099e63e' curl -s 'https://api.roundhouseai.io/v0/entities/0xb3a444072f3b4a639d084abc1540bc570099e63e/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.