AgentReport

0x9e9c…7b4e

0x9e9c9e133cd1b503f0be2aee7e023b8b62177b4eExplorer
Paid out
$0.009
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
4
Last 7d vs prior 7d
3
Distinct counterparties
Over the whole indexed history

Paid $0.009 of the $3064.22M Roundhouse has indexed across 1,399,289 wallets — less than 0.0001% of it.

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

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
Crypto Markets67%$0.00621
Onchain Data22%$0.00211
Not in any catalogue11%$0.00111

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

One merchant publishes more endpoints than a single catalogue read returns; its list is partial.

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
0xe903…1abf$0.006$0.002120d agoGraph
0xae0d…00b1$0.002$0.001128d agoGraph
0xcf92…42fb$0.001$0.001129d agoGraph

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

Data quality

67% of observed volume is with a single counterparty, in all 4 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x9e9c…7b4e0xe903…1abfBaseBase$0.003100%coinbase120d ago0xac95a8…ea994e
0x9e9c…7b4e0xe903…1abfBaseBase$0.003100%coinbase120d ago0xd349e1…f6ff21
0x9e9c…7b4e0xae0d…00b1BaseBase$0.002100%coinbase128d ago0xba5a3c…be2f2f
0x9e9c…7b4e0xcf92…42fbBaseBase$0.001100%coinbase129d ago0x3c7194…f52682

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

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

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: 0x9e9c…7b4e

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