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%daydreams338d ago0xb5718e…a2e3b0
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams338d ago0x59a2cc…a0e2e4
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams338d ago0xc135ee…2507bd
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams339d ago0x14577e…6d1478
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams339d ago0x6276e8…0811b0
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams340d ago0x1270ad…214dd7
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams340d ago0xc62694…5f9b30
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams340d ago0xb02d9e…9a0598
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams340d ago0x5d2c28…fd37b1
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams340d ago0x63fdf2…8a6514
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams340d ago0x6b0c8e…106abd
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams340d ago0x1aec22…f28873
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams340d ago0xc806a4…cf8125
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams340d ago0x383002…accdca
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams340d ago0xc58c7c…08f2ed
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams340d ago0x37048a…add3ff
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams341d ago0xb9833d…e4a318
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams341d ago0xad7822…5b5df2
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams341d ago0x3aa59d…266647
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams341d ago0x12877d…1b1999
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams341d ago0x89036d…29ca46
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams341d ago0x31d4b3…b125cb
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams341d ago0xb6aee4…ef6ce5
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams341d ago0x80f627…a1bbb9
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams341d ago0xde61fc…56e2ec

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.