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%daydreams349d ago0x90df3a…7035a9
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams349d ago0xd3dd3c…3f76fb
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams349d ago0xd76a65…6cce78
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams349d ago0x262f6c…5faac7
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams349d ago0x1a1640…a6737b
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams350d ago0x28e327…a03984
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams350d ago0xd9eb70…707841
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams350d ago0x82d112…921450
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams350d ago0x918736…9cf442
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams350d ago0x2061c8…b61932
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams351d ago0x7178a5…14671d
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams351d ago0xdf2244…16edf5
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams351d ago0x5ad010…d20a02
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams352d ago0x578678…5e1fc9
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams352d ago0x42ba40…3f033a
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams352d ago0xbe5cd5…ed9b7c
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams352d ago0x614585…816417
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams352d ago0x237d2b…688916
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams352d ago0xa0c892…1ed05a
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams352d ago0x976ca5…d57154
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams352d ago0x2e2e8d…7dbdc4
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams352d ago0x7cbea8…67918d
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams353d ago0x49b88a…d7edc4
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams353d ago0x9ca6d2…f107fe
0x54da…02620x6482…b779BaseBase$0.0001100%daydreams353d ago0x7bbc0c…b38f66

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.