AgentReport

0x60a3…0909

0x60a3458bb1326770de7b9a96f52fb03387810909Explorer
Paid out
$130.20↓ 100%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
5↓ 100%
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $130.20 of the $3220.73M Roundhouse has indexed across 1,448,289 wallets — less than 0.0001% of it.

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

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

$130.20 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 8d ago
    $130.20
    5 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$130.20$0.0058d 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 5 observed settlements.

Organic volume $130.20 of $130.20 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x60a3…09090x5c7b…35c5EthereumEthereum$42.0070%0xc10a…ae5d8d ago0x2f2fb2…a51d9f
0x60a3…09090x5c7b…35c5EthereumEthereum$21.0070%0xd016…b67a13d ago0x6e2b9a…d662a0
0x60a3…09090x5c7b…35c5EthereumEthereum$18.9070%0xd016…b67a30d ago0xb3d927…4a2ffd
0x60a3…09090x5c7b…35c5EthereumEthereum$31.5070%0xe459…e4de48d ago0x03b75d…fa3789
0x60a3…09090x5c7b…35c5EthereumEthereum$16.8070%0xd016…b67a55d ago0xc1cebe…e99e4b

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

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

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: 0x60a3…0909

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