AgentReport
0x80c5…a238
0x80c51bdb6846963930f1114a96b37429c5d4a238Explorer
Outbound volume
$0.07
Last 7d vs prior 7d
Settlements
37
Last 7d vs prior 7d
2
Distinct counterparties
Chains: Base (37)
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 | |
|---|---|---|---|---|---|
| 0xe903…1abf | $0.07 | $0.00 | 31 | 20h ago | Graph |
| 0x2633…2223 | $0.00255 | $0.00 | 6 | 48d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
Data quality
96% of observed volume is with a single counterparty.
Organic volume $0.07 of $0.07 total.
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 0x80c5…a238 has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x80c51bdb6846963930f1114a96b37429c5d4a238
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: 0x80c5…a238 curl -s 'https://api.roundhouseai.io/v0/agents/0x80c51bdb6846963930f1114a96b37429c5d4a238' curl -s 'https://api.roundhouseai.io/v0/entities/0x80c51bdb6846963930f1114a96b37429c5d4a238/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.