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 $3070.29M Roundhouse has indexed across 1,403,290 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%daydreams338d ago0x42d892…1617f4
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams338d ago0x478dfb…e454d3
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams338d ago0x35fae7…f8fdc1
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams340d ago0x8dd8af…fd2d8a
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams340d ago0x5773d4…3e8b15
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams340d ago0x677270…73432f
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams340d ago0xdaab55…8b1cca
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams340d ago0x3f1940…2a252a
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams340d ago0xe59c63…ac8b01
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams340d ago0xb4594c…cdd6d3
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams340d ago0xe02fce…c1bef1
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams340d ago0x08688a…06c6b2
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams340d ago0xd1602a…28afa8
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams341d ago0xb2e1a4…b0f162
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams341d ago0x50f034…d929d9
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams341d ago0xf2a1a2…b9a001
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams341d ago0xca0ac2…8d9d2c
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams341d ago0xccb065…4cb709
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams341d ago0xe1e692…49a1c7
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams341d ago0x1275f5…05f4b3
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams341d ago0x6ae0f7…62f2ea
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams341d ago0x676b34…c31045
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams341d ago0xc89aa9…a44491
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams342d ago0x1ce853…b70088
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams342d ago0xceeaea…4839be

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.