AgentReport

0xa5a4…e191

0xa5a40970fdd4c19059a4ec28c82e8daaada2e191Explorer
Paid out
$2.24
Last 7d vs prior 7d
Received
$1.97
Last 7d vs prior 7d
Settlements
129
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $2.24 of the $3059.45M Roundhouse has indexed across 1,397,282 wallets — less than 0.0001% of it.

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

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

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

  • 0x7231…3230 · last paid 140d ago
    $2.24
    3 calls

    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
0x7231…3230$2.24$0.003140d agoGraph
0xb90a…9ae4$0.00$1.97126147d agoGraph

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

Data quality

53% of observed volume is with a single counterparty, in all 129 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xb90a…9ae40xa5a4…e191BaseBase$0.01100%fluxa166d ago0xa61bb5…3fd9ef
0xb90a…9ae40xa5a4…e191BaseBase$0.01100%fluxa166d ago0x2ac3f8…6a2bf5
0xb90a…9ae40xa5a4…e191BaseBase$0.01100%fluxa166d ago0xafd3ef…ed3046
0xb90a…9ae40xa5a4…e191BaseBase$0.01100%fluxa166d ago0x16f530…5a1ec9

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

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

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: 0xa5a4…e191

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