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%daydreams341d ago0xba3b4f…9d82ee
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams341d ago0x3223a5…c9791c
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams341d ago0x04c934…69cfb0
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams341d ago0x9afd7c…e64f1d
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams341d ago0xe8fa22…9a4453
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams341d ago0x91934f…309c9d
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams341d ago0x802fd8…fb3d9d
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams341d ago0x7bf795…d11f20
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams342d ago0x696309…0f7046
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams342d ago0x0d5c5c…a7905d
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams342d ago0x2a77a0…992ba6
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams342d ago0x71c48d…421ff4
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams342d ago0x7fe2a9…ead4e8
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams342d ago0xa0d30c…f9c213
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams342d ago0xdaaa46…a33e9f
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams342d ago0x20a3c2…2f62f0
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams342d ago0xe3c815…5a3c83
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams343d ago0x063042…8c304e
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams343d ago0x0b388e…4c0b69
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams343d ago0x575fb1…e0f5da
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams343d ago0x8522b7…c38893
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams343d ago0x45b362…df350c
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams343d ago0x786ee6…d48bef
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams343d ago0xb5a696…1ee016
0xddf2…d1ab0x6482…b779BaseBase$0.0001100%daydreams343d ago0x46f745…26c501

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.