AgentReport

0xa65f…0430

0xa65fa79296c885b65b9d4af59ae915d84f250430Explorer
Paid out
$0.90
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
896
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.90 of the $3105.03M Roundhouse has indexed across 1,405,088 wallets — less than 0.0001% of it.

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

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.908962

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

  • 0xfe80…47ee · last paid 40d ago
    $0.62
    620 calls

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

  • 0x9c95…e299 · last paid 78d ago
    $0.28
    276 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
0xfe80…47ee$0.62$0.0062040d agoGraph
0x9c95…e299$0.28$0.0027678d agoGraph

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

Data quality

69% of observed volume is with a single counterparty, in all 896 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa61d ago0x7bba50…7398c9
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa61d ago0x548e8c…aa72b8
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa61d ago0x1921d3…ddb1f4
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa61d ago0x89485e…6f380c
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa61d ago0x8af695…985a48
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa61d ago0xea8a67…cebfd7
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa61d ago0xe6ad5f…fadd37
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa61d ago0x94a150…078701
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa62d ago0xf5ab3d…764dc2
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa62d ago0x4a9803…2c925d
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa62d ago0xcdce5f…0d2f29
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa62d ago0xfa49dd…5c9b4b
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa62d ago0x87e5dc…abec43
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa62d ago0xeb5f0a…2d255e
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa62d ago0x01a641…652524
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa62d ago0x40b058…2ce334
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa62d ago0x5a7a28…020ee7
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa62d ago0xfe940c…126652
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa62d ago0xc079b8…ca5440
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa62d ago0x7044c4…3ab210
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa62d ago0xba0ab3…25be60
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa62d ago0x610d72…f9a076
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa62d ago0xb424e6…1110ca
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa62d ago0x98b2a3…f54138
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa62d ago0xc5ab88…69991b

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

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

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: 0xa65f…0430

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