AgentReport

0x02de…a7e2

0x02de752cac0c45664f37bf239237e93e3942a7e2Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
267
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3066.54M Roundhouse has indexed across 1,400,843 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (267)

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.032671

$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
    267 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.00267276d 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 267 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x02de…a7e20x6482…b779BaseBase$0.0001100%daydreams348d ago0xbdc00e…7a52a0
0x02de…a7e20x6482…b779BaseBase$0.0001100%daydreams348d ago0x3ab575…609e37
0x02de…a7e20x6482…b779BaseBase$0.0001100%daydreams348d ago0x77d29b…31ce4a
0x02de…a7e20x6482…b779BaseBase$0.0001100%daydreams348d ago0x4512c5…79f408
0x02de…a7e20x6482…b779BaseBase$0.0001100%daydreams349d ago0x2e2980…8880d1
0x02de…a7e20x6482…b779BaseBase$0.0001100%daydreams349d ago0x49b812…5be0c6
0x02de…a7e20x6482…b779BaseBase$0.0001100%daydreams349d ago0x2a8352…7490f2
0x02de…a7e20x6482…b779BaseBase$0.0001100%daydreams349d ago0x86f107…426bc3
0x02de…a7e20x6482…b779BaseBase$0.0001100%daydreams349d ago0x8fe3bf…3bf1f9
0x02de…a7e20x6482…b779BaseBase$0.0001100%daydreams350d ago0x05110e…81e8b8
0x02de…a7e20x6482…b779BaseBase$0.0001100%daydreams350d ago0x2e56cd…f8128b
0x02de…a7e20x6482…b779BaseBase$0.0001100%daydreams350d ago0x88466a…4d4715
0x02de…a7e20x6482…b779BaseBase$0.0001100%daydreams350d ago0xb39d20…51cff5
0x02de…a7e20x6482…b779BaseBase$0.0001100%daydreams351d ago0x0dea0d…fff9cf
0x02de…a7e20x6482…b779BaseBase$0.0001100%daydreams351d ago0x0f42f6…f05cc9
0x02de…a7e20x6482…b779BaseBase$0.0001100%daydreams351d ago0xea37d1…a6f57e
0x02de…a7e20x6482…b779BaseBase$0.0001100%daydreams351d ago0x13b873…538a21
0x02de…a7e20x6482…b779BaseBase$0.0001100%daydreams351d ago0xa4cbad…cf93e3
0x02de…a7e20x6482…b779BaseBase$0.0001100%daydreams351d ago0x9acf95…62bc23
0x02de…a7e20x6482…b779BaseBase$0.0001100%daydreams351d ago0xf9c426…30a264
0x02de…a7e20x6482…b779BaseBase$0.0001100%daydreams351d ago0x5783aa…210d5e
0x02de…a7e20x6482…b779BaseBase$0.0001100%daydreams351d ago0x13d84f…c1d23a
0x02de…a7e20x6482…b779BaseBase$0.0001100%daydreams352d ago0xc5a7ce…b0a892
0x02de…a7e20x6482…b779BaseBase$0.0001100%daydreams352d ago0x7848b4…ac4007
0x02de…a7e20x6482…b779BaseBase$0.0001100%daydreams352d ago0x3b23cc…974f78

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 0x02de…a7e2 has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0x02de752cac0c45664f37bf239237e93e3942a7e2

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: 0x02de…a7e2

curl -s 'https://api.roundhouseai.io/v0/agents/0x02de752cac0c45664f37bf239237e93e3942a7e2'
curl -s 'https://api.roundhouseai.io/v0/entities/0x02de752cac0c45664f37bf239237e93e3942a7e2/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.