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%daydreams352d ago0xd8f505…3f802a
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams352d ago0xc91be7…958d34
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams352d ago0x205e48…02464f
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams352d ago0x37f4a3…2a3289
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams352d ago0x1a2c34…cd2891
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams352d ago0x476f25…f81f5e
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams353d ago0x9148da…bb9650
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams353d ago0x0af823…08534f
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams353d ago0xbdb066…f44069
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams353d ago0xba0850…f8b770
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams354d ago0xdc36a1…34c53a
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams354d ago0x1ae8bc…88af16
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams354d ago0x7463b1…e0d463
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams354d ago0x49e7ef…32a12e
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams355d ago0xa057df…6880de
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams355d ago0xb84778…de784c
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams355d ago0x1e741f…77bd3a
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams355d ago0x477412…433f5f
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams355d ago0xf30570…382303
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams356d ago0xf73408…455c35
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams357d ago0x303cb4…c91570
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams357d ago0x10ce23…889cf4
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams357d ago0xbef10d…5d8fbb
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams357d ago0x63cc84…8c379f
0x545b…649f0x6482…b779BaseBase$0.0001100%daydreams357d ago0x95b853…debe4c

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.