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.84M Roundhouse has indexed across 1,401,919 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%daydreams346d ago0xa85002…2821af
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams346d ago0x273aee…e4be2a
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams346d ago0xc4b772…02702d
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams346d ago0xfd5611…51d1f5
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams346d ago0x4b42a6…46b8f8
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams346d ago0x40121c…55fdca
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams346d ago0x651174…8c1122
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams346d ago0x6ecbfd…5c1a4d
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams347d ago0xabe045…3717fd
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams347d ago0xd4ad09…79569a
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams347d ago0xd7687d…9e1057
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams347d ago0xcbc1e8…fee479
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams347d ago0xf4bd77…a56882
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams347d ago0x504806…a373bc
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams348d ago0xfa7313…ebdf68
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams348d ago0xf6a138…26937a
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams348d ago0x4da684…abd686
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams348d ago0x2f6abf…151549
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams348d ago0xf05305…e48e45
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams348d ago0x40ba89…9e220c
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams348d ago0x6eb974…4df404
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams348d ago0x930297…4f1540
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams348d ago0x606ee4…3391f5
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams348d ago0x706317…0691e6
0xe195…36470x6482…b779BaseBase$0.0001100%daydreams348d ago0x998e29…21bab3

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.