AgentReport

0xaff1…45bf

0xaff10a1de2ddfc2baf2fe6992a3ba485f83145bfExplorer
Paid out
$0.95
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
952
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.95 of the $3064.22M Roundhouse has indexed across 1,399,289 wallets — less than 0.0001% of it.

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

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

$0.95 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 62d ago
    $0.70
    702 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 77d ago
    $0.25
    250 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.70$0.0070262d agoGraph
0x9c95…e299$0.25$0.0025077d agoGraph

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

Data quality

74% of observed volume is with a single counterparty, in all 952 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xaff1…45bf0xfe80…47eeBaseBase$0.001100%fluxa63d ago0x0cdcd1…9c9ea8
0xaff1…45bf0xfe80…47eeBaseBase$0.001100%fluxa63d ago0xbf1eac…f2695b
0xaff1…45bf0xfe80…47eeBaseBase$0.001100%fluxa63d ago0xae99f4…d350a4
0xaff1…45bf0xfe80…47eeBaseBase$0.001100%fluxa63d ago0xd0ae32…7de1d7
0xaff1…45bf0xfe80…47eeBaseBase$0.001100%fluxa63d ago0x539900…75885a
0xaff1…45bf0xfe80…47eeBaseBase$0.001100%fluxa63d ago0xcfdff8…68bb05
0xaff1…45bf0xfe80…47eeBaseBase$0.001100%fluxa63d ago0x5c4a33…77bb16
0xaff1…45bf0xfe80…47eeBaseBase$0.001100%fluxa63d ago0x71b28b…1a4bac
0xaff1…45bf0xfe80…47eeBaseBase$0.001100%fluxa63d ago0xb88574…2b4157
0xaff1…45bf0xfe80…47eeBaseBase$0.001100%fluxa63d ago0x811949…9c9a46
0xaff1…45bf0xfe80…47eeBaseBase$0.001100%fluxa63d ago0x75366e…49cd14
0xaff1…45bf0xfe80…47eeBaseBase$0.001100%fluxa63d ago0x4a1e29…962407
0xaff1…45bf0xfe80…47eeBaseBase$0.001100%fluxa63d ago0xdc7586…2166b6
0xaff1…45bf0xfe80…47eeBaseBase$0.001100%fluxa63d ago0x22c8ae…6e7710
0xaff1…45bf0xfe80…47eeBaseBase$0.001100%fluxa63d ago0x779f21…1a4ce0
0xaff1…45bf0xfe80…47eeBaseBase$0.001100%fluxa63d ago0xdf76e1…b70832
0xaff1…45bf0xfe80…47eeBaseBase$0.001100%fluxa63d ago0x7ce823…84e995
0xaff1…45bf0xfe80…47eeBaseBase$0.001100%fluxa63d ago0x124760…f7bc7e
0xaff1…45bf0xfe80…47eeBaseBase$0.001100%fluxa64d ago0x306db1…083425
0xaff1…45bf0xfe80…47eeBaseBase$0.001100%fluxa64d ago0x1a107c…6e3d47
0xaff1…45bf0xfe80…47eeBaseBase$0.001100%fluxa64d ago0x448274…2992df
0xaff1…45bf0xfe80…47eeBaseBase$0.001100%fluxa64d ago0xba1439…8dee7d
0xaff1…45bf0xfe80…47eeBaseBase$0.001100%fluxa64d ago0xe6c8aa…0e6752
0xaff1…45bf0xfe80…47eeBaseBase$0.001100%fluxa64d ago0x599f24…dd99b7
0xaff1…45bf0xfe80…47eeBaseBase$0.001100%fluxa64d ago0xd35e27…4f05b1

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

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

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: 0xaff1…45bf

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