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%daydreams337d ago0x2ad9c9…fa4a32
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams338d ago0xbd9826…1ae431
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams338d ago0x258347…bd9d3d
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams339d ago0x4a8d75…fc730d
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams339d ago0xe995a9…01cac0
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams339d ago0x4f2907…aaebac
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams339d ago0x3f5820…9439f5
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams339d ago0x0d0c41…73b106
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams339d ago0xe2e660…05721f
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams339d ago0xe0295e…02244c
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams340d ago0x06696a…6b8828
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams340d ago0xbba0d7…9b450c
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams340d ago0xecdb3f…38e8e2
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams340d ago0x3b0f89…6b8dee
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams340d ago0x5833af…1ddf3b
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams340d ago0xeedede…fd4145
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams340d ago0x8f8ff6…1bc92e
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams340d ago0x1d7b53…3f61c7
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams340d ago0x887d41…ba1f33
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams340d ago0x850d51…1b1650
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams340d ago0x20783a…ef0fd8
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams341d ago0xb668d6…75ab36
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams341d ago0x35f984…68f404
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams341d ago0x6aedf1…267e4b
0x1df6…ca330x6482…b779BaseBase$0.0001100%daydreams341d ago0xed2301…25e586

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.