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,396 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%daydreams344d ago0x27923b…d5074b
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams344d ago0x9d7bc0…73ac8b
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams344d ago0xf77100…85584e
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams344d ago0x5e5e8e…60c7f4
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams344d ago0xa0a350…42fa78
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams344d ago0xd2bb9f…3fbbb0
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams344d ago0xe669df…54cdeb
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams344d ago0xff68a0…c2d7d7
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams345d ago0xdc61e3…8cef59
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams345d ago0xd4cf8b…4c300e
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams345d ago0xb8ac26…8fbed9
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams345d ago0xa0bc18…856c1f
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams345d ago0x7a6e33…9bcdf7
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams345d ago0x422d27…742a08
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams345d ago0x2d69a2…540c54
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams345d ago0xd84544…157532
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams345d ago0xfa9d23…0a303a
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams345d ago0x859ef7…c482b4
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams345d ago0xb576e1…60a541
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams345d ago0xecebf8…e4da52
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams346d ago0x00cdac…35e172
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams346d ago0x1c3c06…ab5b05
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams346d ago0x429d98…f15ac4
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams346d ago0x64102a…0fca97
0xbcbd…d9d70x6482…b779BaseBase$0.0001100%daydreams346d ago0x2c5519…c6bafe

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.