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 $3067.84M Roundhouse has indexed across 1,401,919 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%daydreams341d ago0xecdbe2…33a4b1
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams341d ago0xb22154…6d383b
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams341d ago0x558f79…51a0a0
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams342d ago0x934dc8…0e2f64
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams342d ago0x89b418…c9bc7e
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams342d ago0x8de2ef…558b8f
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams342d ago0xb9c5f0…d9cd0e
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams342d ago0xda75b1…ec29cc
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams342d ago0x9fb1a0…40939f
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams342d ago0x638bd8…e9f75f
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams342d ago0x1272d6…f12e7a
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams342d ago0xd17538…bfe835
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams342d ago0x47b467…9d0e9d
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams342d ago0xf6be39…005c77
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams343d ago0x326d0b…268236
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams343d ago0xba2bdd…2248cc
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams343d ago0x6e67f3…03b855
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams343d ago0x47458b…c7dd1e
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams343d ago0x73bc94…119131
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams343d ago0x85a2a7…554987
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams343d ago0x367961…ebe64e
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams343d ago0xc681d2…8ea3f7
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams343d ago0xf4e969…9b0d0e
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams344d ago0xb24228…c01111
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams344d ago0x6f0963…e4e793

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.