AgentReport

0xa5425ab809369b13e3f359a459054e4190cce32f

0xa5425ab809369b13e3f359a459054e4190cce32fExplorer
Paid out
$0.04
Last 7d vs prior 7d
Received
$0.04
Last 7d vs prior 7d
Settlements
5
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.04 of the $3238.84M Roundhouse has indexed across 1,456,200 wallets — less than 0.0001% of it.

Whole-history totals from the index rollup, which can be up to 30 minutes behind.

Chains (from the recent scan): Base (5)

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%$0.0411

$0.04 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.

  • 0x9d19…08d3 · last paid 157d ago
    $0.04
    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

MayJunJulAugSepOctNov
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x9d19…08d3$0.04$0.001157d agoGraph
0xb90a…9ae4$0.00$0.044157d agoGraph

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

Data quality

50% of observed volume is with a single counterparty, in all 5 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xa542…e32f0x9d19…08d3BaseBase$0.04100%fluxa157d ago0x89644f…3b0755
0xb90a…9ae40xa542…e32fBaseBase$0.01100%fluxa157d ago0x531104…cc5161
0xb90a…9ae40xa542…e32fBaseBase$0.01100%fluxa158d ago0xf9059a…9bb783
0xb90a…9ae40xa542…e32fBaseBase$0.01100%fluxa159d ago0x504826…b2c4bd
0xb90a…9ae40xa542…e32fBaseBase$0.01100%fluxa160d ago0xa921c7…a6cb47

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

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

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: 0xa5425ab809369b13e3f359a459054e4190cce32f

curl -s 'https://api.roundhouseai.io/v0/agents/0xa5425ab809369b13e3f359a459054e4190cce32f'
curl -s 'https://api.roundhouseai.io/v0/entities/0xa5425ab809369b13e3f359a459054e4190cce32f/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. Either pay over x402 (mint a personal key for $0.01 at
GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at
https://roundhouseai.io/dashboard/connections. If you have neither, ask before going further.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.