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,563 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 276d 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.00263276d 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%daydreams326d ago0x509ba6…f882f3
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams326d ago0xa92a87…959e86
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams326d ago0x3db9e3…454e87
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams326d ago0x1728cd…56053c
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams326d ago0xf12095…1ee8f5
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams326d ago0x382645…4bda3f
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams326d ago0x89eae5…0e6d03
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams327d ago0xfbe374…5a860d
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams327d ago0x6ed036…d1737d
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams327d ago0x6118b2…0d02f8
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams327d ago0x816863…19fd63
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams327d ago0xab956f…a9a9d2
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams327d ago0x950252…68bb25
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams327d ago0xeefc16…d4b731
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams327d ago0xd40658…0b0473
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams328d ago0x254a1b…000ae8
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams328d ago0x6f5a0f…24eaf5
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams328d ago0xb2436f…b368ee
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams328d ago0x05ea7e…134fe4
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams328d ago0x6b0147…ffc4ad
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams336d ago0xd3425d…291cd6
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams337d ago0x693f37…b8eded
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams337d ago0x93a0e5…1b26e2
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams337d ago0xf0013c…327de8
0xbb96…2ca80x6482…b779BaseBase$0.0001100%daydreams338d ago0xa7579b…80609e

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.