AgentReport

0xdf4c…8711

0xdf4c42f5fe1b6c5782f944d2035720399c0e8711Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
254
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,689 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (254)

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

$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
    254 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.00254276d 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 254 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xdf4c…87110x6482…b779BaseBase$0.0001100%daydreams343d ago0xeb78a6…aecf9a
0xdf4c…87110x6482…b779BaseBase$0.0001100%daydreams343d ago0x948492…7a0c10
0xdf4c…87110x6482…b779BaseBase$0.0001100%daydreams343d ago0x3f0996…67b206
0xdf4c…87110x6482…b779BaseBase$0.0001100%daydreams343d ago0x81b69e…11a101
0xdf4c…87110x6482…b779BaseBase$0.0001100%daydreams343d ago0x4c73a3…12f1de
0xdf4c…87110x6482…b779BaseBase$0.0001100%daydreams344d ago0x80da02…550a9f
0xdf4c…87110x6482…b779BaseBase$0.0001100%daydreams344d ago0x5057f2…f5d0eb
0xdf4c…87110x6482…b779BaseBase$0.0001100%daydreams344d ago0x23ada1…4fc256
0xdf4c…87110x6482…b779BaseBase$0.0001100%daydreams344d ago0xe9c9d3…cd1f19
0xdf4c…87110x6482…b779BaseBase$0.0001100%daydreams344d ago0xb3ab7e…7bf343
0xdf4c…87110x6482…b779BaseBase$0.0001100%daydreams344d ago0x317bc4…9d4af5
0xdf4c…87110x6482…b779BaseBase$0.0001100%daydreams344d ago0x7eab49…b427e6
0xdf4c…87110x6482…b779BaseBase$0.0001100%daydreams344d ago0x4975e4…573eea
0xdf4c…87110x6482…b779BaseBase$0.0001100%daydreams344d ago0x75b181…b64d38
0xdf4c…87110x6482…b779BaseBase$0.0001100%daydreams344d ago0x32bf54…b6100b
0xdf4c…87110x6482…b779BaseBase$0.0001100%daydreams344d ago0x75b417…7e515c
0xdf4c…87110x6482…b779BaseBase$0.0001100%daydreams345d ago0xa3ac41…c8896b
0xdf4c…87110x6482…b779BaseBase$0.0001100%daydreams345d ago0x70f2cc…224c86
0xdf4c…87110x6482…b779BaseBase$0.0001100%daydreams345d ago0x1ad068…ccad61
0xdf4c…87110x6482…b779BaseBase$0.0001100%daydreams345d ago0x443e2a…f7899d
0xdf4c…87110x6482…b779BaseBase$0.0001100%daydreams345d ago0xc0935e…225d18
0xdf4c…87110x6482…b779BaseBase$0.0001100%daydreams345d ago0xb71272…d2c7d0
0xdf4c…87110x6482…b779BaseBase$0.0001100%daydreams345d ago0x571a8a…aa1efb
0xdf4c…87110x6482…b779BaseBase$0.0001100%daydreams345d ago0x65270a…46f3c8
0xdf4c…87110x6482…b779BaseBase$0.0001100%daydreams345d ago0x7e7690…2699b1

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

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

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: 0xdf4c…8711

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