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%daydreams345d ago0xc5ae60…d1e380
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams345d ago0x48d0b9…ceb7c7
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams346d ago0xc6d838…eeb47e
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams346d ago0xd16528…de7a77
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams346d ago0x0536dd…7e3831
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams346d ago0xf835fb…62cb66
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams346d ago0xb4849b…eb5366
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams346d ago0xa8669a…c308db
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams346d ago0x8de1cc…ce444d
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams346d ago0xc09b87…8acff5
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams346d ago0xb3902a…fcde7b
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams346d ago0xe6fdb7…a2fc95
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams346d ago0xf77a15…c207e2
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams347d ago0x32634a…eddb10
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams347d ago0x72f111…bf4956
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams347d ago0xdb23ea…9fb9f6
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams347d ago0x0189e7…d7c17b
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams347d ago0xa7c7a3…3f68b1
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams347d ago0xf56e91…96e226
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams348d ago0xa5d239…e88c6d
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams348d ago0x3f173f…d2730c
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams348d ago0x648b20…bff821
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams348d ago0x6e4889…534e36
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams348d ago0x69f20d…54b267
0xf1bb…36380x6482…b779BaseBase$0.0001100%daydreams348d ago0x6207e2…fb4969

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.