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%daydreams324d ago0x219476…354929
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams324d ago0x650562…dca280
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams324d ago0xd4addf…75f655
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams324d ago0x73b7e3…ffd5e6
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams324d ago0x931ef1…2d4f38
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams324d ago0x569678…11376d
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams324d ago0x922e21…d94571
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams324d ago0xc17cfd…7bf82d
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams324d ago0x03995d…865f61
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams325d ago0x947cef…9df10c
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams325d ago0xad5e34…fa1b34
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams325d ago0x5c8d93…888cee
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams325d ago0x7c3607…4a05d6
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams325d ago0xad78dd…c00ecc
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams325d ago0x8cc6f1…114a8b
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams325d ago0xb4356a…4264c3
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams325d ago0x72c52a…829ad0
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams325d ago0xb5eae4…ffa9bb
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams325d ago0x0075f0…f1df1c
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams325d ago0x244408…d8cb4d
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams325d ago0x7a6ea4…420ba1
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams326d ago0x23ba16…8ecf83
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams326d ago0x4c73b5…919149
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams326d ago0x2e0955…8574b2
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams326d ago0x5ce702…ec0b1d

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.