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%daydreams342d ago0xa7962c…04e48f
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams342d ago0x7e35e6…b50bb3
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams342d ago0x73a21c…dd3434
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams342d ago0xf74511…9aa8cd
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams342d ago0x7ba987…cc64e7
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams342d ago0x42ad5f…1ef875
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams342d ago0x87f299…e4de8d
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams342d ago0xffc643…6aaf47
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams342d ago0x3686a8…aabc9a
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams343d ago0xa646c1…a65461
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams343d ago0x8efe74…0843a1
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams343d ago0x29a220…cc0eff
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams343d ago0x2d36a2…8d3e8c
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams343d ago0xe33ee7…a588ae
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams343d ago0xc998bc…128b7b
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams343d ago0xe9f237…cce7c1
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams343d ago0x0d8ff9…ceb9c0
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams343d ago0xf2c232…1282e6
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams344d ago0xe6702b…339907
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams344d ago0x609265…21f59a
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams344d ago0x419204…1714c3
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams344d ago0xf85e7c…17a31c
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams344d ago0x5aa137…228fa5
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams344d ago0x6aa81a…62b76f
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams344d ago0x16d836…abe99f

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.