AgentReport

0x5372…f458

0x53728d4be659d46b92b9c0fbe72805e30c3bf458Explorer
Paid out
$4,780.61
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
3
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $4,780.61 of the $258.60M Roundhouse has indexed across 713,391 wallets0.0018% 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.

GroupShareSpentCallsSellers
Not in any catalogue100%$4,780.6132

$4,780.61 went to wallets that publish no endpoint in any catalogue we crawl — spend we can see and cannot describe.

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.

  • 0x0e3d…7757 · last paid 54d ago
    $3,668.47
    2 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x47c5…4fc3 · last paid 23d ago
    $1,112.14
    1 call

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

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

CounterpartyPaid themReceived backSettlementsLast
0x0e3d…7757$3,668.47$0.00254d agoGraph
0x47c5…4fc3$1,112.14$0.00123d agoGraph

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

Data quality

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

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x5372…f4580x47c5…4fc3Base$1,112.1470%0x3dd1…4d5c23d ago0xff9859…fe192b
0x5372…f4580x0e3d…7757Base$1,450.63100%0x617f…c06d54d ago0xf567e4…63a734
0x5372…f4580x0e3d…7757Base$2,217.84100%0x4c95…d79b114d ago0x1514c5…689425

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

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

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: 0x5372…f458

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