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.41M Roundhouse has indexed across 1,405,967 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%fluxa68d ago0xa9c9a6…51060a
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa68d ago0x9c2303…682a4d
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa68d ago0x202c0b…160356
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa68d ago0xce2ab2…fe53ce
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa69d ago0x67ed5f…d7aec6
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa69d ago0x3063f9…84b2a4
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa69d ago0xe3caa1…d7a465
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa69d ago0x002238…8b6214
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa69d ago0xbc7837…0c841a
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa69d ago0xb0af14…32d787
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa69d ago0x31d263…c0eaf1
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa69d ago0xcb3943…2193f8
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa69d ago0x42e94a…7e44ec
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa69d ago0x12ff3c…e13d52
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa69d ago0xd984ea…b5b40e
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa69d ago0xee7bcd…73f535
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa69d ago0x131214…a82bd9
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa69d ago0x325424…184135
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa69d ago0x31a134…499128
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa69d ago0xe8d505…dbe895
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa69d ago0x935faa…f30eef
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa69d ago0xa2e6bd…8e8a2d
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa69d ago0x9caab8…acb46d
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa69d ago0xb4f3e0…643285
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa69d ago0x0ae004…3107e5

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.