AgentReport

0xe93f…637f

0xe93ffcd0b17740369dd54c8116628411727f637fExplorer

$0.00

Paid out

$0.00

Received

Settlements

Distinct counterparties

Over the whole indexed history

Paid $0.00 of the $259.40M Roundhouse has indexed across 714,764 wallets.

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%	$0.00	2	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.

0x87f1…7da0
0x87f1…7da0 · last paid 99d ago
$0.00
2 calls
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

no priced payments to size a call from

—

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 429: {"correlationId":"a406db3c9e99de8e-IAD","errorLink":"https://docs.cdp.coinbase.com/api-reference/v2/errors#rate-limit-exceeded","errorMessage":"Rate limit exceeded. Please try again in a few seconds."), 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
0x87f1…7da0	$0.00	$0.00	2	99d ago	Graph

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

Data quality

all observed volume is with one counterparty, in all 2 observed settlements.

Recent activity

Payer Payee	Chain	Amount	x402	Route	Age	Txn hash
0xe93f…637f0x87f1…7da0	Base	$0.00	100%	payAI	99d ago	0xd280c8…a6f04a
0xe93f…637f0x87f1…7da0	Base	$0.00	100%	payAI	99d ago	0x67ef12…249147

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

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

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: 0xe93f…637f

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