AgentReport

0xf26a…15a6

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

Paid $10.70 of the $3154.54M Roundhouse has indexed across 1,427,537 wallets — less than 0.0001% of it.

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

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 catalogue73%$7.83111
AI & Media27%$2.871931

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 2 of 2 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
H3RETIK Cloud$7.83$0.0011144d agoGraph
0xe903…1abf$2.87$0.001939d agoGraph

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

Data quality

73% of observed volume is with a single counterparty, in all 204 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf26a…15a6H3RETIK CloudBaseBase$0.60100%coinbase145d ago0x4827fd…1fb2a4
0xf26a…15a6H3RETIK CloudBaseBase$0.19100%coinbase145d ago0x9f2a6d…e0af56
0xf26a…15a6H3RETIK CloudBaseBase$0.05100%coinbase145d ago0x87b4f4…472b13
0xf26a…15a6H3RETIK CloudBaseBase$0.05100%coinbase145d ago0xa834d9…e87bbe

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

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

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: 0xf26a…15a6

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