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 $3068.58M Roundhouse has indexed across 1,402,722 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 277d 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.00257277d 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%daydreams352d ago0x577b9f…edf4af
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams353d ago0x5d4921…1d4b59
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams353d ago0x800eda…05a9e7
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams353d ago0x7abec6…21b548
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams353d ago0xd6f285…6b0a56
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams353d ago0x319d83…4e8e04
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams353d ago0x32f913…1e8442
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams353d ago0xa3d11e…c03b73
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams354d ago0xd7cfe2…11fb9c
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams354d ago0xdd726b…cf11cf
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams355d ago0x9b1dbe…622bee
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams355d ago0x195e2b…257204
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams355d ago0x971d44…23b13f
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams356d ago0x35b6ce…489acf
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams356d ago0x4b09f6…e2a6e6
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams356d ago0xa01020…d40e28
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams357d ago0x764d13…3cf3ac
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams357d ago0x73097a…7e1da3
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams357d ago0x22b018…3ec3d9
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams357d ago0xb51045…5d6047
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams357d ago0x86cdea…58a48c
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams357d ago0x705ff2…307877
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams358d ago0xc9e4d4…d47a0e
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams358d ago0xca0baf…dc9fd1
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams358d ago0x745315…cd554c

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.