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%daydreams326d ago0x446b94…9fff0b
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams327d ago0xc35071…8b30e7
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams327d ago0x8ade18…f87216
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams327d ago0xfa5e19…319307
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams327d ago0x035eb0…f1cc0d
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams327d ago0x10b29e…c9eef1
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams327d ago0x55682e…416864
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams327d ago0x1e6706…fce05f
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams327d ago0x0a7363…9fad69
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams328d ago0xe30c02…2ea300
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams328d ago0x9eae42…05bae8
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams328d ago0xd80a03…b71df3
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams328d ago0x1d5d8d…22ef4e
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams328d ago0xf2e022…e10960
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams328d ago0xb04bf6…acb37a
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams336d ago0x46f2d8…e3a886
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams336d ago0x2267f3…fd9edf
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams337d ago0xeeed43…084980
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams337d ago0x59eb87…ea3391
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams337d ago0xd2c643…437894
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams338d ago0x4caa91…b18dab
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams338d ago0xd5f079…54ee43
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams338d ago0xb0d27d…02dbb7
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams338d ago0x37265c…329c3f
0x4c95…18380x6482…b779BaseBase$0.0001100%daydreams338d ago0xd92a7c…8a64b6

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.