AgentReport

0xf3cc…cbc8

0xf3cc83a990f5a319c14b9aafbf0af4449feacbc8Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
251
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 (251)

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.032511

$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
    251 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.00251277d 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 251 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf3cc…cbc80x6482…b779BaseBase$0.0001100%daydreams344d ago0x4b5de3…52bcb4
0xf3cc…cbc80x6482…b779BaseBase$0.0001100%daydreams344d ago0xc73f55…eceba7
0xf3cc…cbc80x6482…b779BaseBase$0.0001100%daydreams344d ago0x68a15d…a8612b
0xf3cc…cbc80x6482…b779BaseBase$0.0001100%daydreams344d ago0xef6b8d…d28b8a
0xf3cc…cbc80x6482…b779BaseBase$0.0001100%daydreams344d ago0x60fa74…1644d5
0xf3cc…cbc80x6482…b779BaseBase$0.0001100%daydreams344d ago0x3b06d0…280d78
0xf3cc…cbc80x6482…b779BaseBase$0.0001100%daydreams344d ago0xf79684…28bd0a
0xf3cc…cbc80x6482…b779BaseBase$0.0001100%daydreams345d ago0x170063…342574
0xf3cc…cbc80x6482…b779BaseBase$0.0001100%daydreams345d ago0x4c2e9c…b764d4
0xf3cc…cbc80x6482…b779BaseBase$0.0001100%daydreams345d ago0xb96259…78cecf
0xf3cc…cbc80x6482…b779BaseBase$0.0001100%daydreams345d ago0xcc3565…b96d25
0xf3cc…cbc80x6482…b779BaseBase$0.0001100%daydreams345d ago0xd97a72…b770c0
0xf3cc…cbc80x6482…b779BaseBase$0.0001100%daydreams345d ago0x6f5606…c1fb9b
0xf3cc…cbc80x6482…b779BaseBase$0.0001100%daydreams345d ago0x497518…492c75
0xf3cc…cbc80x6482…b779BaseBase$0.0001100%daydreams345d ago0xb3b4a5…f24dad
0xf3cc…cbc80x6482…b779BaseBase$0.0001100%daydreams345d ago0xf67b4f…04b780
0xf3cc…cbc80x6482…b779BaseBase$0.0001100%daydreams345d ago0x497a67…eac84d
0xf3cc…cbc80x6482…b779BaseBase$0.0001100%daydreams345d ago0x31b5d6…d233f5
0xf3cc…cbc80x6482…b779BaseBase$0.0001100%daydreams345d ago0xbde50f…ba4004
0xf3cc…cbc80x6482…b779BaseBase$0.0001100%daydreams345d ago0xed2224…c1f4f8
0xf3cc…cbc80x6482…b779BaseBase$0.0001100%daydreams346d ago0x785623…1a23a6
0xf3cc…cbc80x6482…b779BaseBase$0.0001100%daydreams346d ago0x035b67…a9413b
0xf3cc…cbc80x6482…b779BaseBase$0.0001100%daydreams346d ago0x59c349…f91095
0xf3cc…cbc80x6482…b779BaseBase$0.0001100%daydreams346d ago0xc3f17b…6e7d80
0xf3cc…cbc80x6482…b779BaseBase$0.0001100%daydreams346d ago0x971315…62406b

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

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

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: 0xf3cc…cbc8

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