AgentReport

0xbe9f…0562

0xbe9f3a3ff4423993e0fd9e9dd061b3c7dc280562Explorer
Paid out
$3,035.00
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
19
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

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

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

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%$3,035.00191

$3,035.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 38d ago
    $3,035.00
    19 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$3,035.00$0.001938d 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 19 observed settlements.

Organic volume $3,035.00 of $3,035.00 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xbe9f…05620x5c7b…35c5EthereumEthereum$157.5070%0xd016…b67a38d ago0xc05de8…5ece6a
0xbe9f…05620x5c7b…35c5EthereumEthereum$210.0070%0xd016…b67a38d ago0x16f21f…bec34f
0xbe9f…05620x5c7b…35c5EthereumEthereum$105.0070%0xe459…e4de46d ago0x0662b4…cc56e5
0xbe9f…05620x5c7b…35c5EthereumEthereum$105.0070%0xc10a…ae5d50d ago0x93e9c2…6c0c49
0xbe9f…05620x5c7b…35c5EthereumEthereum$105.0070%0xc10a…ae5d63d ago0x6e3e80…7f8894
0xbe9f…05620x5c7b…35c5EthereumEthereum$105.0070%0xd016…b67a64d ago0xa3bcc3…22053d
0xbe9f…05620x5c7b…35c5EthereumEthereum$210.0070%0xd016…b67a66d ago0x4d9059…fd3af1
0xbe9f…05620x5c7b…35c5EthereumEthereum$210.0070%0xc10a…ae5d72d ago0x4c6853…abcfa9
0xbe9f…05620x5c7b…35c5EthereumEthereum$315.0070%0xd016…b67a74d ago0x2705aa…c5099c
0xbe9f…05620x5c7b…35c5EthereumEthereum$262.5070%0xc10a…ae5d75d ago0x45e8dd…4a8931
0xbe9f…05620x5c7b…35c5EthereumEthereum$210.0070%0xc10a…ae5d75d ago0xb70df9…f852bf
0xbe9f…05620x5c7b…35c5EthereumEthereum$210.0070%0xd016…b67a76d ago0xfbaa5c…e6de0d
0xbe9f…05620x5c7b…35c5EthereumEthereum$105.0050%0xc10a…ae5d76d ago0x99e5c4…a31e60
0xbe9f…05620x5c7b…35c5EthereumEthereum$105.0070%0xd016…b67a76d ago0x1da0bc…5e353e
0xbe9f…05620x5c7b…35c5EthereumEthereum$105.0070%0xe459…e4de85d ago0x63314e…301b77
0xbe9f…05620x5c7b…35c5EthereumEthereum$210.0070%0xd016…b67a88d ago0x876ffa…2203d0
0xbe9f…05620x5c7b…35c5EthereumEthereum$105.0070%0xd016…b67a88d ago0x8fe41c…6596fa
0xbe9f…05620x5c7b…35c5EthereumEthereum$105.0070%0xe459…e4de89d ago0x26d511…ad633b
0xbe9f…05620x5c7b…35c5EthereumEthereum$95.0070%0xd016…b67a183d ago0xd83528…668a58

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

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

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: 0xbe9f…0562

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