AgentReport

0x5cef…ff1b

0x5cef42c19504d1129704df7db0c44ba71a4dff1bExplorer
Paid out
$10,554.37↓ 100%
Last 7d vs prior 7d
Received
$0.10
Last 7d vs prior 7d
Settlements
4↓ 100%
Last 7d vs prior 7d
3
Distinct counterparties
Over the whole indexed history

Paid $10,554.37 of the $3215.71M Roundhouse has indexed across 1,444,683 wallets — 0.0003% of it.

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

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%$10,554.3721

$10,554.37 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 8d ago
    $10,554.37
    2 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$10,554.37$0.0028d agoGraph
0x51ce…10ba$0.00$0.051244d agoGraph
0x7867…1b3d$0.00$0.051246d 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, in all 4 observed settlements.

Organic volume $10,554.47 of $10,554.47 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x5cef…ff1b0x5c7b…35c5EthereumEthereum$5,141.8870%0xd016…b67a8d ago0x4cccf3…cf1d22
0x5cef…ff1b0x5c7b…35c5EthereumEthereum$5,412.4970%0xd016…b67a9d ago0x18c3e4…b96e68
0x51ce…10ba0x5cef…ff1bEthereumEthereum$0.0570%0x2a93…ecaa244d ago0x2a9172…9b9dfb
0x7867…1b3d0x5cef…ff1bEthereumEthereum$0.0570%0x2a93…ecaa246d ago0x27261e…eef5bd

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

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

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: 0x5cef…ff1b

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