AgentReport

0x0dfa…4cf7

0x0dfa1e898f21a9b50b61ef8928b434869b244cf7Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
262
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 (262)

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.032621

$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
    262 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.00262276d 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 262 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams345d ago0x22445d…dcf544
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams345d ago0x65a7f2…9a263a
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams345d ago0x59d924…cfdff0
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams346d ago0x91958d…1a3b10
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams346d ago0xcbc357…800fe3
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams346d ago0xf33f06…91d007
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams346d ago0x241d9e…fac9f2
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams346d ago0x759279…d56b8b
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams346d ago0xcd298f…b568df
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams346d ago0x728bd5…1d8168
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams346d ago0x5b232c…ee9d8f
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams346d ago0x175866…e72737
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams347d ago0x28353c…d09897
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams347d ago0x9ea7ea…593ce8
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams347d ago0x89d486…974241
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams347d ago0xd2944c…e75e6a
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams347d ago0x4d9056…ea954a
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams347d ago0xf045d7…847353
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams348d ago0xafc763…76cea9
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams348d ago0x0612fc…b35963
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams348d ago0xa658e1…74776f
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams348d ago0xb1ee3a…31f908
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams348d ago0x42e949…2fa628
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams348d ago0xeef1f3…2192a0
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams348d ago0xd067f6…57577f

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 0x0dfa…4cf7 has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0x0dfa1e898f21a9b50b61ef8928b434869b244cf7

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: 0x0dfa…4cf7

curl -s 'https://api.roundhouseai.io/v0/agents/0x0dfa1e898f21a9b50b61ef8928b434869b244cf7'
curl -s 'https://api.roundhouseai.io/v0/entities/0x0dfa1e898f21a9b50b61ef8928b434869b244cf7/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.