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.17M Roundhouse has indexed across 1,400,092 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%daydreams337d ago0xa96004…42e595
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams337d ago0xd6f951…f981ed
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams337d ago0xe6026e…55d99f
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams338d ago0x38c30e…20a869
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams338d ago0x74c551…a60021
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams339d ago0x338db2…1e828b
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams339d ago0xabf9de…f7e459
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams339d ago0xc911d8…b85056
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams339d ago0xb7e67f…efe1ed
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams339d ago0x0ecc75…08cd98
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams339d ago0x793e4f…ee5fa0
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams339d ago0x507181…fade11
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams340d ago0x822379…1b2686
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams340d ago0xbf8cbe…e9b17d
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams340d ago0x68ecdd…00dfa8
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams340d ago0x365239…11c8cd
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams340d ago0xe0c082…5f39a5
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams340d ago0x01fe52…8bc286
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams340d ago0x1b6764…7d9b6d
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams340d ago0x3037aa…6756b4
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams340d ago0x207119…75ca9a
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams340d ago0xff11dc…02a904
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams340d ago0xd6c5db…93b72a
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams341d ago0x44c9ec…d5272a
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams341d ago0x72e7ca…e3c0bb

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.