AgentReport

0x45cc…8ee9

0x45cc6f5a6d5a5684f8b9d257efbd9ffe0b2f8ee9Explorer
$246.75
Paid out
$0.00
Received
3
Settlements
1
Distinct counterparties
Over the whole indexed history

Paid $246.75 of the $3217.31M Roundhouse has indexed across 1,445,802 wallets — less than 0.0001% of it.

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

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

$246.75 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 45d ago
    $246.75
    3 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…

Activity

MayJunJulAugSepOctNov
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x5c7b…35c5$246.75$0.00345d 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 3 observed settlements.

Organic volume $246.75 of $246.75 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x45cc…8ee90x5c7b…35c5EthereumEthereum$152.2570%0xc10a…ae5d45d ago0x78ddf9…e1223f
0x45cc…8ee90x5c7b…35c5EthereumEthereum$73.5070%0xe459…e4de45d ago0x427b16…962d15
0x45cc…8ee90x5c7b…35c5EthereumEthereum$21.0070%0xd016…b67a45d ago0xdff421…5db8f7

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

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

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: 0x45cc…8ee9

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