AgentReport

0xbb96…2ca8

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

Paid $0.03 of the $3069.68M Roundhouse has indexed across 1,403,034 wallets — less than 0.0001% of it.

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

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

$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 277d ago
    $0.03
    263 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.00263277d 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 263 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams349d ago0x2ced34…ac0097
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams349d ago0x86a2f5…984d4d
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams349d ago0xbe94ce…4b9e00
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams350d ago0x225302…d14d0e
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams350d ago0xe812c0…08dbb3
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams350d ago0x27d0ba…2215ed
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams350d ago0x1fbfaa…30c7e1
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams350d ago0x3761bd…2da983
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams350d ago0xa4a7ac…f31a3f
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams350d ago0xc3cf56…4b78c9
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams351d ago0xe26b21…a246be
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams351d ago0xbc6b9c…eff5e6
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams351d ago0x8e6f62…e3ab47
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams351d ago0xb47d35…cb95af
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams351d ago0x5b7045…963b79
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams351d ago0xafe32b…658287
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams351d ago0xa58410…4422b4
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams352d ago0xad1ca1…964124
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams352d ago0x33e3f8…6d0e88
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams352d ago0xe49c90…62d8bd
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams352d ago0x857686…3ff05c
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams352d ago0xf544cf…902085
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams352d ago0x37fc77…a8aa35
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams352d ago0xbceabb…887928
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams352d ago0x532c8a…40605e

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

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

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: 0xbb96…2ca8

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