AgentReport

0xf2b2…b2fd

0xf2b2a8e362244b39c1acd6ec3df5073e81cbb2fdExplorer
Paid out
$19.38
Last 7d vs prior 7d
Received
$10.00
Last 7d vs prior 7d
Settlements
164
Last 7d vs prior 7d
8
Distinct counterparties
Over the whole indexed history

Paid $19.38 of the $3059.45M Roundhouse has indexed across 1,397,037 wallets — less than 0.0001% of it.

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

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
Risk & Compliance92%$17.811291
Not in any catalogue6%$1.15123
Web & Content1%$0.22182
Crypto Markets1%$0.2032

$1.00 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 8 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
velinus.eth$17.81$10.0013155d agoGraph
0xccc8…15be$1.00$0.002135d agoGraph
0x50ab…12fc$0.20$0.00261d agoGraph
0xcfa2…4dbe$0.12$0.002114d agoGraph
0x9dba…0df8$0.10$0.0016112d agoGraph
0x9ed1…c08f$0.08$0.008116d agoGraph
0x3c5c…d5fa$0.07$0.00263d agoGraph
0x2b6d…32c5$0.003$0.00163d agoGraph

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

Data quality

95% of observed volume is with a single counterparty, in all 164 observed settlements.

Organic volume $29.38 of $29.38 total.

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

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

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: 0xf2b2…b2fd

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