AgentReport

0xe4ed…c1e3

0xe4ed6378fa7e45860a285911e065ad2dee1bc1e3Explorer
Paid out
$33.90
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
21630
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $33.90 of the $261.15M Roundhouse has indexed across 716,924 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (1000)

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%$3.501,0002

Every merchant paid publishes at least one catalogued endpoint.

Services it paid

A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; for 2 of 2 the amount paid narrows the list to the ones listed at that price.

Folded from this wallet's 1,000 most recent settlements of 21,630 lifetime, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not.

Balance now
Reading the chain…
Spending power
Reading the chain…
Burn rate
Reading the chain…
Runway
Reading the chain…

Funds flow over time

Activity

MarAprMayJunJulAugSep
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x0495…eed9$2.12$0.00862225d agoGraph
0x8324…fd0e$1.38$0.00138238d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

61% of observed volume is with a single counterparty, in the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap).

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xe4ed…c1e30x0495…eed9Base$0.01100%payAI225d ago0x754153…4ae750
0xe4ed…c1e30x0495…eed9Base$0.01100%payAI225d ago0xdd9ab4…5ddf6d
0xe4ed…c1e30x0495…eed9Base$0.01100%payAI225d ago0x9a89fc…983906
0xe4ed…c1e30x0495…eed9Base$0.01100%payAI225d ago0xfd7006…ede665
0xe4ed…c1e30x0495…eed9Base$0.10100%payAI225d ago0xea43c7…c5f641
0xe4ed…c1e30x0495…eed9Base$0.10100%payAI225d ago0xe04bce…3e9995
0xe4ed…c1e30x0495…eed9Base$0.10100%payAI225d ago0x6cf003…00c00d
0xe4ed…c1e30x0495…eed9Base$0.10100%payAI225d ago0xde5544…3982dd
0xe4ed…c1e30x0495…eed9Base$0.10100%payAI225d ago0x66be6c…ed4bff
0xe4ed…c1e30x0495…eed9Base$0.10100%payAI225d ago0x66be6c…ed4bff
0xe4ed…c1e30x0495…eed9Base$0.10100%payAI225d ago0x3bef0f…5bffdb
0xe4ed…c1e30x0495…eed9Base$0.10100%payAI225d ago0x62a86a…47a08e
0xe4ed…c1e30x0495…eed9Base$0.10100%payAI225d ago0x42a32d…664a8f
0xe4ed…c1e30x0495…eed9Base$0.10100%payAI225d ago0x9aa55d…24d52f
0xe4ed…c1e30x0495…eed9Base$0.10100%payAI225d ago0x1161d7…652e20
0xe4ed…c1e30x0495…eed9Base$0.10100%payAI225d ago0xc751fa…e34a1f
0xe4ed…c1e30x0495…eed9Base$0.10100%payAI225d ago0xe36a77…b3a4c7
0xe4ed…c1e30x0495…eed9Base$0.10100%payAI225d ago0xb9591d…a2bfca
0xe4ed…c1e30x0495…eed9Base$0.10100%payAI225d ago0x0ec21a…fa2252
0xe4ed…c1e30x0495…eed9Base$0.10100%payAI225d ago0xd8f01d…c12e29
0xe4ed…c1e30x0495…eed9Base$0.10100%payAI225d ago0x2fe2d2…e983a1
0xe4ed…c1e30x0495…eed9Base$0.10100%payAI225d ago0x0a979b…fa8330
0xe4ed…c1e30x0495…eed9Base$0.10100%payAI225d ago0xbfef43…2360b6
0xe4ed…c1e30x0495…eed9Base$0.10100%payAI225d ago0x271b9e…a63002
0xe4ed…c1e30x0495…eed9Base$0.0001100%payAI238d ago0x7aa92a…e88a23

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

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

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: 0xe4ed…c1e3

curl -s 'https://api.roundhouseai.io/v0/agents/0xe4ed6378fa7e45860a285911e065ad2dee1bc1e3'
curl -s 'https://api.roundhouseai.io/v0/entities/0xe4ed6378fa7e45860a285911e065ad2dee1bc1e3/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.