AgentReport

0xa272…e274

0xa272835d34949a1c88d9144a2a7293265bf0e274Explorer

also a merchant

Paid out

$5.10

Last 7d vs prior 7d

Received

$0.10

Last 7d vs prior 7d

Settlements

Last 7d vs prior 7d

Distinct counterparties

Over the whole indexed history

Paid $5.10 of the $260.82M Roundhouse has indexed across 716,570 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%	$5.10	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; for 1 of 1 the amount paid narrows the list to the ones listed at that price.

0x45e3…6faax402zeroclick.comEndpoint up
0x45e3…6faa · last paid 332d ago
$5.10
2 calls
▸3 of 4 catalogued endpoints list a price this agent paid
- /small-mintPrice match$0.10 listed
- /small-mintPrice match$0.10 listed
- /mintPrice match$5.00 listed
- /large-mint$10.00 listed

$0.00

Balance now

USDC on Base, read 0s ago

Spending power

more calls at its median payment of $2.55

—

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":"a40d6b87d8a80db7-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
0x45e3…6faa	$5.10	$0.00	2	332d ago	Graph
0x19ef…3a7f	$0.00	$0.10	1	332d ago	Graph

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

Data quality

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

Organic volume $5.20 of $5.20 total.

Recent activity

Payer Payee	Chain	Amount	x402	Route	Age	Txn hash
0xa272…e2740x45e3…6faa	Base	$0.10	100%	payAI	332d ago	0xf1a0b3…841e88
0x19ef…3a7f0xa272…e274	Base	$0.10	100%	payAI	332d ago	0x58e9bf…d82165
0xa272…e2740x45e3…6faa	Base	$5.00	100%	payAI	334d ago	0x3baa30…681b4d

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

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

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: 0xa272…e274

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