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%daydreams348d ago0x4aaedf…bbeb2f
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams348d ago0xd59d27…6236a1
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams348d ago0xbc3c92…64ed10
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams349d ago0x76b030…55bdb5
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams349d ago0xdec58f…6d8beb
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams350d ago0xb6a521…abcefa
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams350d ago0x930c6c…f45647
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams350d ago0x726c8c…fd806c
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams350d ago0x7392ce…0761f3
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams350d ago0x5fe475…a0f754
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams350d ago0x0a5025…5723cc
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams351d ago0x9746b8…f0d952
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams351d ago0xd3db08…2bc359
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams351d ago0x31c83a…31b302
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams351d ago0x6e1b0d…9c72f9
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams351d ago0x820c14…a5b53a
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams351d ago0x81c8b9…a5de8b
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams351d ago0xe18c4d…65ad93
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams351d ago0x7edb84…507489
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams351d ago0xf21ce1…9ceb3c
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams351d ago0x2a9e70…dd3bd0
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams352d ago0xabd65a…f26cf7
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams352d ago0x47858f…27346c
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams352d ago0x89386f…e9f175
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams352d ago0x19c08c…c06968

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.