AgentReport

0x4c95…1838

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

Paid $0.03 of the $3069.68M Roundhouse has indexed across 1,403,034 wallets — less than 0.0001% of it.

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

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

$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
    260 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.00260277d 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 260 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams324d ago0xe478c5…73538f
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams324d ago0xd7ae5a…8c2760
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams324d ago0x3f88db…0435c6
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams324d ago0x804fa2…545713
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams324d ago0x106675…480c1b
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams324d ago0x851ef7…e005ba
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams325d ago0x32df17…4f6aed
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams325d ago0xf4947a…d73f27
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams325d ago0x827cf4…4a94de
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams325d ago0x80bf51…b04362
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams325d ago0x6bd348…a90544
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams325d ago0x20df4a…305a54
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams325d ago0x1f4001…288a52
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams325d ago0x103ee5…4ced66
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams325d ago0x37a297…dbf48f
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams325d ago0xd421e7…837769
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams325d ago0x9f9b3a…953350
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams326d ago0x823dd7…8e28f0
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams326d ago0xa5d05e…f62dfa
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams326d ago0xb85652…e77fa8
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams326d ago0x8eb485…762907
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams326d ago0xfc64f4…b1cdd1
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams326d ago0x055ccc…62f24a
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams326d ago0x084323…d9ef51
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams326d ago0x3a3ecf…e1cb1b

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

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

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: 0x4c95…1838

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