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,396 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%daydreams338d ago0xdca62c…3ec1d0
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams338d ago0x85279b…1c5a76
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams338d ago0xde3a70…e8fe2d
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams338d ago0xa5da1f…3d6d78
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams338d ago0x5abe94…0cda41
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams338d ago0x4ba45b…f6f8d4
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams338d ago0x89a0de…53586a
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams338d ago0x9f53fc…32aa65
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams339d ago0xdc38ec…4db1c9
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams340d ago0x4fed5b…958a79
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams340d ago0xeccd3f…56543f
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams340d ago0x58f683…5c0c39
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams340d ago0xc593e9…4cdb84
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams340d ago0x0818ed…9d32f2
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams340d ago0xb7a37b…96233b
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams340d ago0xdc5663…a4f51b
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams340d ago0xfc1e14…7aad1f
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams340d ago0xcc1ff5…9f20f5
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams340d ago0x561f6d…6f749d
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams340d ago0xc12e8f…33446a
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams340d ago0x0698cd…cbc6f8
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams341d ago0xa35a3b…dbd9e5
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams341d ago0xbf2e88…932c8b
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams341d ago0x3021a0…43b18a
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams341d ago0x4fcde8…0f8717

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.