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%daydreams352d ago0x54507d…b123de
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams353d ago0x698980…82efff
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams353d ago0xb0e36c…1d4fa0
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams353d ago0xb423d7…de3f1f
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams353d ago0x76b9eb…260a5f
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams353d ago0x021d28…470c53
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams353d ago0xc19127…a8f399
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams353d ago0x772da8…faa8f4
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams353d ago0xa89577…7a25e5
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams354d ago0x77d810…63007d
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams355d ago0xebad7d…6a281c
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams355d ago0xddb61e…8bd077
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams355d ago0x9f50da…c3eb88
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams355d ago0x9e4b9e…d55422
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams356d ago0xb9baf5…150301
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams356d ago0x9614ca…5c5b53
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams357d ago0x2832c7…5b221f
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams357d ago0xd9e7ee…0ef84c
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams357d ago0x6c6edb…a7c25f
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams357d ago0x2a0bf6…fcd403
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams358d ago0x5b9a34…62681e
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams358d ago0x2f47a5…ad31a7
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams359d ago0xf97467…f12519
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams359d ago0x490152…1ce2b2
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams360d ago0xef036b…037240

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.