AgentReport

0xddf2…d1ab

0xddf2a2150134bcfe015a66492ca54e14a0c4d1abExplorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
256
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,255 wallets — less than 0.0001% of it.

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

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

$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
    256 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.00256276d 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 256 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams345d ago0xe5d3b2…1edc91
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams345d ago0xe4b933…6ca38b
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams346d ago0x80f84e…9a3450
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams346d ago0x2af366…2a970a
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams346d ago0x79f4c9…e4c370
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams346d ago0x359a5e…824cec
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams346d ago0xdb5de5…f4969b
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams346d ago0xc9f193…65c2e1
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams346d ago0x66f531…716ff1
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams346d ago0xff6047…cd9717
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams346d ago0x4063e9…d4fa0c
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams347d ago0x9f4084…112179
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams347d ago0xb123d7…3543e2
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams347d ago0x825747…7d2374
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams347d ago0xdbfe48…1cedd0
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams347d ago0x942a09…9c256f
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams347d ago0xb9a23a…abf2e2
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams348d ago0xe8f759…b82efe
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams348d ago0x208044…54810a
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams348d ago0x8146d8…e65994
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams348d ago0x2ca19b…e7eae5
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams348d ago0x998aec…896a5f
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams348d ago0x0ad40c…a5d1f7
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams348d ago0xbe3888…cd6204
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams348d ago0x7f431c…76c8d4

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

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

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: 0xddf2…d1ab

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