AgentReport

0xf39f…61b9

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

Paid $0.03 of the $3068.58M Roundhouse has indexed across 1,402,563 wallets — less than 0.0001% of it.

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

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

$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 276d ago
    $0.03
    280 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.00280276d 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 280 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams348d ago0x4dd916…dc5abb
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams349d ago0x5bce1f…9880c8
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams349d ago0x8add71…530665
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams349d ago0xc4c429…d2691e
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams349d ago0x872747…b9de67
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams349d ago0x702010…cd8892
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams349d ago0x82d0d3…6fb6f8
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams349d ago0x363e4b…096ab4
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams349d ago0x1876f8…989786
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams350d ago0x653318…af4823
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams350d ago0x43c19f…5e0f05
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams350d ago0x0fc066…296464
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams350d ago0xc46645…624a9b
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams350d ago0xac594b…c203c0
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams351d ago0xd2ca23…53ce44
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams351d ago0xaaf3dd…9462f0
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams351d ago0x432d7d…336524
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams351d ago0x5fd275…31ff27
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams351d ago0xbce555…a0a781
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams351d ago0xa96f03…1b42c2
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams351d ago0x07379e…57f2c8
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams352d ago0xe4155a…4f0bc9
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams352d ago0x6619b6…6a3a9a
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams352d ago0x062a5c…de2781
0xf39f…61b90x6482…b779BaseBase$0.0001100%daydreams352d ago0x0e2fdc…b9a933

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

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

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: 0xf39f…61b9

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