AgentReport

0xff68…72da

0xff68b8329a4e9504c99a84439e9b79ad39ae72daExplorer
Paid out
$400.05↓ 100%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
41↓ 100%
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $400.05 of the $3214.08M Roundhouse has indexed across 1,444,054 wallets — less than 0.0001% of it.

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

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%$400.05411

$400.05 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.

  • 0x5c7b…35c5 · last paid 13d ago
    $400.05
    41 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
0x5c7b…35c5$400.05$0.004113d 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 41 observed settlements.

Organic volume $400.05 of $400.05 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xff68…72da0x5c7b…35c5EthereumEthereum$10.5070%0xc10a…ae5d13d ago0x09245d…743c8e
0xff68…72da0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a30d ago0x6ab47d…aa4297
0xff68…72da0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a46d ago0xecb929…100940
0xff68…72da0x5c7b…35c5EthereumEthereum$10.5070%0xc10a…ae5d56d ago0xdbc25a…1e11e5
0xff68…72da0x5c7b…35c5EthereumEthereum$10.5070%0xc10a…ae5d56d ago0xb1ea4f…995eb8
0xff68…72da0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a56d ago0x572e6d…499594
0xff68…72da0x5c7b…35c5EthereumEthereum$26.2570%0xc10a…ae5d58d ago0xc41096…2f486c
0xff68…72da0x5c7b…35c5EthereumEthereum$10.5070%0xc10a…ae5d59d ago0x98759c…6c2d45
0xff68…72da0x5c7b…35c5EthereumEthereum$10.5070%0xc10a…ae5d64d ago0xd1568c…215d30
0xff68…72da0x5c7b…35c5EthereumEthereum$10.5070%0xc10a…ae5d64d ago0x86a88b…74cc74
0xff68…72da0x5c7b…35c5EthereumEthereum$10.5070%0xe459…e4de71d ago0x130e39…86a50f
0xff68…72da0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a73d ago0xa721d8…518392
0xff68…72da0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a73d ago0x6afb60…1b3ce8
0xff68…72da0x5c7b…35c5EthereumEthereum$10.5070%0xc10a…ae5d74d ago0x9d472a…10c59e
0xff68…72da0x5c7b…35c5EthereumEthereum$26.2570%0xd016…b67a74d ago0x0abf30…9a308c
0xff68…72da0x5c7b…35c5EthereumEthereum$10.5070%0xe459…e4de74d ago0x28e132…3aa640
0xff68…72da0x5c7b…35c5EthereumEthereum$10.5070%0xc10a…ae5d74d ago0x84dc36…de99c8
0xff68…72da0x5c7b…35c5EthereumEthereum$10.5070%0xc10a…ae5d74d ago0x18c8c8…5b869c
0xff68…72da0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a74d ago0x571c81…592a50
0xff68…72da0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a74d ago0x12c272…53d01a
0xff68…72da0x5c7b…35c5EthereumEthereum$10.5070%0xc10a…ae5d74d ago0xa7958f…ef1cb0
0xff68…72da0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a74d ago0x0d5c35…275592
0xff68…72da0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a74d ago0xfde5de…bc6cbe
0xff68…72da0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a75d ago0x2b0446…38606c
0xff68…72da0x5c7b…35c5EthereumEthereum$15.7570%0xd016…b67a75d ago0xac59fe…a5575f

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

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

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: 0xff68…72da

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