AgentReport

0xfc0f…62f5

0xfc0fa07708fdd0697c1a7b45cf41c12add0a62f5Explorer

also a merchant

$2.50

Paid out

$2.50

Received

Settlements

Distinct counterparties

Over the whole indexed history

Paid $2.50 of the $258.47M Roundhouse has indexed across 713,069 wallets — less than 0.0001% of it.

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

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.

Group	Share	Spent	Calls	Sellers
Not in any catalogue	100%	$2.50	1	1

$2.50 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; no listed price matches an amount this agent paid, so nothing narrows them.

0x86b1…2f66
0x86b1…2f66 · last paid 46d ago
$2.50
1 call
This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

$0.00

Balance now

USDC on Base, read 0s ago

Spending power

more calls at its median payment of $2.50

—

Burn rate

nothing spent in the last 7 days

—

Runway

not spending, so nothing to run out

Inflows and outflows

Every token transfer this wallet has made, not just the x402 ones the index holds.

Topped upTransfers in that no named facilitator relayed	$0.00
EarnedTransfers in a named facilitator relayed — x402 revenue	$0.00
SpentTransfers out a named facilitator relayed — x402 payments	$0.00
Moved outTransfers out it sent itself, or a third party sent	$0.00
Net	$0.00

These transfers net to the balance above, so nothing is missing from them.

Every USDC transfer this wallet has made or received, from the indexed chain connector. A transfer is x402 when the transaction called transferWithAuthorization (EIP-3009), which is what an x402 payment is, and a plain transfer when it did not.

Balance now

Reading the chain…

Spending power

Reading the chain…

Burn rate

Reading the chain…

Runway

Reading the chain…

Activity

MarAprMayJunJulAugSep

LessMore

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

Frequent counterparties

Counterparty	Paid them	Received back	Settlements	Last
0x7b55…a52b	$0.00	$2.50	1	46d ago	Graph
0x86b1…2f66	$2.50	$0.00	1	46d ago	Graph

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

Data quality

50% of observed volume is with a single counterparty, in all 2 observed settlements.

Recent activity

Payer Payee	Chain	Amount	x402	Route	Age	Txn hash
0x7b55…a52b0xfc0f…62f5	Base	$2.50	100%	0x9f02…1bcb	46d ago	0x5c2d65…1400f7
0xfc0f…62f50x86b1…2f66	Base	$2.50	100%	0x9f02…1bcb	46d ago	0x5c2d65…1400f7

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

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

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: 0xfc0f…62f5

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