AgentReport

0xaf2f…68ba

0xaf2f522cde5a75038a080e92e39fe3334fa868baExplorer
Paid out
$2.42
Last 7d vs prior 7d
Received
$2.47
Last 7d vs prior 7d
Settlements
141
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

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

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

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%$2.4251

$2.42 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.

  • 0x3f14…146d · last paid 148d ago
    $2.42
    5 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
0xb90a…9ae4$0.00$2.47136148d agoGraph
0x3f14…146d$2.42$0.005148d agoGraph

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

Data quality

51% of observed volume is with a single counterparty, in all 141 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xb90a…9ae40xaf2f…68baBaseBase$0.01100%fluxa150d ago0x82c168…ddde95
0xb90a…9ae40xaf2f…68baBaseBase$0.01100%fluxa150d ago0x36b31a…bf6558
0xb90a…9ae40xaf2f…68baBaseBase$0.01100%fluxa150d ago0x08c668…5463cd
0xb90a…9ae40xaf2f…68baBaseBase$0.01100%fluxa150d ago0xf42c57…ea34d4
0xb90a…9ae40xaf2f…68baBaseBase$0.05100%fluxa150d ago0x20319e…5ebc59
0xb90a…9ae40xaf2f…68baBaseBase$0.01100%fluxa150d ago0xcc351c…654a23
0xb90a…9ae40xaf2f…68baBaseBase$0.01100%fluxa151d ago0x26657d…43d1c3
0xb90a…9ae40xaf2f…68baBaseBase$0.01100%fluxa151d ago0x1efd7f…4fed45
0xb90a…9ae40xaf2f…68baBaseBase$0.01100%fluxa151d ago0x7a5640…813fad
0xb90a…9ae40xaf2f…68baBaseBase$0.01100%fluxa151d ago0xe6a059…747d6d
0xb90a…9ae40xaf2f…68baBaseBase$0.01100%fluxa151d ago0xed43a4…06d49f
0xb90a…9ae40xaf2f…68baBaseBase$0.01100%fluxa151d ago0xc62d4a…d4c2bd
0xb90a…9ae40xaf2f…68baBaseBase$0.01100%fluxa151d ago0xf86644…af4e8f
0xb90a…9ae40xaf2f…68baBaseBase$0.01100%fluxa151d ago0xf44880…51e8f0
0xb90a…9ae40xaf2f…68baBaseBase$0.01100%fluxa151d ago0x7f0c75…ff2fdd
0xb90a…9ae40xaf2f…68baBaseBase$0.05100%fluxa151d ago0xb21357…fc69c1
0xb90a…9ae40xaf2f…68baBaseBase$0.01100%fluxa152d ago0xe81d9b…b3f186
0xb90a…9ae40xaf2f…68baBaseBase$0.01100%fluxa152d ago0x80743a…b6096f
0xaf2f…68ba0x3f14…146dBaseBase$0.40100%fluxa152d ago0x0d2e0d…b81ad7
0xb90a…9ae40xaf2f…68baBaseBase$0.01100%fluxa152d ago0xce9ae2…9fcf6d
0xb90a…9ae40xaf2f…68baBaseBase$0.01100%fluxa152d ago0x206013…8e90a3
0xb90a…9ae40xaf2f…68baBaseBase$0.01100%fluxa152d ago0x3ef65c…94e91a
0xb90a…9ae40xaf2f…68baBaseBase$0.01100%fluxa152d ago0xaf61d1…442120
0xb90a…9ae40xaf2f…68baBaseBase$0.01100%fluxa152d ago0x7b995b…a1f750
0xb90a…9ae40xaf2f…68baBaseBase$0.05100%fluxa152d ago0xe07a39…f99243

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

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

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: 0xaf2f…68ba

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