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%daydreams337d ago0x03cecc…45e553
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams337d ago0x522ca3…346fab
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams338d ago0x77aae0…233f09
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams338d ago0xd64ea8…2a8aab
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams338d ago0x74c60a…c2261c
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams338d ago0xe6b33d…0b6b98
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams338d ago0x2ab949…a32e8c
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams338d ago0xafd116…808ac7
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams338d ago0x95c40e…3b60a1
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams338d ago0x9ba13a…87ac9d
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams338d ago0x4c42d0…25adf6
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams340d ago0xa6a5c7…2f5dd2
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams340d ago0x9ea8fc…a522a7
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams340d ago0xd8cb4c…0c65b6
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams340d ago0x5db388…6c3851
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams340d ago0x11a3d6…94797d
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams340d ago0x79d681…185f01
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams340d ago0x9254b8…24cbc2
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams340d ago0x6b2c50…341b89
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams340d ago0x53563f…2889eb
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams340d ago0xd5d780…f89b3f
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams340d ago0xbc53c0…e5ce66
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams341d ago0x24060e…72007f
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams341d ago0x6cff14…493f03
0xc02f…82f20x6482…b779BaseBase$0.0001100%daydreams341d ago0x8a92fa…24c71c

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.