AgentReport

0xf95a…95c5

0xf95a4a53bdcb98c190c92ee5641a9545349d95c5Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
270
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,396 wallets — less than 0.0001% of it.

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

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

$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
    270 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.00270276d 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 270 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf95a…95c50x6482…b779BaseBase$0.0001100%daydreams352d ago0x39663e…5a45fe
0xf95a…95c50x6482…b779BaseBase$0.0001100%daydreams352d ago0x0b6cd5…4c97f7
0xf95a…95c50x6482…b779BaseBase$0.0001100%daydreams352d ago0x356c8d…58d62a
0xf95a…95c50x6482…b779BaseBase$0.0001100%daydreams352d ago0x024a90…4338e1
0xf95a…95c50x6482…b779BaseBase$0.0001100%daydreams352d ago0xde5fda…72f68b
0xf95a…95c50x6482…b779BaseBase$0.0001100%daydreams353d ago0x845a85…4f3df1
0xf95a…95c50x6482…b779BaseBase$0.0001100%daydreams353d ago0xa8e235…bca885
0xf95a…95c50x6482…b779BaseBase$0.0001100%daydreams353d ago0xf0170d…71183a
0xf95a…95c50x6482…b779BaseBase$0.0001100%daydreams353d ago0xf5296f…30c997
0xf95a…95c50x6482…b779BaseBase$0.0001100%daydreams353d ago0x5ccb71…0b35fa
0xf95a…95c50x6482…b779BaseBase$0.0001100%daydreams353d ago0x508194…5b3bfc
0xf95a…95c50x6482…b779BaseBase$0.0001100%daydreams354d ago0x171102…1a917b
0xf95a…95c50x6482…b779BaseBase$0.0001100%daydreams355d ago0x1066de…aedc7b
0xf95a…95c50x6482…b779BaseBase$0.0001100%daydreams355d ago0xe84012…e57d95
0xf95a…95c50x6482…b779BaseBase$0.0001100%daydreams355d ago0x68fc62…e0e264
0xf95a…95c50x6482…b779BaseBase$0.0001100%daydreams355d ago0x87dcc3…353635
0xf95a…95c50x6482…b779BaseBase$0.0001100%daydreams356d ago0x268f63…de1227
0xf95a…95c50x6482…b779BaseBase$0.0001100%daydreams356d ago0x0e11aa…028c57
0xf95a…95c50x6482…b779BaseBase$0.0001100%daydreams356d ago0xe4680c…f66ec5
0xf95a…95c50x6482…b779BaseBase$0.0001100%daydreams356d ago0x1ae4b1…74ceb2
0xf95a…95c50x6482…b779BaseBase$0.0001100%daydreams356d ago0xca916e…ba8b24
0xf95a…95c50x6482…b779BaseBase$0.0001100%daydreams356d ago0xa654d0…9432dd
0xf95a…95c50x6482…b779BaseBase$0.0001100%daydreams357d ago0x65ea78…bb88ab
0xf95a…95c50x6482…b779BaseBase$0.0001100%daydreams357d ago0xa8217b…347866
0xf95a…95c50x6482…b779BaseBase$0.0001100%daydreams357d ago0xb6a4a4…610dbd

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

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

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: 0xf95a…95c5

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