AgentReport

0x79e833dff3151ef73413582579ff8c8da8e338b6

0x79e833dff3151ef73413582579ff8c8da8e338b6Explorer
$40.13
Outbound volume
1
Settlements
1
Distinct counterparties

Chains: Base (1)

Activity

MarAprMayJunJulAug
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0xccc8…15be$40.13$0.00183d agoGraph

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 $40.13 of $40.13 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x79e8…38b60xccc8…15beBase$40.13100%Route unknown83d ago0x51edc7…bfbbc2

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 0x79e833dff3151ef73413582579ff8c8da8e338b6 has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0x79e833dff3151ef73413582579ff8c8da8e338b6

Open skill.md
Show 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: 0x79e833dff3151ef73413582579ff8c8da8e338b6

curl -s 'https://api.roundhouseai.io/v0/agents/0x79e833dff3151ef73413582579ff8c8da8e338b6'
curl -s 'https://api.roundhouseai.io/v0/entities/0x79e833dff3151ef73413582579ff8c8da8e338b6/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.