AgentReport

EZgcudgvfV6bLffrBuFr7kZQkmv4sz16aJLD7LTzRr5P

EZgcudgvfV6bLffrBuFr7kZQkmv4sz16aJLD7LTzRr5PExplorer
Paid out
$0.78↓ 100%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
28↓ 100%
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.78 of the $3116.99M Roundhouse has indexed across 1,419,290 wallets — less than 0.0001% of it.

Chains (from the recent scan): Solana (28)

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.78281

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 1 of 1 the amount paid narrows the list to the ones listed at that price.

Wallet balance

Not read. Solana wallets are not supported by the balance and funding-history read yet. Nothing is shown here about this wallet's balance or funding, which is not the same as it holding none.

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
2gmFrG…p42j$0.78$0.00289d 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 28 observed settlements.

Organic volume $0.78 of $0.78 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
EZgcud…Rr5P2gmFrG…p42jSolanaSolana$0.02100%dexter69d ago39ineXYW…99rrga
EZgcud…Rr5P2gmFrG…p42jSolanaSolana$0.02100%dexter69d ago2wvnfur1…dKzdCs
EZgcud…Rr5P2gmFrG…p42jSolanaSolana$0.02100%dexter69d ago2NUwjYAA…mY4kvN

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

GET api.roundhouseai.io/v0/agents/EZgcudgvfV6bLffrBuFr7kZQkmv4sz16aJLD7LTzRr5P

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: EZgcudgvfV6bLffrBuFr7kZQkmv4sz16aJLD7LTzRr5P

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