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%daydreams337d ago0x67db1c…db050b
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams337d ago0x685c50…40ec72
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams338d ago0x40cc77…ad15be
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams338d ago0xddc0b1…c40ed9
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams338d ago0x7747f0…fd92a3
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams339d ago0xe628bd…dfa723
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams339d ago0x79ad7f…e69759
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams339d ago0x9ae3dc…6d9b35
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams339d ago0x86d96b…dad69c
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams339d ago0x1d6915…75eaa5
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams339d ago0x14e941…f399d3
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams339d ago0x723b4d…e75a27
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams340d ago0x8bb0de…776bc4
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams340d ago0x191894…fab7ff
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams340d ago0x8d5ae5…1a29ee
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams340d ago0xd4e4bf…be825f
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams340d ago0xd89542…fa124b
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams340d ago0x9a66c4…202ed2
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams340d ago0x6ba5ee…16a336
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams340d ago0xfbb26e…715f02
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams340d ago0x518fa4…bf48e4
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams340d ago0xf45cba…83c808
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams340d ago0x92c09d…614fc9
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams341d ago0x83cb4f…0ff7af
0x0dfa…4cf70x6482…b779BaseBase$0.0001100%daydreams341d ago0xb6518d…7569d3

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.