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%daydreams346d ago0x718fe0…0ffbb0
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams346d ago0x5bd1c5…9f7bf9
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams346d ago0xe0661a…1ed9b4
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams346d ago0xb392d9…571ea1
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams346d ago0xa48cbe…159b2b
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams346d ago0x927592…70f38e
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams346d ago0x8458c7…641162
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams346d ago0xaa79f0…b7efda
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams346d ago0x82da14…1819a5
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams347d ago0x751711…85393f
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams347d ago0x51fd65…6b4fdf
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams347d ago0xd3dbc6…a5ae9c
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams347d ago0x2c9193…92d5ea
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams347d ago0x426a37…a30189
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams347d ago0xfe969b…191450
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams348d ago0xd57d50…abebf5
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams348d ago0xf5a458…dec4e8
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams348d ago0x786eed…516062
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams348d ago0xbaa7a7…a62b92
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams348d ago0xd94fba…2721e0
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams348d ago0x49db53…3bc9c5
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams348d ago0x9f9c1f…167744
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams348d ago0xb8ca46…19d900
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams348d ago0x168263…0332f6
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams348d ago0x3ff3d3…fb4202

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.