AgentReport

0x216f…d891

0x216f2a0f11a65ed148dcbd405e888b5e0139d891Explorer

also a merchant

Paid out

$0.001↓ 100%

Last 7d vs prior 7d

Received

$0.009↓ 100%

Last 7d vs prior 7d

Settlements

3↓ 100%

Last 7d vs prior 7d

Distinct counterparties

Over the whole indexed history

Paid $0.001 of the $259.50M Roundhouse has indexed across 714,807 wallets — less than 0.0001% of it.

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

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%	$0.001	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.

0xa75c…39e8veriton-html-json-api.netlify.appEndpoint down
0xa75c…39e8 · last paid 11d ago
$0.001
1 call
▸1 catalogued endpoints, none priced at an amount this agent paid
- /v1/html-to-json$0.02 listed

$0.00

Balance now

USDC on Base, read 0s ago

Spending power

more calls at its median payment of $0.001

—

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":"a4071d4e2b74d693-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…

Funds flow over time

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
0xa75c…39e8	$0.001	$0.008	2	11d ago	Graph
0x5fe7…c827	$0.00	$0.001	1	10d ago	Graph

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

Data quality

90% of observed volume is with a single counterparty, in all 3 observed settlements.

Organic volume $0.01 of $0.01 total.

Recent activity

Payer Payee	Chain	Amount	x402	Route	Age	Txn hash
0x5fe7…c8270x216f…d891	Base	$0.001	100%	payAI	10d ago	0x7f05d3…191bf6
0xa75c…39e80x216f…d891	Base	$0.008	100%	payAI	11d ago	0xd4b8c2…eaf505
0x216f…d8910xa75c…39e8	Base	$0.001	100%	payAI	11d ago	0x8df0a1…966a06

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

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

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: 0x216f…d891

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