AgentReport

0x545b…649f

0x545bbff8173a093feddec369a42fab5ae448649fExplorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
270
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3066.54M Roundhouse has indexed across 1,400,255 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (270)

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.032701

$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
    270 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.00270276d 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 270 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams341d ago0x2c318e…3ff9d1
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams341d ago0x8f9c15…89db7d
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams341d ago0x529ee3…4d9796
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams341d ago0x0de13a…e7e54f
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams341d ago0xa7e6c7…73d58c
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams341d ago0xa9932c…3e2a8e
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams341d ago0xcfc952…9d5aa9
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams341d ago0x58cb69…84bfce
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams341d ago0x3a03ee…42b06c
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams342d ago0xcbea33…513805
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams342d ago0x4ad6a7…9003a1
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams342d ago0x7ea5a6…2c033f
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams342d ago0x3c8b4e…56207c
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams342d ago0x661f95…d5c553
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams342d ago0x584faf…55551b
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams342d ago0x0405fc…251e1b
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams342d ago0x3392d6…53dd7a
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams342d ago0xb07ce6…cc56c1
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams342d ago0xa54da3…631fe8
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams343d ago0x707d2e…0a860a
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams343d ago0x98bea2…72868b
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams343d ago0x019bfd…29f213
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams343d ago0xaea78a…26c6ad
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams343d ago0x729f6d…65ce9d
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams343d ago0xac4c93…a66eee

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 0x545b…649f has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0x545bbff8173a093feddec369a42fab5ae448649f

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: 0x545b…649f

curl -s 'https://api.roundhouseai.io/v0/agents/0x545bbff8173a093feddec369a42fab5ae448649f'
curl -s 'https://api.roundhouseai.io/v0/entities/0x545bbff8173a093feddec369a42fab5ae448649f/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.