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%daydreams348d ago0x1dc9e9…448723
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams348d ago0x8e74cc…48b8cd
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams348d ago0x684e30…bb0757
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams348d ago0x5701fc…23fd50
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams348d ago0xaa0b1e…5eb280
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams349d ago0x861327…7c5813
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams349d ago0x868757…10aac3
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams349d ago0x2837dd…022ebd
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams349d ago0x8a6701…718f8c
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams350d ago0x1e967a…1723af
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams350d ago0x84db1a…bb9e0e
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams350d ago0xdb9587…0e64e4
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams350d ago0x9baa98…2b9460
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams350d ago0x342d0f…bbab5c
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams350d ago0x855099…c52021
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams351d ago0x01ca4d…09bc60
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams351d ago0x191567…c69910
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams351d ago0xebc0c3…43c622
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams351d ago0xbbb51a…20bfed
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams351d ago0x1e0d8e…dcbc3c
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams351d ago0xeef8fe…8f1c17
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams352d ago0x0f0622…d13a16
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams352d ago0xe3a9dd…74f25c
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams352d ago0xdce9b4…6a0e6d
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams352d ago0xe72a7f…d4d24c

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.