AgentReport

0xf8d0…d4cd

0xf8d0c637e28409a3950a5e6dfc9809bc3906d4cdExplorer

also a merchant

$0.000001

Paid out

$0.000001

Received

Settlements

Distinct counterparties

Over the whole indexed history

Paid $0.000001 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
AI & Media	100%	$0.000001	1	1

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

Studio Xwww.studio-x.ccImage generationEndpoint up
0x1919…679c · last paid 72d ago
$0.000001
1 call
▸4 catalogued endpoints, none priced at an amount this agent paid
- /api/generate/video-fast$0.17 listed
- /api/generate/video-pro$0.55 listed
- /api/generate/video-ultra$0.55 listed
- /api/generate/imageImage generation$0.02 listed

$0.00

Balance now

USDC on Base, read 0s ago

Spending power

more calls at its median payment of $0.000001

—

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.

The transfer history behind this wallet was not read (cdp sql 400: {"correlationId":"a40119c52f3cfe99-IAD","errorLink":"https://docs.cdp.coinbase.com/api-reference/v2/errors#invalid-request","errorMessage":"Limit for rows or bytes to read on leaf node exceeded, max b), so where its funds came from is unknown here. The balance above is still measured.

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
0x1919…679c	$0.000001	$0.00	1	72d ago	Graph
0x5a9a…9311	$0.00	$0.000001	1	72d 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
0xf8d0…d4cd0x1919…679c	Base	$0.000001	100%	payAI	72d ago	0x8d250b…527af5
0x5a9a…93110xf8d0…d4cd	Base	$0.000001	100%	payAI	72d ago	0xc52c7c…208e1f

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

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

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: 0xf8d0…d4cd

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