AgentReport

0xea88…cc72

0xea88d820376af508daacfd059fef3bc6cdaacc72Explorer
Paid out
$0.63
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
521
Last 7d vs prior 7d
7
Distinct counterparties
Over the whole indexed history

Paid $0.63 of the $3060.46M Roundhouse has indexed across 1,398,118 wallets — less than 0.0001% of it.

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

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 catalogue93%$0.595143
Location & Weather3%$0.0232
Web & Content3%$0.0221
Onchain Data<1%$0.00221

$0.56 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; for 5 of 7 the amount paid narrows the list to the ones listed at that price.

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
0x2f51…d688$0.56$0.00511279d agoGraph
0x7d9d…405d$0.02$0.002284d agoGraph
0xd8ba…8e9b$0.02$0.002285d agoGraph
0x0495…eed9$0.02$0.002285d agoGraph
0xf43f…ec91$0.01$0.001285d agoGraph
0x998f…b36f$0.002$0.002292d agoGraph
0x1bb5…ae7f$0.001$0.001285d agoGraph

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

Data quality

88% of observed volume is with a single counterparty, in all 521 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xea88…cc720x2f51…d688BaseBase$0.001100%dexter289d ago0xa2a80b…774362
0xea88…cc720x2f51…d688BaseBase$0.001100%openfacilitator289d ago0x6f69d5…839730
0xea88…cc720x2f51…d688BaseBase$0.001100%openfacilitator289d ago0xeb3cc2…94e91a
0xea88…cc720x2f51…d688BaseBase$0.001100%openfacilitator289d ago0xb051e7…2a47ae
0xea88…cc720x2f51…d688BaseBase$0.001100%openfacilitator289d ago0xa499ab…1cfccf
0xea88…cc720x2f51…d688BaseBase$0.001100%openfacilitator289d ago0x895f37…20a344
0xea88…cc720x2f51…d688BaseBase$0.001100%payAI289d ago0x5490d5…9583c6
0xea88…cc720x2f51…d688BaseBase$0.001100%payAI289d ago0xea8359…24408e
0xea88…cc720x2f51…d688BaseBase$0.001100%payAI289d ago0xd165d5…0afa27
0xea88…cc720x2f51…d688BaseBase$0.001100%payAI289d ago0x56a143…efeccb
0xea88…cc720x2f51…d688BaseBase$0.001100%payAI289d ago0x2bb118…55b39a
0xea88…cc720x2f51…d688BaseBase$0.001100%dexter289d ago0x2660c8…940d6a
0xea88…cc720x2f51…d688BaseBase$0.001100%dexter289d ago0x0befa9…ce9315
0xea88…cc720x2f51…d688BaseBase$0.001100%dexter289d ago0x40ecb0…1520e1
0xea88…cc720x2f51…d688BaseBase$0.001100%dexter289d ago0x74999b…801577
0xea88…cc720x2f51…d688BaseBase$0.001100%dexter289d ago0x1a2bd4…7bd7da
0xea88…cc720x2f51…d688BaseBase$0.001100%openfacilitator290d ago0x89c3a8…280e31
0xea88…cc720x2f51…d688BaseBase$0.001100%openfacilitator290d ago0xd6ef6b…f67f53
0xea88…cc720x2f51…d688BaseBase$0.001100%openfacilitator290d ago0xd1324d…ff212b
0xea88…cc720x2f51…d688BaseBase$0.001100%openfacilitator290d ago0xda5345…5d69f1
0xea88…cc720x2f51…d688BaseBase$0.001100%openfacilitator290d ago0x28fdba…ba8bdc
0xea88…cc720x2f51…d688BaseBase$0.001100%payAI290d ago0x5ab6cc…784ede
0xea88…cc720x2f51…d688BaseBase$0.001100%payAI290d ago0xad969e…ed9523
0xea88…cc720x2f51…d688BaseBase$0.001100%payAI290d ago0x6ffdf7…6b79fd
0xea88…cc720x2f51…d688BaseBase$0.001100%payAI290d ago0x3fb323…3963f9

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

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

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: 0xea88…cc72

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