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%daydreams323d ago0xce1607…fe75a1
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams323d ago0xc10566…29ba74
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams324d ago0x58e59c…d6952f
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams324d ago0x4bb824…871d00
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams324d ago0x235b07…884988
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams324d ago0x98a38b…498a82
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams324d ago0xdb9a23…574cdb
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams324d ago0x9bb835…69f7a5
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams324d ago0x8ecff3…31a623
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams324d ago0xe28d45…63e109
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams324d ago0xc81dfa…4b183d
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams324d ago0xb05603…dd8c41
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams325d ago0x9802e5…d670e2
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams325d ago0xdb8630…f919ec
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams325d ago0x15ebf4…ae742b
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams325d ago0x8f0bf2…e8d3df
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams325d ago0xde3a56…273aef
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams325d ago0x26f970…689468
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams325d ago0x12d844…f400c0
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams325d ago0x35eb4e…0c8943
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams325d ago0x956182…8cfa78
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams325d ago0xca91e9…6a30c2
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams325d ago0xf9b25e…b7de24
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams326d ago0x13b63f…35a447
0xe94b…f03e0x6482…b779BaseBase$0.0001100%daydreams326d ago0x2d7d94…ebbc42

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.