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,689 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%daydreams343d ago0x98e2d1…a8d2a8
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams343d ago0x907a64…83028d
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams343d ago0x6884de…430bae
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams343d ago0xccba82…699aad
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams343d ago0x074b83…96dd9b
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams344d ago0x217daa…da2dec
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams344d ago0x82c88b…94c7d4
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams344d ago0xf4dc85…581596
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams344d ago0x8e58e2…56c778
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams344d ago0x16cd06…1e5013
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams344d ago0x2c3299…53d924
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams344d ago0x25dd1e…79956a
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams344d ago0x9deae9…858eca
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams344d ago0x56df82…ae4ea0
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams344d ago0x59f948…136ef2
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams344d ago0xad7d05…1e4453
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams345d ago0xe5acb4…282245
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams345d ago0x9782c8…09ef1c
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams345d ago0xffb06e…f3e2c4
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams345d ago0xb1a447…13bc2e
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams345d ago0x27cdfe…0ae971
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams345d ago0xfc8887…affa22
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams345d ago0x693716…0a2374
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams345d ago0x5b8403…eb1e3e
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams345d ago0xef45ae…5d9593

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.