AgentReport

0x8931…af49

0x89312009c091fa3242419dece7aa039266f3af49Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
258
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3068.58M Roundhouse has indexed across 1,402,563 wallets — less than 0.0001% of it.

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

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

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

  • 0x6482…b779 · last paid 276d ago
    $0.03
    258 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
0x6482…b779$0.03$0.00258276d agoGraph

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

Data quality

100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 258 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams344d ago0x7b7d7f…e16282
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams344d ago0x59e760…256a73
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams344d ago0x329a65…909d1d
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams344d ago0x2e7656…3c6bd1
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams344d ago0x122791…5ac4f8
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams344d ago0xef01fc…06af5f
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams344d ago0x30b063…430185
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams344d ago0x78ff84…169a91
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams344d ago0xf15677…8069b0
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams345d ago0x966b4f…7effb1
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams345d ago0xc742d1…503b0d
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams345d ago0x4a3669…8f6719
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams345d ago0x33c5e5…a03430
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams345d ago0x139abb…6b9077
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams345d ago0xbc8776…54a621
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams345d ago0x84f824…88eddb
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams345d ago0x55b9bd…b921aa
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams345d ago0xd2968d…9789c1
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams345d ago0x352d03…2ab634
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams345d ago0x286360…53d017
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams345d ago0x62594a…c67a62
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams346d ago0xe5888d…e97b23
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams346d ago0x18dbcc…165359
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams346d ago0x4fea63…8bc8cc
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams346d ago0x593f55…c88da6

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

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

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: 0x8931…af49

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