AgentReport

0x11a5…ac1e

0x11a55385ae9a7d961c8c2852c40ea1b8b986ac1eExplorer
Paid out
$58.80
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
2
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $58.80 of the $3126.72M Roundhouse has indexed across 1,420,789 wallets — less than 0.0001% of it.

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

$58.80 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 89d ago
    $58.80
    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$58.80$0.00289d 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 2 observed settlements.

Organic volume $58.80 of $58.80 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x11a5…ac1e0x5c7b…35c5EthereumEthereum$36.7570%0xd016…b67a89d ago0xb08c73…322e9f
0x11a5…ac1e0x5c7b…35c5EthereumEthereum$22.0570%0xd016…b67a125d ago0x75e212…3e4ad4

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

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

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: 0x11a5…ac1e

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