AgentReport

0xbcbd…d9d7

0xbcbdf264b7330f47808ce9b2f46bc1ccd4ffd9d7Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
277
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 (277)

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

$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
    277 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.00277277d 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 277 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams349d ago0x9b6762…1c4c22
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams349d ago0x6dd627…539673
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams349d ago0x1ec472…786327
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams349d ago0xd7d749…94eb2a
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams349d ago0x25d0f9…e4dad5
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams350d ago0xddcd93…bddddc
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams350d ago0xa0adcc…0a1168
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams350d ago0x9e33d0…00fa87
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams350d ago0x21aae3…e721ee
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams350d ago0xa130b5…c4aa5a
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams350d ago0x6c6ac4…b6d948
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams350d ago0x0ed15b…c3d348
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams351d ago0x8340b3…4db4b1
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams351d ago0x35b3ff…f582b3
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams351d ago0x3fd07f…10b62b
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams351d ago0x306a22…957786
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams351d ago0x0d78e5…866927
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams352d ago0x8971a9…82549d
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams352d ago0xdfed15…0a38f5
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams352d ago0x410507…d2fc68
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams352d ago0x9cabf6…1a8a8b
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams352d ago0xbbaf29…6d5098
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams352d ago0x5c0e37…17b76c
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams352d ago0x4daef5…aab96b
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams352d ago0xab0b6f…29ed90

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

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

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: 0xbcbd…d9d7

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