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,563 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%daydreams344d ago0x45a581…1ed90d
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x64759f…c492f9
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x3f26cd…bd4d35
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0xbf2c2c…44a641
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x6dd73e…a6e711
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0xf249ea…860f2f
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0xea4b8e…72fb20
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x6e1d01…4abb2c
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0xb8fff9…a9a6a4
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x4a8f64…447f64
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0xebb172…2ac413
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x47ce2a…6f803d
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0xee0d1a…6158d2
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x5ed045…b8bd40
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x0f5ced…684d3d
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x749ea9…f9fb6a
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x50e10c…0f044a
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x814a8f…16026b
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x322ccc…24a795
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x6fc2c8…5fe6ed
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x48478c…3c28fc
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0xcd9d11…cf2954
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0xca622c…efe07d
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams346d ago0x09614f…82f614
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams346d ago0xdd514a…f85d49

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.