AgentReport

0xf1bb…3638

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

Paid $0.03 of the $3066.54M Roundhouse has indexed across 1,400,510 wallets — less than 0.0001% of it.

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

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

$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
    262 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.00262276d 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 262 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams337d ago0xb35354…2e50ae
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams337d ago0x6ae7fe…801cc6
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams337d ago0xb82cf4…1bb4ae
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams337d ago0x3c2bbc…977140
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams338d ago0x319be0…8941b9
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams338d ago0xa55166…87d8e8
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams338d ago0xc13ff9…e0ae42
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams339d ago0x26cda6…3ffebc
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams339d ago0xa6312f…85d887
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams339d ago0xd9712e…717767
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams339d ago0xf93358…f41acf
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams339d ago0x162786…106a0b
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams339d ago0x476462…d4a7f6
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams339d ago0xc87bea…a240b7
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams340d ago0x003d2f…11b5fb
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams340d ago0xc7118a…f18448
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams340d ago0x97df28…8f5bf1
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams340d ago0x032a69…e85d94
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams340d ago0x91b7f9…500596
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams340d ago0xec5025…bcd808
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams340d ago0xc8f8ff…e783ca
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams340d ago0x580d22…215ca8
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams340d ago0xcf1670…0ac55a
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams340d ago0x693e09…6745d0
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams340d ago0xeac6b6…33618f

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

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

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: 0xf1bb…3638

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