AgentReport

0x5b60…3a6e

0x5b6084a46d8a072a8c7ecf7a6ec3c177e0083a6eExplorer
Paid out
$1,359.75
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
65
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $1,359.75 of the $3210.96M Roundhouse has indexed across 1,442,756 wallets — less than 0.0001% of it.

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

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%$1,359.75651

$1,359.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 34d ago
    $1,359.75
    65 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$1,359.75$0.006534d 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 65 observed settlements.

Organic volume $1,359.75 of $1,359.75 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x5b60…3a6e0x5c7b…35c5EthereumEthereum$26.2570%0xe459…e4de34d ago0x6d78dc…f57116
0x5b60…3a6e0x5c7b…35c5EthereumEthereum$52.5070%0xd016…b67a68d ago0x018f50…35700b
0x5b60…3a6e0x5c7b…35c5EthereumEthereum$21.0070%0xd016…b67a69d ago0x4c7683…f6f66f
0x5b60…3a6e0x5c7b…35c5EthereumEthereum$18.9070%0xd016…b67a75d ago0xe1b60a…c19b21
0x5b60…3a6e0x5c7b…35c5EthereumEthereum$21.0070%0xd016…b67a78d ago0xca6574…0a15cf
0x5b60…3a6e0x5c7b…35c5EthereumEthereum$21.0070%0xd016…b67a89d ago0x7a8a50…213afa
0x5b60…3a6e0x5c7b…35c5EthereumEthereum$10.5070%0xc10a…ae5d90d ago0xcdcb0b…cea53d
0x5b60…3a6e0x5c7b…35c5EthereumEthereum$10.5070%0xe459…e4de90d ago0xfa5b8a…d56281
0x5b60…3a6e0x5c7b…35c5EthereumEthereum$10.5070%0xe459…e4de90d ago0x86084a…1c5c99
0x5b60…3a6e0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a91d ago0x444bd2…354351
0x5b60…3a6e0x5c7b…35c5EthereumEthereum$8.4070%0xd016…b67a91d ago0x645603…af66c9
0x5b60…3a6e0x5c7b…35c5EthereumEthereum$15.7570%0xd016…b67a91d ago0xc85b38…591249
0x5b60…3a6e0x5c7b…35c5EthereumEthereum$7.3570%0xc10a…ae5d91d ago0x85e848…0d7fae
0x5b60…3a6e0x5c7b…35c5EthereumEthereum$8.4070%0xc10a…ae5d92d ago0x4c56e2…a23a6c
0x5b60…3a6e0x5c7b…35c5EthereumEthereum$10.5070%0xc10a…ae5d92d ago0x0fb81d…a2970f
0x5b60…3a6e0x5c7b…35c5EthereumEthereum$10.5070%0xc10a…ae5d92d ago0xaa3e74…11e58b
0x5b60…3a6e0x5c7b…35c5EthereumEthereum$21.0070%0xc10a…ae5d93d ago0xaaf51b…d792b2
0x5b60…3a6e0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a97d ago0x6e0bec…778fb3
0x5b60…3a6e0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a97d ago0xf16aa1…98f62b
0x5b60…3a6e0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a97d ago0xa6057b…bf38ee
0x5b60…3a6e0x5c7b…35c5EthereumEthereum$10.5070%0xc10a…ae5d97d ago0xd5297e…d75979
0x5b60…3a6e0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a97d ago0x499ba3…a114fc
0x5b60…3a6e0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a97d ago0x625b3a…8582c3
0x5b60…3a6e0x5c7b…35c5EthereumEthereum$21.0070%0xd016…b67a97d ago0x76a09f…ce4254
0x5b60…3a6e0x5c7b…35c5EthereumEthereum$31.5070%0xc10a…ae5d97d ago0xcf02ee…4d7b3a

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

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

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: 0x5b60…3a6e

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