AgentReport

0x52dd…c7a2

0x52dd16c077cca4658bce1c172867cfc32da7c7a2Explorer

$0.15

Paid out

$0.00

Received

Settlements

Distinct counterparties

Over the whole indexed history

Paid $0.15 of the $261.32M Roundhouse has indexed across 717,386 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.15	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.

0x3417…f694x402.nolimit.foundationEndpoint down
0x3417…f694 · last paid 297d ago
$0.15
3 calls
▸1 of 3 catalogued endpoints list a price this agent paid
- /noLimitLLMPrice match$0.05 listed
- /noLimitSwap$0.10 listed
- /noLimitMixer$0.08 listed

$0.00

Balance now

USDC on Base, read 0s ago

Spending power

more calls at its median payment of $0.05

—

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

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
0x3417…f694	$0.15	$0.00	3	297d 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.15 of $0.15 total.

Recent activity

Payer Payee	Chain	Amount	x402	Route	Age	Txn hash
0x52dd…c7a20x3417…f694	Base	$0.05	100%	payAI	297d ago	0xd407b7…a49520
0x52dd…c7a20x3417…f694	Base	$0.05	100%	payAI	297d ago	0xf85db2…597f4e
0x52dd…c7a20x3417…f694	Base	$0.05	100%	payAI	297d ago	0x7dcd70…02a3c6

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

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

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: 0x52dd…c7a2

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