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 $3067.84M Roundhouse has indexed across 1,402,228 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 276d 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.00277276d 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%daydreams324d ago0x018c06…2b2bc3
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams324d ago0x305763…67ee61
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams324d ago0x2b5ec2…9a640b
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams324d ago0xe68577…e5a8aa
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams324d ago0xd023b3…9df92d
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams324d ago0x9b2435…3311ba
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams324d ago0x97d273…b144e9
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams324d ago0x9737bb…5eed9d
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams324d ago0xac3f25…380ca7
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams325d ago0x1d17c4…9de196
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams325d ago0x0a2b7d…0b57ce
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams325d ago0xd38e35…09146c
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams325d ago0x2efd4a…ac9efe
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams325d ago0xcd85f0…0fe71c
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams325d ago0x50ee03…56cb3b
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams325d ago0x163b10…20e7a3
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams325d ago0xf54b8a…0ded0d
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams325d ago0x2f030e…604c3a
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams326d ago0x968c78…8547b2
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams326d ago0x6f3c06…92536a
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams326d ago0x809add…2921f1
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams326d ago0x45ae05…216677
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams326d ago0x4e985a…10bdd4
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams326d ago0x08bc85…c1c235
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams326d ago0x08cffd…aa37ac

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.