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%daydreams341d ago0xb8cf4a…b047eb
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams341d ago0x73be51…d60428
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams341d ago0x0d5bbd…b78a60
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams341d ago0xa8d747…7a6c3b
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams342d ago0x627f10…e9bf02
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams342d ago0xd06c4e…1dc9be
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams342d ago0xc39146…f2b829
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams342d ago0xc4a1ab…0f2c95
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams342d ago0x6b1d2d…35b2bc
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams342d ago0x7a0c05…774499
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams342d ago0x7dfe4f…e249c1
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams342d ago0xd9f2a5…15341a
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams342d ago0x8e56fd…d0af5a
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams342d ago0xacb6eb…2f4532
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams343d ago0xce9043…d9bec6
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams343d ago0x93b2f5…f6c49e
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams343d ago0x8e3dab…f26b6e
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams343d ago0x0ece8d…37c242
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams343d ago0x9f0554…46cfa8
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams343d ago0x07d191…83c3d8
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams343d ago0x6e054d…dcdd6d
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams343d ago0xac3b6a…a58d67
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams343d ago0xeed1e7…0e9778
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams343d ago0xdb396a…8d53c0
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams344d ago0xa96361…b1d7f1

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.