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,255 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%daydreams323d ago0xcd5ca2…b57e41
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams323d ago0x79d960…0ac3c0
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams323d ago0x9d94de…ad398c
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams323d ago0x293f62…8699f8
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams323d ago0xa34bbb…6459f2
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams323d ago0x5ac79c…867d95
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams323d ago0x8e6b47…7f75ae
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams323d ago0x5879c6…d31a77
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams324d ago0x039371…43e17e
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams324d ago0x0f31c4…d59563
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams324d ago0xabae28…936848
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams324d ago0x5e5495…59c865
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams324d ago0x899fcd…a1478a
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams324d ago0x47817f…1418c3
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams324d ago0x98c305…032e79
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams324d ago0xc2105e…379f7b
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams324d ago0x01913c…192b41
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams324d ago0x2cc2f5…7f5d2d
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams325d ago0x798b07…7b2bca
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams325d ago0x5753c6…a6cc17
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams325d ago0x649592…a22c94
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams325d ago0xefec3c…e5a9b5
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams325d ago0x490014…36ff69
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams325d ago0x6e974b…ba4573
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams325d ago0x8c0041…53bd62

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.