0xb42d…33e0
Paid $779.07 of $3.31B indexed (less than 0.0001%).
Whole-history totals from the index rollup, which can be up to 30 minutes behind.
Chains (from the recent scan): Ethereum (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% | $779.07 | 1 | 1 |
$779.07 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.
- 0x1c88…2fab · last paid 295d ago$779.071 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 | |
|---|---|---|---|---|---|
| 0x1c88…2fab | $779.07 | $0.00 | 1 | 295d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
One counterparty only.
$779.07 of $779.07 is organic.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0xb42d…33e00x1c88…2fab | Ethereum | $779.07 | 70% | 0xbfa1…1b33 | 295d ago | 0x4b8729…f5dc4c |
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 0xb42d…33e0 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0xb42dd174570d8cb6e3a5efffbdc8578e3e0c33e0
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: 0xb42d…33e0 curl -s 'https://api.roundhouseai.io/v0/agents/0xb42dd174570d8cb6e3a5efffbdc8578e3e0c33e0' curl -s 'https://api.roundhouseai.io/v0/entities/0xb42dd174570d8cb6e3a5efffbdc8578e3e0c33e0/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.