AgentReport

0xdf7c…bf8d

0xdf7cc470213f1224ac8d6bf35480b66b4352bf8dExplorer
Paid out
$2,472.11
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
7
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $2,472.11 of the $3105.10M Roundhouse has indexed across 1,405,259 wallets — less than 0.0001% of it.

Chains (from the recent scan): Ethereum (7)

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%$2,472.1172

$2,472.11 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.

  • 0x0629…5506 · last paid 96d ago
    $1,516.63
    4 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x42ec…7160 · last paid 252d ago
    $955.48
    3 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
0x0629…5506$1,516.63$0.00496d agoGraph
0x42ec…7160$955.48$0.003252d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

61% of observed volume is with a single counterparty, in all 7 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xdf7c…bf8d0x0629…5506EthereumEthereum$477.9370%0xe528…c02896d ago0x69c1ee…e80fb6
0xdf7c…bf8d0x0629…5506EthereumEthereum$351.1170%0x23ef…243198d ago0x133269…390b62
0xdf7c…bf8d0x0629…5506EthereumEthereum$346.2470%0x23ef…2431153d ago0xae9dbd…fd91df
0xdf7c…bf8d0x0629…5506EthereumEthereum$341.3570%0xe528…c028158d ago0x9e467a…7b6ed6
0xdf7c…bf8d0x42ec…7160EthereumEthereum$351.2070%0x42ec…7160252d ago0xbdb0c0…b9fd6e
0xdf7c…bf8d0x42ec…7160EthereumEthereum$306.8570%0x42ec…7160277d ago0xbc42cc…79f180
0xdf7c…bf8d0x42ec…7160EthereumEthereum$297.4370%0x42ec…7160278d ago0x6c5707…300552

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

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

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: 0xdf7c…bf8d

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