AgentReport

0xaf43…ae60

0xaf433290231d0678e7e064494ab17c2f6d33ae60Explorer
Paid out
$0.50
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
499
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.50 of the $3066.17M Roundhouse has indexed across 1,400,092 wallets — less than 0.0001% of it.

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

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

$0.50 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.30
    304 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.20
    195 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.30$0.0030462d agoGraph
0x9c95…e299$0.20$0.0019577d agoGraph

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

Data quality

61% of observed volume is with a single counterparty, in all 499 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa63d ago0x280911…c1428f
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa63d ago0x466eec…6b6f16
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa63d ago0x1f1a64…ed57c5
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa63d ago0x305a25…b1bebd
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa64d ago0xfc2af8…0b668d
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa64d ago0x8a2925…9e5444
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa64d ago0x32f19e…9fc00c
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa64d ago0x24cea2…30a591
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa64d ago0x2989b5…60e72d
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa64d ago0x79dd7e…9d65ce
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa64d ago0x299994…fbd3b7
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa64d ago0xf03fa5…ee3a1e
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa64d ago0xceb8ba…74c03e
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa64d ago0x3bc2f7…a48047
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa64d ago0x7637ff…5eafb4
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa64d ago0xd11e05…475e9a
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa64d ago0x3bed0f…d9cad8
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa64d ago0xc72a17…3c4414
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa64d ago0xe701a1…2a577f
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa64d ago0x8d4a70…7dbda4
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa64d ago0x65b360…9c5aa0
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa64d ago0x1b328e…52893c
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa64d ago0xbba09f…690928
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa65d ago0x6bde8c…e1e018
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa65d ago0x9fc311…1a4af8

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

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

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: 0xaf43…ae60

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