AgentReport

0x5b6d…ef5c

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

Paid $120.00 of the $3211.44M Roundhouse has indexed across 1,443,675 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%$120.0031

$120.00 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 126d ago
    $120.00
    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$120.00$0.003126d 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 $120.00 of $120.00 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x5b6d…ef5c0x5c7b…35c5EthereumEthereum$100.0070%0xe459…e4de126d ago0x73d1dc…12fad1
0x5b6d…ef5c0x5c7b…35c5EthereumEthereum$10.0070%0xc10a…ae5d126d ago0x94c8b3…1d0fc5
0x5b6d…ef5c0x5c7b…35c5EthereumEthereum$10.0070%0xd016…b67a126d ago0x45c4fd…a5c1cb

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

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

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: 0x5b6d…ef5c

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