AgentReport

0x8ada…89cd

0x8ada51d603a3b6ca21db036d6b83e2ea6e4c89cdExplorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
257
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,402,228 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (257)

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.032571

$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
    257 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.00257276d 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 257 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams326d ago0x17b9e3…59ce40
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams326d ago0xcc189b…ecd33f
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams326d ago0xa55bd1…8f1821
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams326d ago0xc4ce7e…abb251
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams326d ago0x4f4d09…87a30d
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams326d ago0x302558…ccfe72
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams326d ago0x6b57f0…62d494
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams327d ago0x253b06…8ee465
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams327d ago0x858140…50b730
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams327d ago0x5954d2…edaf69
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams327d ago0x455583…546f76
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams327d ago0xddfb17…e2a25e
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams327d ago0xdccda5…f7d26d
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams327d ago0xff9e68…9e51e3
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams327d ago0xac1f49…db43b3
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams328d ago0x98eac3…ceb662
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams328d ago0x02ef02…3283b6
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams328d ago0x3dd91f…22b811
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams328d ago0x9189b9…d31ee5
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams328d ago0xd1aaba…997542
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams328d ago0x3f91de…25b8c7
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams336d ago0xfa9fdb…37504f
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams337d ago0x3a8807…7307de
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams337d ago0x10baa9…8f610a
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams337d ago0x398d77…589b86

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 0x8ada…89cd has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0x8ada51d603a3b6ca21db036d6b83e2ea6e4c89cd

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: 0x8ada…89cd

curl -s 'https://api.roundhouseai.io/v0/agents/0x8ada51d603a3b6ca21db036d6b83e2ea6e4c89cd'
curl -s 'https://api.roundhouseai.io/v0/entities/0x8ada51d603a3b6ca21db036d6b83e2ea6e4c89cd/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.