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%daydreams337d ago0x4c9b27…e1d509
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams337d ago0x52908d…9f66f6
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams338d ago0x662af9…ae59b7
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams338d ago0x35cfe6…c7aa02
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams338d ago0xfc4c06…80af71
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams339d ago0xcca5c7…bea334
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams339d ago0x7efd3d…b76e5c
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams339d ago0xd0d206…d0b497
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams339d ago0x9843f6…844563
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams339d ago0xd3d999…2f3cfa
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams339d ago0x229476…b39dc1
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams339d ago0x01264d…5ccd2b
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams340d ago0x111f42…a60cd1
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams340d ago0x8574ad…d44330
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams340d ago0x7a61af…d6d04d
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams340d ago0x18be42…4b55a9
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams340d ago0x2b84d4…2574a9
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams340d ago0xf81231…979ae8
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams340d ago0xb39513…703ede
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams340d ago0x82ab67…3e674d
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams340d ago0x2dbe3f…5a87ed
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams340d ago0xa7ea96…a248e3
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams340d ago0x0b8b6c…b9f232
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams341d ago0x54ba3f…976e51
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams341d ago0x071bd0…71ed30

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.