AgentReport

0x0f3b…856f

0x0f3b3fb1ce2975714233801881d28dbfe148856fExplorer
Paid out
$19.81
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
52
Last 7d vs prior 7d
5
Distinct counterparties
Over the whole indexed history

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

Whole-history totals from the index rollup, which can be up to 30 minutes behind.

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

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%$19.80514
Web & Content<1%$0.0111

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 5 of 5 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
0xe126…652a$17.01$0.003076d agoGraph
0xac0b…2f6e$2.18$0.001935d agoGraph
WithZero$0.60$0.00177d agoGraph
0x7dd5…2629$0.01$0.00177d agoGraph
0x94b1…3cee$0.01$0.00177d agoGraph

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

Data quality

86% of observed volume is with a single counterparty, in all 52 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x0f3b…856f0xe126…652aBaseBase$0.001100%coinbase77d ago0x102cb4…9c4810
0x0f3b…856f0xe126…652aBaseBase$5.00100%coinbase77d ago0xe8cd9e…0081cc

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

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

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: 0x0f3b…856f

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