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%daydreams349d ago0xa6a5ac…74e825
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams349d ago0xaccb16…a6555a
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams349d ago0x996873…01a134
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams349d ago0xcd3473…f149e7
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams350d ago0x434a4f…a96ba2
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams350d ago0x25bfb6…d80648
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams350d ago0xe6eef0…14dfc1
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams350d ago0xed781f…ebd9e3
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams350d ago0x74ece3…d9a8f5
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams350d ago0xa5d401…ee3ebc
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams350d ago0xdd9e48…2309de
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams351d ago0x8608ae…175ffd
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams351d ago0x55bb32…55fb70
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams351d ago0x4ed20c…2544d6
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams351d ago0xf34e4a…aceb2c
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams352d ago0xfa2abc…7e8b7c
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams352d ago0xe87efd…92415c
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams352d ago0xc9461b…0de8f6
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams352d ago0x7d9b55…4070a5
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams352d ago0x2d7802…67e4b0
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams352d ago0xd0eeb4…4dd73f
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams352d ago0xc86c88…71a32b
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams352d ago0x333c4e…682aeb
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams352d ago0x818ea4…f8209f
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams353d ago0x3e3a9b…fecd71

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.