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 $3067.00M Roundhouse has indexed across 1,400,982 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%daydreams352d ago0xfba8bb…8da2ff
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams352d ago0x6f75b6…5f7ddd
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams352d ago0xdc7bda…ace253
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams352d ago0xd612ed…2677ec
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams352d ago0xc4b3ef…49f4da
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams352d ago0x9eabd1…74e678
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams352d ago0x72edf1…920c3b
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams353d ago0xc40a05…4cb589
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams353d ago0x0cbf69…a586ef
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams353d ago0x39e93f…ae209f
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams353d ago0x042dc1…e11640
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams354d ago0xc67a92…81dce7
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams354d ago0x99b0d9…38b6ed
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams355d ago0xce50c3…06d82e
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams355d ago0x45498b…8b0679
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams355d ago0xe5626e…d7409e
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams355d ago0xfbae0f…a3c4a0
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams356d ago0x3b8c2b…6b1902
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams356d ago0xa8bf3e…34bf74
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams356d ago0xe20903…f54321
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams356d ago0x9ca78a…10fda0
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams357d ago0xa4887c…f6bbcf
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams357d ago0xbfb6be…20c7ce
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams358d ago0x9d67dd…ad7df7
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams358d ago0x25ebea…001b59

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.