AgentReport

0x8b67…2f65

0x8b677b54dbef7532959dcf155a209ae311022f65Explorer

also a merchant

Paid out

$0.001↓ 100%

Last 7d vs prior 7d

Received

$0.26↓ 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.08M Roundhouse has indexed across 714,004 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.08

Balance now

USDC on Base, read 0s ago

~79

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":"a4042956d9d0d693-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
0x4040…017f	$0.00	$0.25	1	12d ago	Graph
0xa75c…39e8	$0.001	$0.01	2	11d ago	Graph

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

Data quality

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

Organic volume $0.26 of $0.26 total.

Recent activity

Payer Payee	Chain	Amount	x402	Route	Age	Txn hash
0xa75c…39e80x8b67…2f65	Base	$0.01	100%	payAI	11d ago	0x93c174…a63f10
0x8b67…2f650xa75c…39e8	Base	$0.001	100%	payAI	11d ago	0x523465…d414bf
0x4040…017f0x8b67…2f65	Base	$0.25	70%	0x8b67…2f65	12d ago	0xb105e8…5fe8a3

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

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

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: 0x8b67…2f65

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