AgentReport

0xbeef…9a39

0xbeef875db3cc2e0aa8673d6cb1fec672b1e79a39Explorer

$0.30

Paid out

$0.00

Received

Settlements

Distinct counterparties

Over the whole indexed history

Paid $0.30 of the $259.13M Roundhouse has indexed across 714,127 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.30	3	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; for 1 of 1 the amount paid narrows the list to the ones listed at that price.

0xed8b…8a8aapi.nftitem.ioEndpoint up
0xed8b…8a8a · last paid 194d ago
$0.30
3 calls
▸1 of 1 catalogued endpoints list a price this agent paid
- /x402/v2/uploadPrice match$0.10 listed

—

Balance now

Not read (rpc HTTP 429)

—

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.

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.10
Moved outTransfers out it sent itself, or a third party sent	$0.00
Net	-$0.10

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
0xed8b…8a8a	$0.30	$0.00	3	194d ago	Graph

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

Data quality

100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 3 observed settlements.

Organic volume $0.30 of $0.30 total.

Recent activity

Payer Payee	Chain	Amount	x402	Route	Age	Txn hash
0xbeef…9a390xed8b…8a8a	Base	$0.10	100%	coinbase	194d ago	0xaf2f45…735188
0xbeef…9a390xed8b…8a8a	Base	$0.10	100%	coinbase	194d ago	0x52ea50…ee71ae
0xbeef…9a390xed8b…8a8a	Base	$0.10	100%	coinbase	194d ago	0x3d2a1b…491151

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

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

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: 0xbeef…9a39

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