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,722 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 277d 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.00258277d 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%daydreams326d ago0xa9a616…be1747
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams326d ago0xd0423f…f3df85
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams326d ago0x909425…a7bb60
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams326d ago0xf531a0…3490ff
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams326d ago0xec0e9c…e2c2dc
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams327d ago0xf7f1c3…bcd246
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams327d ago0xefc535…0dba6e
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams327d ago0x65b1c3…7380d0
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams327d ago0x947db7…08e4e2
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams327d ago0x4acaa8…1e4ced
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams327d ago0x1e833c…6a2348
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams327d ago0x1bf9bf…e834bb
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams327d ago0x9ee406…494781
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams327d ago0x1ec59c…d0aafe
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams328d ago0x187c4d…7cd9c0
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams328d ago0x055bed…bc5933
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams328d ago0x878f46…054f71
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams328d ago0x4546d4…69af48
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams328d ago0x5a6f45…724ee1
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams336d ago0x8bbf8f…8f98d8
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams337d ago0x2d26de…ca0273
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams337d ago0x58aa05…12cf28
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams337d ago0x604ec5…6cc909
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams338d ago0x9e9efa…6dd482
0x8931…af490x6482…b779BaseBase$0.0001100%daydreams338d ago0x23ec33…3560f2

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.