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%daydreams344d ago0xa53589…dff7ac
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams344d ago0x71f06f…381d2b
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams344d ago0x109ee7…217485
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams344d ago0xecfe69…889a1d
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams344d ago0xd74f28…e7a87f
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams344d ago0x7a58ee…4c285c
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams344d ago0x56e554…d29549
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams344d ago0xb6aeea…3b4c04
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams344d ago0x0832bb…f69991
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams344d ago0xc0f127…0bea50
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams344d ago0x83edb4…735fc7
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams345d ago0x6de546…4b2151
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams345d ago0xa59d9d…69eeda
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams345d ago0xb698c3…3c8161
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams345d ago0x0172b7…2e425e
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams345d ago0x0c63ba…a242b7
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams345d ago0xfbe38e…d408ef
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams345d ago0xeb59c8…c7e296
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams345d ago0x470a79…b3ce20
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams345d ago0xa31765…66705c
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams345d ago0x789548…0a27ca
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams345d ago0x83005c…3d11d5
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams345d ago0xf5fe4a…6efd9c
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams346d ago0x40a1d8…905ee4
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams346d ago0x19ec49…bf083b

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.