AgentReport

0xbf64…3536

0xbf6456efa95df362f3f2258a15475dfb32473536Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
257
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 (257)

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.032571

$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
    257 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.00257277d 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 257 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams349d ago0x292cf7…49af37
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams349d ago0x00beda…f2ffae
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams349d ago0x010094…fd0b4e
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams349d ago0x59c9cb…7eac72
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams349d ago0xb74d7a…f004fb
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams350d ago0xd7d532…ff794a
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams350d ago0xc5d49f…50b09b
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams350d ago0xee897f…a696c4
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams350d ago0x722290…23b0a0
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams350d ago0xd9aa26…b42dd4
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams351d ago0xe124ba…49d5a8
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams351d ago0x05fae3…8bc4e3
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams351d ago0x42c7c1…7d65a7
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams351d ago0x7de2b3…4afaf3
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams351d ago0x0e93a1…fe5071
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams351d ago0xb108c0…315890
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams352d ago0xe44268…00ab48
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams352d ago0xb59bcb…72080a
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams352d ago0x359361…a34895
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams352d ago0xb7e968…4c3338
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams352d ago0x3a7a16…fb709f
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams352d ago0xd02ba9…8c45b4
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams352d ago0xa44d56…e8e1fc
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams352d ago0xf0fb1b…0b944b
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams353d ago0xbd4cb7…af3234

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 0xbf64…3536 has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0xbf6456efa95df362f3f2258a15475dfb32473536

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: 0xbf64…3536

curl -s 'https://api.roundhouseai.io/v0/agents/0xbf6456efa95df362f3f2258a15475dfb32473536'
curl -s 'https://api.roundhouseai.io/v0/entities/0xbf6456efa95df362f3f2258a15475dfb32473536/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.