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,510 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%daydreams352d ago0x386f85…b218ec
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams352d ago0xffeb95…635d52
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams352d ago0x5fd60d…6c907f
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams352d ago0xdccad7…ba8886
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams353d ago0xe00b78…595b39
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams353d ago0xc7bdd3…1bafa3
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams353d ago0xed7d0a…9a3034
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams354d ago0xd74ef1…507a99
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams354d ago0xc13ea5…ba7f04
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams355d ago0xecff10…40de3e
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams355d ago0x1e927b…2cdec0
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams356d ago0x8b8547…3d3caf
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams356d ago0xd6b185…9882d1
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams356d ago0xcc5cf0…bfd6b6
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams356d ago0xa24d66…698ec7
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams356d ago0x3f2fb2…a01a9b
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams357d ago0x62e9fd…725f7e
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams357d ago0x572b08…9adc74
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams357d ago0x22a275…d163f8
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams357d ago0x55ced2…6979b8
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams358d ago0x996ce6…66c397
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams358d ago0x4ec9ef…635b86
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams359d ago0xfc3cbb…39c358
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams359d ago0x17a9d4…7a8e6c
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams360d ago0x8246f8…33839d

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.