AgentReport

0xfe4f…9d62

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

Paid $6.32K of $3.31B indexed (0.0002%).

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

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%$6,318.6022

$6,318.60 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.

  • 0xd208…4659 · last paid 235d ago
    $4,418.60
    1 call

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

  • 0x5953…0b38 · last paid 272d ago
    $1,900.00
    1 call

    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
0xd208…4659$4,418.60$0.001235d agoGraph
0x5953…0b38$1,900.00$0.001272d agoGraph

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

Data quality

70% of volume with one counterparty.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xfe4f…9d620xd208…4659EthereumEthereum$4,418.6070%0xbfa1…1b33235d ago0xda6a84…f99f98
0xfe4f…9d620x5953…0b38EthereumEthereum$1,900.0070%0xbfa1…1b33272d ago0x086633…e6a46e

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

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

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: 0xfe4f…9d62

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