AgentReport

0xe94b…f03e

0xe94b53d8ba89b9886c48434180fddd9cca80f03eExplorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
268
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 (268)

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

$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
    268 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.00268277d 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 268 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams338d ago0x14117a…89249f
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams338d ago0x488227…887fbd
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams338d ago0xc91e7d…0a1822
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams338d ago0xd3d71e…d80925
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams338d ago0x04b350…6b28b9
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams338d ago0xc8c59b…0dc0b4
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams338d ago0x77dd2a…43b033
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams338d ago0x3b08ba…d8526b
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams340d ago0xb30bf7…e8c855
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams340d ago0xc12a60…37781b
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams340d ago0x6c35d7…9af91c
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams340d ago0xe92230…645764
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams340d ago0xdad745…3f3a47
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams340d ago0x1dd9d5…021fee
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams340d ago0x713e62…5833a1
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams340d ago0xe87619…b47ee1
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams340d ago0xc15bb6…28b33f
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams340d ago0xa2cf0d…b29153
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams341d ago0x391a51…f07b07
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams341d ago0xa5be0a…21622c
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams341d ago0xb86199…baac71
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams341d ago0xb09665…611dab
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams341d ago0xa18731…708a9d
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams341d ago0x3449ec…d22569
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams341d ago0x05eaea…4281e3

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

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

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: 0xe94b…f03e

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