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 $3068.58M Roundhouse has indexed across 1,402,722 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%daydreams346d ago0x7a2ffd…0944dc
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams346d ago0xf38570…b7beff
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams346d ago0x7ba12d…2deb2a
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams346d ago0x77215c…a2af59
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams347d ago0x3a7d9b…201062
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams347d ago0xd9758d…871922
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams347d ago0xf0cd4a…6edd1e
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams347d ago0x0e98e1…bd3223
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams347d ago0xb0f118…ee2f16
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams347d ago0xb8e258…d6e839
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams347d ago0x292439…446611
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams347d ago0xb1ac7b…bc0dc2
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams348d ago0xe8528b…8ca48d
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams348d ago0xfa5fa8…20c84b
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams348d ago0x6a3af2…528884
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams348d ago0xa91dbd…5366eb
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams348d ago0x6db61a…785222
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams348d ago0x595834…b44632
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams348d ago0x7bd17d…912739
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams348d ago0xa348f0…d13ccf
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams348d ago0xc3cd8a…50b1c8
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams348d ago0xee97d3…602c71
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams349d ago0x337029…f02282
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams349d ago0xef3e4c…b16f02
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams349d ago0x20178c…a44c7c

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.