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.17M Roundhouse has indexed across 1,400,092 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%daydreams326d ago0x6ab979…06d796
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams326d ago0x5db0fe…1bbdde
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams326d ago0x2804ab…c0f255
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams326d ago0x4a5544…fd48d3
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams326d ago0xb37407…fbbbde
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams326d ago0x694210…f53f94
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams326d ago0x0990a3…1a41e9
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams326d ago0x56347b…7485cf
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams327d ago0x0d3ba8…82b761
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams327d ago0xf59203…b971d0
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams327d ago0x58e054…d02d5b
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams327d ago0x580f8c…05ba92
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams327d ago0x6a7013…7f0a3b
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams327d ago0xf0a8e1…a66542
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams327d ago0x01d328…468cca
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams328d ago0x273214…861baf
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams335d ago0xd3985a…a422b4
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams337d ago0x3c66e2…2c0688
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams337d ago0x208780…a58e85
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams337d ago0xc9c852…85e326
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams337d ago0xca8fca…4984aa
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams337d ago0xadf3ae…7cde26
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams337d ago0x8c3bae…c80c98
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams337d ago0xe58949…fdbd4a
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams337d ago0xacc36a…cd69ee

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.