0x9be6…a3ea
Paid $991.82 of the $3139.09M Roundhouse has indexed across 1,424,501 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (5)
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% | $991.82 | 4 | 2 |
$991.82 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.
- 0x245a…4eed · last paid 529d ago$900.203 calls
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x9871…c517 · last paid 509d ago$91.621 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
ERC-8004 registration
- Declares 3 endpoints, none of them in any catalogue we crawl
Card follows eips.ethereum.org/EIPS/eip-8004#registration-v1
Funds flow over time
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x245a…4eed | $900.20 | $0.00 | 3 | 529d ago | Graph |
| 0x9871…c517 | $91.62 | $30.54 | 2 | 508d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
88% of observed volume is with a single counterparty, in all 5 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x9871…c5170x9be6…a3ea | Base | $30.54 | 70% | 0xe890…f632 | 508d ago | 0x595861…0bad89 |
| 0x9be6…a3ea0x9871…c517 | Base | $91.62 | 70% | 0xe890…f632 | 509d ago | 0x7067c6…046d25 |
| 0x9be6…a3ea0x245a…4eed | Base | $300.07 | 70% | 0xe890…f632 | 529d ago | 0xc28c95…0a49c8 |
| 0x9be6…a3ea0x245a…4eed | Base | $300.07 | 70% | 0xe890…f632 | 531d ago | 0x7cd89f…27b2c5 |
| 0x9be6…a3ea0x245a…4eed | Base | $300.06 | 70% | 0xe890…f632 | 537d ago | 0x328f1d…b343a2 |
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 0x9be6…a3ea has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x9be6e220bce4fa00102dde0cdf9e880cfb14a3ea
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: 0x9be6…a3ea curl -s 'https://api.roundhouseai.io/v0/agents/0x9be6e220bce4fa00102dde0cdf9e880cfb14a3ea' curl -s 'https://api.roundhouseai.io/v0/entities/0x9be6e220bce4fa00102dde0cdf9e880cfb14a3ea/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.