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%daydreams348d ago0x147ef2…607aae
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams348d ago0x622a98…5483b6
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams348d ago0x394e3d…443061
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams349d ago0xfb678e…a8f086
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams349d ago0xe10cf4…e8c94d
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams349d ago0x36ff30…8b2004
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams349d ago0xc7b4d4…84a358
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams350d ago0x7ebc92…22edc9
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams350d ago0x055c26…489526
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams350d ago0xefa7f4…de51d6
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams350d ago0x89af4a…db9be5
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams350d ago0x8d9f32…c6350b
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams350d ago0x05aa1e…e12fdc
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams350d ago0x6c6a67…52189b
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams351d ago0xc81df1…771de3
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams351d ago0xf77fdb…e16b6f
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams351d ago0x84ec25…d0fcf1
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams351d ago0x9e0f97…154132
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams351d ago0x4b6756…4dfc86
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams351d ago0x09d814…373879
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams351d ago0xfbe4de…63013c
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams351d ago0x5af16a…a68de3
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams352d ago0x358ff1…cc5911
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams352d ago0x740fb2…d7969d
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams352d ago0x3364ea…ae2fd9

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.