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%openfacilitator289d ago0xfba5ec…699321
0xea88…cc720x2f51…d688BaseBase$0.001100%openfacilitator289d ago0xfbdd4c…c46b2d
0xea88…cc720x2f51…d688BaseBase$0.001100%openfacilitator289d ago0xfb017e…6adaf7
0xea88…cc720x2f51…d688BaseBase$0.001100%openfacilitator289d ago0xa1699f…8beffe
0xea88…cc720x2f51…d688BaseBase$0.001100%openfacilitator289d ago0x075077…106637
0xea88…cc720x2f51…d688BaseBase$0.001100%payAI289d ago0xb5851e…3cb159
0xea88…cc720x2f51…d688BaseBase$0.001100%payAI289d ago0x259b79…577f7a
0xea88…cc720x2f51…d688BaseBase$0.001100%payAI289d ago0xb92c38…605924
0xea88…cc720x2f51…d688BaseBase$0.001100%payAI289d ago0xeb77a4…0e151d
0xea88…cc720x2f51…d688BaseBase$0.001100%payAI289d ago0x5bf937…4f2773
0xea88…cc720x2f51…d688BaseBase$0.001100%dexter289d ago0xf670d2…21a0eb
0xea88…cc720x2f51…d688BaseBase$0.001100%openfacilitator289d ago0x307f67…0b4954
0xea88…cc720x2f51…d688BaseBase$0.001100%openfacilitator289d ago0x1e5841…54a507
0xea88…cc720x2f51…d688BaseBase$0.001100%openfacilitator289d ago0x030e64…0224db
0xea88…cc720x2f51…d688BaseBase$0.001100%openfacilitator289d ago0xff10b6…d3bada
0xea88…cc720x2f51…d688BaseBase$0.001100%openfacilitator289d ago0xd0a8b6…ef88bc
0xea88…cc720x2f51…d688BaseBase$0.001100%payAI289d ago0x801bdb…629880
0xea88…cc720x2f51…d688BaseBase$0.001100%payAI289d ago0xee5283…eda958
0xea88…cc720x2f51…d688BaseBase$0.001100%payAI289d ago0x4a9a42…d46270
0xea88…cc720x2f51…d688BaseBase$0.001100%payAI289d ago0xbb4284…7fc829
0xea88…cc720x2f51…d688BaseBase$0.001100%payAI289d ago0x8cdde8…4a8167
0xea88…cc720x2f51…d688BaseBase$0.001100%dexter289d ago0x5052d3…0fd203
0xea88…cc720x2f51…d688BaseBase$0.001100%dexter289d ago0x42f9eb…a2b25d
0xea88…cc720x2f51…d688BaseBase$0.001100%dexter289d ago0x940c0e…2aa941
0xea88…cc720x2f51…d688BaseBase$0.001100%dexter289d ago0x28d831…5f46c8

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.