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,396 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%daydreams338d ago0x6f3567…97ea1d
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams338d ago0xac78a0…4e14af
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams338d ago0x761706…5ea46d
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams338d ago0x663244…4dc885
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams338d ago0x1b9123…d8caf8
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams339d ago0xcebae9…d8e7ac
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams340d ago0xc05365…af74d0
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams340d ago0xf194e5…08b8d5
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams340d ago0x6527b1…b87b58
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams340d ago0x988898…c5015c
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams340d ago0xaa2021…a1683e
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams340d ago0xced9d8…5abde4
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams340d ago0x43878a…ddbf80
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams340d ago0x200d6a…39ede0
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams340d ago0x0679e9…8f8c82
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams340d ago0xb76ac3…4e725b
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams340d ago0x249f31…7b28ea
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams341d ago0x3464f7…38d38b
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams341d ago0x859a52…d31560
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams341d ago0xb0e594…eed0d6
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams341d ago0x513eaa…b049e3
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams341d ago0x26c189…161100
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams341d ago0x9a5dce…79bc30
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams341d ago0x15aeb0…4f0c5f
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams341d ago0x91abc9…a77caf

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.