AgentReport

0x2603…37e4

0x26030abc6857bb5820ead1a0dda9eb9df27937e4Explorer
Paid out
$166.95
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
6
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $166.95 of the $3216.53M Roundhouse has indexed across 1,445,272 wallets — less than 0.0001% of it.

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

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

$166.95 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 63d ago
    $166.95
    6 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$166.95$0.00663d 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 6 observed settlements.

Organic volume $166.95 of $166.95 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x2603…37e40x5c7b…35c5EthereumEthereum$72.4570%0xd016…b67a63d ago0xc8c801…b59ecf
0x2603…37e40x5c7b…35c5EthereumEthereum$14.7070%0xc10a…ae5d64d ago0x15786d…734efa
0x2603…37e40x5c7b…35c5EthereumEthereum$16.8070%0xd016…b67a64d ago0xc02f2f…86a814
0x2603…37e40x5c7b…35c5EthereumEthereum$18.9070%0xe459…e4de64d ago0xe7d607…1bc775
0x2603…37e40x5c7b…35c5EthereumEthereum$30.4570%0xc10a…ae5d65d ago0x90195e…f27819
0x2603…37e40x5c7b…35c5EthereumEthereum$13.6570%0xd016…b67a66d ago0xfa793d…495c95

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

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

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: 0x2603…37e4

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