AgentReport

0x1df6…ca33

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

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

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

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

$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
    258 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.00258276d 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 258 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams325d ago0x9bfd92…3b69cb
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams326d ago0x38966d…e949c7
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams326d ago0x81cb5c…2f62d5
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams326d ago0xce92fa…18994b
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams326d ago0x8f14cf…ce6a2d
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams326d ago0x0fa222…2574a2
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams326d ago0x5b7b6b…826947
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams326d ago0x42038a…2b1d74
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams326d ago0xf26d6a…69a7aa
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams326d ago0x9e5960…b80514
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams327d ago0x3aee16…920640
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams327d ago0x4a38ef…4151de
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams327d ago0xaeb881…359651
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams327d ago0x62c923…328d44
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams327d ago0x698f1e…9b0c9c
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams327d ago0xd92d9c…9df713
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams327d ago0x2d2f9f…5c6b15
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams327d ago0x420e78…63bcdb
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams335d ago0x4f6654…a6bc02
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams337d ago0x211784…2ed4b5
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams337d ago0x2c10c3…cbaa81
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams337d ago0xe622ff…b62c42
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams337d ago0xaa213e…a0a232
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams337d ago0x9687b3…14d2e6
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams337d ago0x08dc27…459d6f

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

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

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: 0x1df6…ca33

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