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%daydreams344d ago0x58d4be…3369a2
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams344d ago0xde45ae…d888b6
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams344d ago0xea4eba…a37e50
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams344d ago0x4c6e0b…8725f0
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams344d ago0xdad000…4841a9
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams344d ago0x4ab8e7…44d48d
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams344d ago0xc05b05…cf50d9
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams344d ago0x160439…c1747c
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams344d ago0x8fa2d1…fb99ea
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams344d ago0x9e56d1…3a536c
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams345d ago0x27d461…493a4c
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams345d ago0x58ef20…c6bdc1
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams345d ago0x502edc…749512
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams345d ago0x92001e…97f4df
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams345d ago0x661953…6dc90d
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams345d ago0x9ff2ae…18f794
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams345d ago0x9694a5…b138cb
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams345d ago0xe99151…8c1cff
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams345d ago0x2cfdf7…68dcb8
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams345d ago0x6ee9a2…07481a
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams345d ago0x95c0b6…d31355
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams345d ago0x589db1…cf3b9c
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams346d ago0xb468c8…4be4c7
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams346d ago0x7d9c57…2dd619
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams346d ago0x022c8c…d33937

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.