AgentReport

0xf969…a6bd

0xf9690d930a80f89ff5bf7be037e3b96d1ceea6bdExplorer
Paid out
$145.48↓ 100%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
6↓ 100%
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $145.48 of the $3216.53M Roundhouse has indexed across 1,445,272 wallets — less than 0.0001% of it.

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

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

$145.48 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
    $145.48
    6 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$145.48$0.0068d 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 6 observed settlements.

Organic volume $145.48 of $145.48 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf969…a6bd0x5c7b…35c5EthereumEthereum$18.9070%0xe459…e4de8d ago0xa3bc4f…ece8f7
0xf969…a6bd0x5c7b…35c5EthereumEthereum$21.0070%0xd016…b67a38d ago0xd43a81…5106bd
0xf969…a6bd0x5c7b…35c5EthereumEthereum$21.0070%0xc10a…ae5d50d ago0x2aa4c0…b5f2cf
0xf969…a6bd0x5c7b…35c5EthereumEthereum$21.0070%0xe459…e4de70d ago0x686888…d274b5
0xf969…a6bd0x5c7b…35c5EthereumEthereum$11.0870%0xc10a…ae5d206d ago0xc842cf…a2b069
0xf969…a6bd0x5c7b…35c5EthereumEthereum$52.5070%0xd016…b67a220d ago0xa17eca…7a8990

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

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

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: 0xf969…a6bd

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