AgentReport

0xfcb8…b145

0xfcb87ad7487eb6d91f41eeba33fca8d056e6b145Explorer
Paid out
$458.85
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 $458.85 of the $3211.44M Roundhouse has indexed across 1,443,675 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%$458.8572

$458.85 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 4d ago
    $385.35
    6 calls

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

  • 0x6769…83c5 · last paid 116d ago
    $73.50
    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
0x5c7b…35c5$385.35$0.0064d agoGraph
0x6769…83c5$73.50$0.001116d agoGraph

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

Data quality

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

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xfcb8…b1450x5c7b…35c5EthereumEthereum$49.3570%0xc10a…ae5d4d ago0x74a148…d02f04
0xfcb8…b1450x5c7b…35c5EthereumEthereum$105.0070%0xd016…b67a73d ago0x351b4d…1e1834
0xfcb8…b1450x5c7b…35c5EthereumEthereum$73.5070%0xc10a…ae5d100d ago0x004cd0…c645ea
0xfcb8…b1450x6769…83c5EthereumEthereum$73.5070%0xd016…b67a116d ago0x0ba95f…46b3a3
0xfcb8…b1450x5c7b…35c5EthereumEthereum$52.5070%0xe0df…59a1125d ago0x9f4435…d18a3b
0xfcb8…b1450x5c7b…35c5EthereumEthereum$52.5050%0xe459…e4de127d ago0x61b56e…c7c6f2
0xfcb8…b1450x5c7b…35c5EthereumEthereum$52.5070%0xe459…e4de169d ago0xa31a31…9b49e6

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

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

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: 0xfcb8…b145

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