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 $3067.84M Roundhouse has indexed across 1,401,919 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%daydreams323d ago0x54d0d9…a90db8
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams323d ago0xecc66c…1ad85e
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams323d ago0x197367…465d0c
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams324d ago0x0da8e5…ea4146
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams324d ago0xcc6058…b5ddd0
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams324d ago0x2e7283…d2d7d6
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams324d ago0xa69ccf…86d228
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams324d ago0x1a5843…e0a664
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams324d ago0x4a79c4…302cfe
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams324d ago0x59919a…2d8850
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams324d ago0x3556fc…71971a
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams324d ago0xe93f3f…f7662a
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams325d ago0xb20b4a…da9067
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams325d ago0x614315…240314
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams325d ago0x9fe311…cd0305
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams325d ago0xcbcbfe…c8db2b
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams325d ago0x8e166b…589e63
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams325d ago0x040d29…30e5d6
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams325d ago0x19c867…89f624
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams325d ago0xc3c8bf…1b327f
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams325d ago0x59ca4e…d70322
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams325d ago0x692ca9…4e0ada
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams325d ago0xb6c8a4…85ce92
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams326d ago0x2c7243…5be0fa
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams326d ago0x3a2201…16e71a

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.