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%daydreams353d ago0xb1aefd…60c8f9
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams353d ago0x230947…3b05a2
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams353d ago0x22213b…65d51f
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams353d ago0x45ce8c…1ef171
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams353d ago0xd3937d…7d96df
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams353d ago0xcaf8b6…3c69f5
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams353d ago0x30b2af…27b4f1
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams354d ago0xd1ded5…59f37c
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams354d ago0x237ee3…bf4372
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams355d ago0xbf2a72…89b91f
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams355d ago0x661686…09cbc1
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams355d ago0xd6844f…edb8d5
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams355d ago0xb5d818…509444
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams356d ago0x902a1b…17a30a
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams356d ago0xd0c0db…c021d0
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams356d ago0x156b92…e60d79
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams356d ago0x570770…ec69b2
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams356d ago0xf4cc5a…79d5c8
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams357d ago0x8fd256…32f721
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams357d ago0x84c391…82d8f8
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams357d ago0x0de106…ac2d66
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams357d ago0x2b246c…091e5d
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams357d ago0xe69683…bf0c21
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams357d ago0x97a064…8c27ff
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams357d ago0xeceb83…137e74

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.