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.10M Roundhouse has indexed across 1,405,259 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%fluxa65d ago0x080ab5…ea18dd
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa65d ago0xe46ee2…191e25
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa65d ago0x2841fe…c29d6b
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa65d ago0x3d5d58…56752c
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa65d ago0x321b3e…fae840
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa65d ago0xd4020c…f5989f
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa65d ago0x45512f…c92015
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa65d ago0xaad194…9212d9
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa65d ago0x3a04a2…14e672
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa65d ago0x34cecd…8415c3
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa65d ago0xc8fda5…5f4ae6
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa65d ago0xb1f9bb…46aef9
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa66d ago0x638490…a456c9
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa66d ago0xed179a…c94b74
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa66d ago0xb1c8e1…85a3ea
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa66d ago0x0e111f…e51d1a
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa66d ago0x9cedf8…98b956
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa66d ago0xce5c4f…e65ad0
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa66d ago0xf1c45c…b341e4
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa66d ago0x0e4cf2…384d96
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa66d ago0x6acc12…7b57d5
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa66d ago0x352890…c5c5df
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa66d ago0x243155…614ce7
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa66d ago0x6c76c0…2c1951
0xa65f…04300xfe80…47eeBaseBase$0.001100%fluxa66d ago0x4010fc…41fbc2

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.