AgentReport

0x9f3f…e5dc

0x9f3f726362ea7d9153142a00e01dc451bb56e5dcExplorer
Paid out
$69.91↓ 100%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
2↓ 100%
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $69.91 of the $833.89M Roundhouse has indexed across 1,300,243 wallets — less than 0.0001% of it.

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

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%$69.9122

$69.91 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; no listed price matches an amount this agent paid, so nothing narrows them.

  • 0xfd78…d002 · last paid 18d ago
    $35.42
    1 call

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x3c41…12da · last paid 10d ago
    $34.49
    1 call

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

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

Funds flow over time

Activity

AprMayJunJulAugSepOct
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0xfd78…d002$35.42$0.00118d agoGraph
0x3c41…12da$34.49$0.00110d agoGraph

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

Data quality

51% of observed volume is with a single counterparty, in all 2 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x9f3f…e5dc0x3c41…12daBase$34.4970%0xa923…c9ac10d ago0x99e372…69b0f8
0x9f3f…e5dc0xfd78…d002Base$35.4270%0x3943…d1bd18d ago0x433b23…c40979

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

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

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: 0x9f3f…e5dc

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