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%daydreams326d ago0x338ba8…afd457
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams326d ago0x195210…fb6a42
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams326d ago0x2fd282…7c5ad7
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams327d ago0x50d93b…e6ac66
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams327d ago0xce3540…045951
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams327d ago0x1d7398…9e5068
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams327d ago0xb9952f…452557
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams327d ago0xe96fb0…a29490
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams327d ago0xdb116d…771c4c
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams328d ago0x09243b…bec6e7
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams328d ago0xc367db…465436
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams328d ago0x0d92c4…10bd60
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams328d ago0x3765b0…426a52
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams328d ago0x1506c4…afede0
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams328d ago0xb20754…6d4613
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams336d ago0x67b0bd…451e0d
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams337d ago0x3168ec…068e14
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams337d ago0xb029fd…3776e7
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams337d ago0x08514b…00a645
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams337d ago0x2d171d…6a2945
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams338d ago0x98b738…72c65c
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams338d ago0x08833f…da2375
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams338d ago0x217e58…20564a
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams338d ago0x616ec2…cf291b
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams338d ago0xb3855c…4a0860

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.