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,722 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%daydreams353d ago0xabb68d…023d38
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams353d ago0xde283f…d1c167
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams353d ago0xd74168…c6b5e0
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams353d ago0x49edb3…3f8f0b
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams353d ago0x5fa358…40670c
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams353d ago0xe02296…590be4
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams355d ago0x0cf36e…e24461
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams355d ago0x77ca6e…98c9d3
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams355d ago0xde6c62…2a54eb
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams355d ago0xb1cd73…cdd86f
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams356d ago0xb24a0f…e91c15
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams356d ago0x30aae4…3d3343
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams356d ago0x011a78…365ce5
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams356d ago0x84343e…1ae550
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams356d ago0x9fa27c…79abcb
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams356d ago0xda9cb0…1ce1f4
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams357d ago0xc40997…81db37
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams357d ago0x89e273…b4e2d8
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams357d ago0xbd17c0…42c03e
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams357d ago0xeaeec9…924657
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams357d ago0x21a09d…e5820b
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams358d ago0xdad71e…0d162a
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams358d ago0x207a3f…e40342
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams358d ago0x985e3e…bb2900
0xbf64…35360x6482…b779BaseBase$0.0001100%daydreams358d ago0x867917…01a47f

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.