AgentReport

0xbb9f…92a6

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

Paid $0.03 of the $3067.43M Roundhouse has indexed across 1,401,742 wallets — less than 0.0001% of it.

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

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

$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
    270 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.00270276d 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 270 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xbb9f…92a60x6482…b779BaseBase$0.0001100%daydreams326d ago0xf54c63…0ef213
0xbb9f…92a60x6482…b779BaseBase$0.0001100%daydreams326d ago0xbc90f3…db92ee
0xbb9f…92a60x6482…b779BaseBase$0.0001100%daydreams326d ago0x57a095…1d4e8e
0xbb9f…92a60x6482…b779BaseBase$0.0001100%daydreams326d ago0x15d822…0cf9db
0xbb9f…92a60x6482…b779BaseBase$0.0001100%daydreams326d ago0xf1ee3b…565587
0xbb9f…92a60x6482…b779BaseBase$0.0001100%daydreams326d ago0x110f4c…ea3f9e
0xbb9f…92a60x6482…b779BaseBase$0.0001100%daydreams326d ago0x7680c8…eef442
0xbb9f…92a60x6482…b779BaseBase$0.0001100%daydreams326d ago0xf4284f…4bf6db
0xbb9f…92a60x6482…b779BaseBase$0.0001100%daydreams326d ago0xfab90a…a7ab11
0xbb9f…92a60x6482…b779BaseBase$0.0001100%daydreams327d ago0xfaea39…f64b1b
0xbb9f…92a60x6482…b779BaseBase$0.0001100%daydreams327d ago0x096199…15a222
0xbb9f…92a60x6482…b779BaseBase$0.0001100%daydreams327d ago0xfb3325…cfd841
0xbb9f…92a60x6482…b779BaseBase$0.0001100%daydreams327d ago0x93c2d5…5d9320
0xbb9f…92a60x6482…b779BaseBase$0.0001100%daydreams327d ago0xc8dfde…a348a9
0xbb9f…92a60x6482…b779BaseBase$0.0001100%daydreams327d ago0x686ab3…6c1652
0xbb9f…92a60x6482…b779BaseBase$0.0001100%daydreams327d ago0x35c9e5…4af68c
0xbb9f…92a60x6482…b779BaseBase$0.0001100%daydreams327d ago0x0ebed8…ace0da
0xbb9f…92a60x6482…b779BaseBase$0.0001100%daydreams328d ago0x0c943c…776c58
0xbb9f…92a60x6482…b779BaseBase$0.0001100%daydreams328d ago0xbd11f5…c5634c
0xbb9f…92a60x6482…b779BaseBase$0.0001100%daydreams328d ago0x6365e7…b8b9ec
0xbb9f…92a60x6482…b779BaseBase$0.0001100%daydreams328d ago0xe2404e…680859
0xbb9f…92a60x6482…b779BaseBase$0.0001100%daydreams328d ago0xcb4f39…883f74
0xbb9f…92a60x6482…b779BaseBase$0.0001100%daydreams335d ago0xf9a1ee…1c967e
0xbb9f…92a60x6482…b779BaseBase$0.0001100%daydreams337d ago0x501ce7…9643dd
0xbb9f…92a60x6482…b779BaseBase$0.0001100%daydreams337d ago0x828801…d26a44

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

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

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: 0xbb9f…92a6

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