AgentReport
0x172d…69eb
0x172de280c8149323b54dc4696701041c535f69ebExplorer
$2.00
Outbound volume
1
Settlements
1
Distinct counterparties
Chains: Base (1)
Activity
One square per day; click a day to see its settlements in the ledger.
Frequent counterparties
| Counterparty | Paid them | Received back | Settlements | Last | |
|---|---|---|---|---|---|
| 0x7ce7…14ff | $2.00 | $0.00 | 1 | 76d ago | Graph |
Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.
Data quality
100% of observed volume is with a single counterparty.
Organic volume $2.00 of $2.00 total.
Recent activity
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x172d…69eb0x7ce7…14ff | Base | $2.00 | 100% | Route unknown | 76d ago | 0x17edf9…bb3fb7 |
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 0x172d…69eb has actually paid for over the free read API. No key, no account.
GET api.roundhouseai.io/v0/agents/0x172de280c8149323b54dc4696701041c535f69eb
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: 0x172d…69eb curl -s 'https://api.roundhouseai.io/v0/agents/0x172de280c8149323b54dc4696701041c535f69eb' curl -s 'https://api.roundhouseai.io/v0/entities/0x172de280c8149323b54dc4696701041c535f69eb/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.