AgentReport

0xf916…01e3

0xf9168d255cc2ba50a9707e127f673e97d04701e3Explorer
Paid out
$1.07↓ 100%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
30↓ 100%
Last 7d vs prior 7d
11
Distinct counterparties
Over the whole indexed history

Paid $1.07 of the $3061.41M Roundhouse has indexed across 1,398,509 wallets — less than 0.0001% of it.

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

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 catalogue71%$0.7653
AI & Media10%$0.1151
Location & Weather8%$0.0822
Reference Data5%$0.0551
Web & Content4%$0.0452
Crypto Markets1%$0.0141
Company & People<1%$0.00741

$0.01 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 7 of 11 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
0x75dd…d2a5$0.75$0.00373d agoGraph
0xe903…1abf$0.11$0.00510d agoGraph
0x4466…125e$0.08$0.00119d agoGraph
0x2932…4f60$0.05$0.00558d agoGraph
0x3c5f…3eea$0.04$0.00476d agoGraph
0x2b6d…32c5$0.01$0.00447d agoGraph
0x20e4…6eb2$0.01$0.00175d agoGraph
0xe73d…1114$0.007$0.00441d agoGraph

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

Data quality

70% of observed volume is with a single counterparty, in all 30 observed settlements.

Recent activity

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

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

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: 0xf916…01e3

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