AgentReport

0xf2cf…c7c4

0xf2cfa0ca7aa0a4a55d89974ea37487340827c7c4Explorer
Paid out
$34.26
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
21578
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $34.26 of the $260.63M Roundhouse has indexed across 716,280 wallets — less than 0.0001% of it.

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

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%$3.871,0002

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.

Folded from this wallet's 1,000 most recent settlements of 21,578 lifetime, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not.

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

Funds flow over time

Activity

MarAprMayJunJulAugSep
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x0495…eed9$2.46$0.00859225d agoGraph
0x8324…fd0e$1.41$0.00141238d agoGraph

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

Data quality

64% of observed volume is with a single counterparty, in the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap).

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf2cf…c7c40x0495…eed9Base$0.01100%payAI225d ago0xff2d0a…a4f541
0xf2cf…c7c40x0495…eed9Base$0.01100%payAI225d ago0xa48065…faa7a4
0xf2cf…c7c40x0495…eed9Base$0.01100%heurist225d ago0x030d62…ccfc42
0xf2cf…c7c40x0495…eed9Base$0.01100%payAI225d ago0xb55ce1…bf3a23
0xf2cf…c7c40x0495…eed9Base$0.01100%payAI225d ago0xd530ac…e89a27
0xf2cf…c7c40x0495…eed9Base$0.01100%payAI225d ago0x4cc70d…2271c4
0xf2cf…c7c40x0495…eed9Base$0.01100%payAI225d ago0x223a98…501ca1
0xf2cf…c7c40x0495…eed9Base$0.10100%payAI225d ago0xc45ab0…944cfa
0xf2cf…c7c40x0495…eed9Base$0.10100%payAI225d ago0x23d893…b1f614
0xf2cf…c7c40x0495…eed9Base$0.10100%payAI225d ago0xcdc3ab…ed1252
0xf2cf…c7c40x0495…eed9Base$0.10100%payAI225d ago0xe950da…c6a598
0xf2cf…c7c40x0495…eed9Base$0.10100%payAI225d ago0x1ac81b…42e549
0xf2cf…c7c40x0495…eed9Base$0.10100%payAI225d ago0x23433d…7918cd
0xf2cf…c7c40x0495…eed9Base$0.10100%payAI225d ago0x66b8a3…709b19
0xf2cf…c7c40x0495…eed9Base$0.10100%payAI225d ago0x985db9…ea197c
0xf2cf…c7c40x0495…eed9Base$0.10100%payAI225d ago0xf83408…8543d0
0xf2cf…c7c40x0495…eed9Base$0.10100%payAI225d ago0x925520…088507
0xf2cf…c7c40x0495…eed9Base$0.10100%payAI225d ago0xfecd8c…6370e6
0xf2cf…c7c40x0495…eed9Base$0.10100%payAI225d ago0xd0200f…dac3bf
0xf2cf…c7c40x0495…eed9Base$0.10100%payAI225d ago0xd088ad…13a1dc
0xf2cf…c7c40x0495…eed9Base$0.01100%payAI225d ago0xb329ec…7cc194
0xf2cf…c7c40x0495…eed9Base$0.10100%payAI225d ago0xea8027…252e73
0xf2cf…c7c40x0495…eed9Base$0.10100%payAI225d ago0x1c63d9…34d9e0
0xf2cf…c7c40x0495…eed9Base$0.10100%payAI225d ago0xe2ccfc…a6e7d3
0xf2cf…c7c40x0495…eed9Base$0.10100%payAI225d ago0x05e488…3dbde0

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

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

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: 0xf2cf…c7c4

curl -s 'https://api.roundhouseai.io/v0/agents/0xf2cfa0ca7aa0a4a55d89974ea37487340827c7c4'
curl -s 'https://api.roundhouseai.io/v0/entities/0xf2cfa0ca7aa0a4a55d89974ea37487340827c7c4/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.