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 $3067.84M Roundhouse has indexed across 1,402,228 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 276d 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.00257276d 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%daydreams326d ago0x784652…32a6c9
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams326d ago0xef2e3e…6c7d34
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams326d ago0x4c968f…2824aa
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams326d ago0xdb2345…45bfe9
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams326d ago0xdbfa7c…8d613f
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams326d ago0x400b74…bcb073
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams327d ago0xe32283…b69d20
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams327d ago0xf59ed8…aa8ffa
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams327d ago0x199591…d406d3
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams327d ago0xf0cbe3…135af7
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams327d ago0xd0a3d6…7d4c05
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams327d ago0x82f9f5…fc84a1
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams327d ago0xe901c4…00a554
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams327d ago0x1730b7…0aaf85
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams328d ago0x9c5971…940cbc
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams328d ago0xfddfe7…2c7d30
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams328d ago0x8af153…7c6d20
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams328d ago0xae5344…102e1f
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams328d ago0x14bb7f…64b72b
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams328d ago0x3b36b9…6c9570
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams336d ago0xaf53a2…9fe26f
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams337d ago0xe4455b…cf7972
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams337d ago0x8e8935…3e77f0
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams337d ago0xc8d374…4410a8
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams337d ago0x4c3b74…6adf11

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.