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%daydreams325d ago0xfe3cc5…5e44ca
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams326d ago0x3a99c4…f27452
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams326d ago0xc635d3…be71b3
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams326d ago0x4bf3e0…0d9dbd
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams326d ago0x1b93ea…4c7732
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams326d ago0x1431a7…753c21
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams326d ago0xa1cab5…f6c587
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams326d ago0x28aa7e…d0df3d
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams326d ago0x10ce34…582fb1
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams326d ago0xfc2bde…7e2288
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams327d ago0xc20683…13b2df
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams327d ago0x6b12b5…278e56
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams327d ago0x17c338…8ee810
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams327d ago0xf0868f…2b54e0
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams327d ago0x60f7b6…b2daa5
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams327d ago0x34a969…b93c2d
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams327d ago0xf52fbe…3dcdab
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams328d ago0x913ed7…60eb39
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams335d ago0x854a26…073f71
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams337d ago0x1c1d34…351652
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams337d ago0xf1ef18…ee223e
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams337d ago0xee1a60…f49590
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams337d ago0x9587f2…b78537
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams337d ago0xf077ac…466f6c
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams337d ago0x1b6ca4…2fa1e0

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.