AgentReport
0x32f6…2a2a
0x32f6d8cbc3edd48003b5a2506499813072762a2aExplorer
Outbound volume
$0.05
Last 7d vs prior 7d
Settlements
47
Last 7d vs prior 7d
2
Distinct counterparties
Chains: Base (47)
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 | |
|---|---|---|---|---|---|
| 0x9c95…e299 | $0.04 | $0.00 | 40 | 15d ago | Graph |
| 0xfe80…47ee | $0.007 | $0.00 | 7 | 14d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
Data quality
No concentration or self-dealing patterns detected in observed activity.
Recent activity
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 0x32f6…2a2a has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x32f6d8cbc3edd48003b5a2506499813072762a2a
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: 0x32f6…2a2a curl -s 'https://api.roundhouseai.io/v0/agents/0x32f6d8cbc3edd48003b5a2506499813072762a2a' curl -s 'https://api.roundhouseai.io/v0/entities/0x32f6d8cbc3edd48003b5a2506499813072762a2a/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://app.roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://app.roundhouseai.io/skill.md first — it is the whole procedure.