AgentReport

0xe195…3647

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

Paid $0.03 of the $3067.43M Roundhouse has indexed across 1,401,742 wallets — less than 0.0001% of it.

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

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

$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 276d ago
    $0.03
    262 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.00262276d 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 262 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams338d ago0x7c31a3…0ecce5
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams338d ago0xf8c8a0…6d801e
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams338d ago0x502ec2…17ae7d
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams338d ago0xadcf58…9e437a
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams339d ago0x4fb798…7b2ed4
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams339d ago0x69d536…d1d4b7
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams339d ago0x7338b9…7f92ff
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams340d ago0x6e8cb2…3e7e56
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams340d ago0xb5aa04…790204
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams340d ago0xe6b519…7fdb2a
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams340d ago0x18eb24…e225ae
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams340d ago0x4f002e…a73096
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams340d ago0xa5a8e3…705c1d
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams340d ago0x4ffe62…33ebf8
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams340d ago0x35397d…7b73e4
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams340d ago0xec6f4b…e13baf
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams340d ago0xc2f8ad…ed3ee4
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams340d ago0xa092f4…c5de71
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams341d ago0x38f2ea…14e9bd
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams341d ago0x87f964…7665b0
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams341d ago0xdf53e9…514403
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams341d ago0xfe6326…de0cb9
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams341d ago0x7d57e0…331403
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams341d ago0x5cdeaa…66d518
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams341d ago0xce5fc4…63fa07

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

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

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: 0xe195…3647

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