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,396 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 276d 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.00258276d 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%daydreams344d ago0xe16305…20fbb4
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams344d ago0x3f0b4a…df88ef
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams344d ago0x56f6e5…fb4687
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams344d ago0xc4a9c0…81867a
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams344d ago0x55f691…bbf486
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams344d ago0x8f9aaa…d44206
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams344d ago0x9abf27…db0d66
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams344d ago0x6b7b52…aa10bf
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams345d ago0x849345…b397a4
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams345d ago0x031599…88ccf8
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams345d ago0xc8f3ff…35e02a
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams345d ago0x9e84b2…547182
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams345d ago0x7d5d04…d2672d
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams345d ago0x54d3d2…b9ffab
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams345d ago0xaf29be…b1d43d
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams345d ago0xc19d9c…5999e2
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams345d ago0xcde17b…0e4687
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams345d ago0x769f9e…3a8d6c
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams345d ago0xc0d65b…c21863
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams345d ago0x055bec…e4df8d
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams346d ago0xb09ae6…55547a
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams346d ago0x352154…e94776
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams346d ago0x875acb…07aa6b
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams346d ago0x77ee39…c99796
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams346d ago0xd0a62f…bead73

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.