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,396 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%daydreams337d ago0xfbea20…1df06e
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams338d ago0x96fbda…07f205
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams338d ago0x3f7f6a…e2e415
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams338d ago0x832bf7…88a2ad
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams338d ago0x7ea64b…60279a
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams338d ago0xef9489…40617e
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams338d ago0xf01ace…405e05
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams338d ago0xc0ba68…08d3f5
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams339d ago0x79177b…a564ec
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x3c6a08…c0ec08
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x7d4cd2…210bd2
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x5a8ac3…c2564e
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x000c13…08781e
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x2b40a4…cc9b20
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x7e197c…54e85a
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x72e808…582183
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x07b73f…f81fa9
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams340d ago0xc38a00…dd4563
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams340d ago0xe5fa29…59fa11
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x989d6f…6ce3d0
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams341d ago0x33581b…139671
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams341d ago0x6e331c…5b4d4b
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams341d ago0x043393…9be80a
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams341d ago0x61624c…6fb5fa
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams341d ago0x484854…3b2ad7

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.