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.17M Roundhouse has indexed across 1,400,092 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%daydreams325d ago0xf36b33…2a1311
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams326d ago0x73c6c0…e01a58
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams326d ago0xbcd7bb…f94d64
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams326d ago0x0d08c3…af19f1
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams326d ago0xc294d8…446edc
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams326d ago0xdfd477…5268af
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams326d ago0xff0c7f…52aa73
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams326d ago0x26019e…48c6a2
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams326d ago0x752bb8…e31945
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams326d ago0x3b7e16…beff56
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams326d ago0x1bb358…bb2e4a
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams327d ago0xd8963a…8e468f
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams327d ago0x219ce0…e206ed
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams327d ago0xffb2e7…809a7c
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams327d ago0x87f6a7…71b6bd
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams327d ago0xa55b7d…7f7362
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams327d ago0x8d4e36…d62ad8
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams327d ago0x9583a9…74bd42
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams335d ago0x4804cb…965cfe
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams337d ago0x9dac02…819cea
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams337d ago0xaf8118…4e565f
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams337d ago0xe79822…a1ec67
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams337d ago0xd1ead8…e04251
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams337d ago0x32d87f…77a079
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams337d ago0xd14e10…a1e39b

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.