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%daydreams346d ago0x3863c4…577797
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams346d ago0x002306…6bbefc
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams346d ago0xf66600…158563
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams346d ago0x0ac575…496a51
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams346d ago0x9ba261…f75477
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams346d ago0x42f61c…686422
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams346d ago0x41569a…4f346e
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams346d ago0x7a8af4…8df73d
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams347d ago0x2ef7a1…9ad7fe
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams347d ago0x0e135f…46b0d5
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams347d ago0xf5915f…a65e41
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams347d ago0xc5ede3…4eb19e
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams347d ago0xe5e60b…7e345e
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams347d ago0x713046…75f22c
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams348d ago0xa11905…e1243e
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams348d ago0xc140e6…bb3421
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams348d ago0xb84455…4c967b
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams348d ago0x539d1d…136250
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams348d ago0x5518eb…cefe25
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams348d ago0x7af015…7d0e9b
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams348d ago0x40f5d1…00c73f
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams348d ago0x29d890…4bff90
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams348d ago0x2d5eea…c6ce47
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams348d ago0xc5cb99…04610a
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams348d ago0x7e5a12…ee7799

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.