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 $3068.58M Roundhouse has indexed across 1,402,722 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%daydreams326d ago0xac25d4…6153c3
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams326d ago0x5eccb4…04c6c7
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams326d ago0xacf605…97b4a6
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams326d ago0xe7d6fa…6cf8d8
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams326d ago0x234ca0…07828b
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams326d ago0x0a3a54…1384e3
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams326d ago0xfe8a21…f65f7d
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams326d ago0x348d86…d6433f
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams327d ago0xf8480d…f74618
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams327d ago0xc2b2dc…677366
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams327d ago0xea6e90…81a58a
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams327d ago0xf59131…054861
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams327d ago0x1e301f…345d37
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams327d ago0x541eae…0f1585
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams327d ago0xacbaaf…efb03b
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams327d ago0x1f2036…cf928a
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams327d ago0x09a85e…561f67
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams328d ago0x14f370…42b096
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams328d ago0x94016e…d52c82
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams328d ago0xf21f07…d0d17d
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams328d ago0x887ebd…6e9a28
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams336d ago0x1dd60e…abacb3
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams337d ago0x4528bb…d5d24e
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams337d ago0xf70ea6…939921
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams337d ago0xe9be3e…c1e6fd

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.