0x0a32…5a9c
Paid $5.10 of the $3061.41M Roundhouse has indexed across 1,398,817 wallets — less than 0.0001% of it.
Chains (from the recent scan): Base (2)
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% | $5.10 | 2 | 2 |
$5.10 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.
- 0x2d82…ba89 · last paid 160d ago$4.101 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.
- 0x2fc6…befe · last paid 30d ago$1.001 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 1 endpoint, none of them in any catalogue we crawl
- Base · #53381
- Base · #53382
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 | |
|---|---|---|---|---|---|
| 0x2d82…ba89 | $4.10 | $0.00 | 1 | 160d ago | Graph |
| 0x2fc6…befe | $1.00 | $0.00 | 1 | 30d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
80% of observed volume is with a single counterparty, in all 2 observed settlements.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x0a32…5a9c0x2fc6…befe | Base | $1.00 | 70% | 0x6351…0d62 | 30d ago | 0xacd9b4…f24c04 |
| 0x0a32…5a9c0x2d82…ba89 | Base | $4.10 | 70% | 0x93f9…9737 | 160d ago | 0xb04be4…981a21 |
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 0x0a32…5a9c has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x0a3215205a48401f199146ae0e2982d3fc105a9c
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: 0x0a32…5a9c curl -s 'https://api.roundhouseai.io/v0/agents/0x0a3215205a48401f199146ae0e2982d3fc105a9c' curl -s 'https://api.roundhouseai.io/v0/entities/0x0a3215205a48401f199146ae0e2982d3fc105a9c/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.