AgentReport

0x61e9…91f8

0x61e93becaccea1ea49f4136bd07c0fff6b6491f8Explorer
Paid out
$960.75
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
7
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $960.75 of the $3116.99M Roundhouse has indexed across 1,419,966 wallets — less than 0.0001% of it.

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

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

$960.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 103d ago
    $698.25
    5 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x6769…83c5 · last paid 115d ago
    $262.50
    2 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$698.25$0.005103d agoGraph
0x6769…83c5$262.50$0.002115d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

73% of observed volume is with a single counterparty, in all 7 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x61e9…91f80x5c7b…35c5EthereumEthereum$236.2570%0xd016…b67a103d ago0xb86876…91fca7
0x61e9…91f80x5c7b…35c5EthereumEthereum$157.5070%0xd016…b67a105d ago0x03b852…723fa7
0x61e9…91f80x5c7b…35c5EthereumEthereum$105.0050%0xd016…b67a107d ago0x68e2a1…b11c1b
0x61e9…91f80x5c7b…35c5EthereumEthereum$94.5070%0xe459…e4de107d ago0x0f9e8f…7f80b8
0x61e9…91f80x5c7b…35c5EthereumEthereum$105.0070%0xe459…e4de112d ago0x2bec57…169567
0x61e9…91f80x6769…83c5EthereumEthereum$157.5070%0xd016…b67a115d ago0xe2e6b5…9ec1f2
0x61e9…91f80x6769…83c5EthereumEthereum$105.0070%0xd016…b67a115d ago0x8cb49a…a42991

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

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

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: 0x61e9…91f8

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