0x35d6…d04e
Paid $1,469.78 of the $258.78M Roundhouse has indexed across 713,781 wallets — 0.0006% 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% | $1,469.78 | 3 | 2 |
$1,469.78 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.
- 0x1678…1d7f · last paid 93d ago$1,279.002 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x94c3…4e96 · last paid 93d ago$190.781 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 | |
|---|---|---|---|---|---|
| 0x1678…1d7f | $1,279.00 | $0.00 | 2 | 93d ago | Graph |
| 0x94c3…4e96 | $190.78 | $0.00 | 1 | 93d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
87% of observed volume is with a single counterparty, in all 3 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x35d6…d04e0x94c3…4e96 | Base | $190.78 | 100% | 0x4661…93fd | 93d ago | 0x895240…8ba5c2 |
| 0x35d6…d04e0x1678…1d7f | Base | $500.00 | 100% | 0x4661…93fd | 93d ago | 0xd7027a…7faacd |
| 0x35d6…d04e0x1678…1d7f | Base | $779.00 | 100% | 0x4661…93fd | 93d ago | 0xe27266…31d14a |
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 0x35d6…d04e has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x35d65d85bdaef6ad6186171a8b11afc486e6d04e
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: 0x35d6…d04e curl -s 'https://api.roundhouseai.io/v0/agents/0x35d65d85bdaef6ad6186171a8b11afc486e6d04e' curl -s 'https://api.roundhouseai.io/v0/entities/0x35d65d85bdaef6ad6186171a8b11afc486e6d04e/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.