AgentReport

0xc02f…82f2

0xc02f9810e1d8f0fcd0b3439b52363628182182f2Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
266
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3069.68M Roundhouse has indexed across 1,403,034 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (266)

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.

GroupShareSpentCallsSellers
Not in any catalogue100%$0.032661

$0.03 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.

  • 0x6482…b779 · last paid 277d ago
    $0.03
    266 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

Balance now
Reading the chain…
Spending power
Reading the chain…
Burn rate
Reading the chain…
Runway
Reading the chain…

Funds flow over time

Activity

MayJunJulAugSepOctNov
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x6482…b779$0.03$0.00266277d 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; all observed volume is with one counterparty, in all 266 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams341d ago0x504c0c…dd721f
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams341d ago0x32832e…ca4666
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams341d ago0xb8507e…4bd917
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams341d ago0x72f716…24ea6d
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams341d ago0xdcc2df…e8e02f
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams341d ago0x6c5dfe…286f08
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams342d ago0xabd760…c10624
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams342d ago0xa79e53…3eb06e
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams342d ago0x63c03b…f74b9f
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams342d ago0xe78f14…47b4e4
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams342d ago0x834591…17fe06
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams342d ago0x4b3e83…2f8f23
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams342d ago0xcad8fa…fdb11e
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams342d ago0xf78992…6d60a1
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams342d ago0x4c31f6…301daf
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams342d ago0xa51ee0…5ffe1d
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams342d ago0x76b7a1…911e93
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams343d ago0x12b5cd…4570ca
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams343d ago0x797b25…1fc8f9
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams343d ago0x8e797c…174c98
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams343d ago0x233265…c20606
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams343d ago0xd12d70…30b33e
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams343d ago0xf5057b…9cf5dd
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams343d ago0xcb9b45…3f5a3e
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams343d ago0xa32752…9804c8

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

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

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: 0xc02f…82f2

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