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%daydreams346d ago0x4ed478…038b0c
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams346d ago0xa9bd06…5abf43
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams346d ago0x1c406a…04efd4
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams346d ago0xb383c6…5b99b8
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams346d ago0x58a312…c597af
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams347d ago0xe0d7cc…af206b
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams347d ago0x1e2980…0e8c40
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams347d ago0xf7db12…c6be13
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams347d ago0x263489…871313
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams347d ago0xe4e48b…6e1f83
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams347d ago0xbe0642…bd368e
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams348d ago0x65dae5…c5f81d
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams348d ago0x682007…416e5e
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams348d ago0x2fa004…2e57fd
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams348d ago0x4f0566…e16e80
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams348d ago0x900103…a3f9f7
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams348d ago0xbd3a53…b1509f
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams348d ago0x3a5b80…176647
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams348d ago0x488e47…3b9d8d
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams348d ago0x949c3b…7294f1
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams348d ago0xd1c31f…6bbbd7
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams348d ago0x76771f…5e8c30
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams349d ago0x33471e…9ff004
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams349d ago0xeb3b16…e5c697
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams349d ago0x24e61b…040e79

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.