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.54M Roundhouse has indexed across 1,400,255 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%fluxa65d ago0xea19b8…67591f
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa65d ago0xa5846b…8b076b
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa65d ago0x885ff5…ae9cd0
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa65d ago0x4750d0…6e7b4e
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa65d ago0xb9478a…57454c
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa65d ago0x40a153…9d2d96
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa65d ago0x9ff012…133740
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa65d ago0x364e6b…1d95d5
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa65d ago0x6cbd02…24ea9e
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa65d ago0x485790…5e6073
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa65d ago0x7a37f3…917ad6
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa65d ago0x771914…c80443
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa65d ago0x76ae3c…09acb5
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa65d ago0xfe7791…3e020e
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa65d ago0xcb35a2…b5d223
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa65d ago0x470f8a…39ea99
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa65d ago0xebd7de…ac3001
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa77d ago0x1c4e81…d77c86
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa77d ago0xea1712…7c6bf6
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa77d ago0xeb7cf4…e31741
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa77d ago0x0bb7ce…2c1f2d
0xaf43…ae600xfe80…47eeBaseBase$0.001100%fluxa77d ago0x543541…40ca0f
0xaf43…ae600x9c95…e299BaseBase$0.001100%fluxa77d ago0x25de2c…f9736c
0xaf43…ae600x9c95…e299BaseBase$0.001100%fluxa77d ago0x7a3d89…c82ab0
0xaf43…ae600x9c95…e299BaseBase$0.001100%fluxa77d ago0x859350…e69869

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.