AgentReport

0x54da…0262

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

Paid $0.03 of the $3068.58M Roundhouse has indexed across 1,402,563 wallets — less than 0.0001% of it.

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

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

$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 277d ago
    $0.03
    258 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.00258277d 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 258 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams353d ago0xb68072…cbdd21
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams353d ago0x8248d9…e4da5b
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams353d ago0xc571e8…872dca
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams353d ago0x831632…208805
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams353d ago0xc863b7…e12f82
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams354d ago0x8f62ec…9ac5b3
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams355d ago0xcbba1f…0f9c6d
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams355d ago0x251038…252aa4
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams355d ago0x033ce9…53ebd1
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams355d ago0xd4725d…8326be
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams355d ago0x27cc01…4e0e57
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams356d ago0x9db3e3…d19f0e
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams356d ago0x83d4fe…1af4b6
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams356d ago0x61d2c5…b0cf67
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams357d ago0x2c127d…9d10fa
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams358d ago0x5f4429…856580
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams358d ago0x8c9d30…7d8cfd
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams358d ago0xefbb28…f9adc1
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams358d ago0x76ff4f…032cca
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams358d ago0x286159…7969f1
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams358d ago0xe7d550…d40ff0
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams360d ago0x9a59e9…e1f28b
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams360d ago0x7eb039…11bb8f
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams360d ago0x40b77f…1e0187
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams360d ago0x107faa…07b752

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

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

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: 0x54da…0262

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