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%daydreams348d ago0xc5a074…e4d250
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams349d ago0x7552e1…8d3042
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams349d ago0xa76015…c88762
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams349d ago0x233222…5e5090
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams349d ago0xd43972…57e1ee
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams349d ago0xa86a8d…4acb92
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams349d ago0x4c649e…f2ccd9
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams350d ago0x45799d…eb13b3
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams350d ago0x02fdc5…8ed1ec
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams350d ago0x5cdbfd…886893
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams350d ago0x9ddb49…55f95f
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams351d ago0x9f4319…22412b
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams351d ago0x10b12b…6ac274
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams351d ago0x4a12b4…eb9b5b
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams351d ago0x24b004…a22103
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams351d ago0xefd0f0…8fa343
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams351d ago0x811402…ff3daa
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams352d ago0x7eb49b…4684c5
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams352d ago0x7002fc…cde703
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams352d ago0x976224…3c618e
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams352d ago0x226385…8ef15d
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams352d ago0xc9eb14…99f1f9
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams352d ago0x564719…679c82
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams352d ago0xeba0f4…080307
0x8ada…89cd0x6482…b779BaseBase$0.0001100%daydreams352d ago0xaa9a9b…90cc4f

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.