AgentReport

0x0dfb…74a0

0x0dfb85495332fc575f0691076ebe74e2859774a0Explorer
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 $3067.84M Roundhouse has indexed across 1,401,919 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
0x0dfb…74a00x6482…b779BaseBase$0.0001100%daydreams341d ago0x02e10d…270a05
0x0dfb…74a00x6482…b779BaseBase$0.0001100%daydreams341d ago0x02fcb0…0cfd9b
0x0dfb…74a00x6482…b779BaseBase$0.0001100%daydreams341d ago0x49283b…db8c39
0x0dfb…74a00x6482…b779BaseBase$0.0001100%daydreams341d ago0xed4119…9b577d
0x0dfb…74a00x6482…b779BaseBase$0.0001100%daydreams341d ago0xa9fe74…5169e2
0x0dfb…74a00x6482…b779BaseBase$0.0001100%daydreams341d ago0xd608ac…7d2a0b
0x0dfb…74a00x6482…b779BaseBase$0.0001100%daydreams342d ago0xd135d9…82bd12
0x0dfb…74a00x6482…b779BaseBase$0.0001100%daydreams342d ago0x9412f4…24be34
0x0dfb…74a00x6482…b779BaseBase$0.0001100%daydreams342d ago0xe42d62…e617fd
0x0dfb…74a00x6482…b779BaseBase$0.0001100%daydreams342d ago0x7da55d…caccc0
0x0dfb…74a00x6482…b779BaseBase$0.0001100%daydreams342d ago0xefacea…616c82
0x0dfb…74a00x6482…b779BaseBase$0.0001100%daydreams342d ago0xb9787f…6ff220
0x0dfb…74a00x6482…b779BaseBase$0.0001100%daydreams342d ago0xba0a83…3ba14a
0x0dfb…74a00x6482…b779BaseBase$0.0001100%daydreams342d ago0x81d6c5…28b728
0x0dfb…74a00x6482…b779BaseBase$0.0001100%daydreams342d ago0xb8c5ab…9853f7
0x0dfb…74a00x6482…b779BaseBase$0.0001100%daydreams342d ago0xb9728e…0d49dd
0x0dfb…74a00x6482…b779BaseBase$0.0001100%daydreams342d ago0x7b7a78…97bccc
0x0dfb…74a00x6482…b779BaseBase$0.0001100%daydreams342d ago0x588dcd…3126ff
0x0dfb…74a00x6482…b779BaseBase$0.0001100%daydreams343d ago0xa984a7…44dd2f
0x0dfb…74a00x6482…b779BaseBase$0.0001100%daydreams343d ago0x88d385…cdd5ad
0x0dfb…74a00x6482…b779BaseBase$0.0001100%daydreams343d ago0x999aa8…094084
0x0dfb…74a00x6482…b779BaseBase$0.0001100%daydreams343d ago0x43f08f…5b0b99
0x0dfb…74a00x6482…b779BaseBase$0.0001100%daydreams343d ago0x01997d…66b11b
0x0dfb…74a00x6482…b779BaseBase$0.0001100%daydreams343d ago0x6b8811…7088e8
0x0dfb…74a00x6482…b779BaseBase$0.0001100%daydreams343d ago0xbaf577…6f6c2e

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

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

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: 0x0dfb…74a0

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