AgentReport

0xf2f8…9aa5

0xf2f85e06e3aef7de9a78e1d5e6cd5ee97d7e9aa5Explorer
Paid out
$52,915.60↓ 88%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
49↓ 80%
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $52,915.60 of the $3105.41M Roundhouse has indexed across 1,405,967 wallets — 0.0017% of it.

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

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%$52,915.60491

$52,915.60 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.

  • 0x7dbb…59e0 · last paid 7m ago
    $52,915.60
    49 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
0x7dbb…59e0$52,915.60$0.00497m 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 49 observed settlements.

Organic volume $52,915.60 of $52,915.60 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf2f8…9aa50x7dbb…59e0EthereumEthereum$880.0070%0x323a…a4f27m ago0x7ea27a…444ee0
0xf2f8…9aa50x7dbb…59e0EthereumEthereum$1,991.1370%0x323a…a4f26d ago0x64868c…b1f51c
0xf2f8…9aa50x7dbb…59e0EthereumEthereum$587.8270%0x323a…a4f27d ago0xfbfea6…f9f820
0xf2f8…9aa50x7dbb…59e0EthereumEthereum$1,468.5470%0x323a…a4f27d ago0x1920c3…29a898
0xf2f8…9aa50x7dbb…59e0EthereumEthereum$2,190.0070%0x323a…a4f27d ago0xfd8ead…e3f5c9
0xf2f8…9aa50x7dbb…59e0EthereumEthereum$1,392.6870%0x323a…a4f29d ago0x9577cd…518ec2
0xf2f8…9aa50x7dbb…59e0EthereumEthereum$1,122.9470%0x323a…a4f221d ago0xb6a050…510aeb
0xf2f8…9aa50x7dbb…59e0EthereumEthereum$795.6970%0x323a…a4f226d ago0x671a82…f33e54
0xf2f8…9aa50x7dbb…59e0EthereumEthereum$828.8670%0x323a…a4f226d ago0x06229c…5f0598
0xf2f8…9aa50x7dbb…59e0EthereumEthereum$656.6570%0x323a…a4f228d ago0x11b5b0…b548de
0xf2f8…9aa50x7dbb…59e0EthereumEthereum$48.4570%0x323a…a4f229d ago0x8c211c…a93d07
0xf2f8…9aa50x7dbb…59e0EthereumEthereum$603.9770%0x323a…a4f232d ago0x5a704c…d99d97
0xf2f8…9aa50x7dbb…59e0EthereumEthereum$744.0670%0x323a…a4f233d ago0x0dfb6b…c578a3
0xf2f8…9aa50x7dbb…59e0EthereumEthereum$2,989.3670%0x323a…a4f236d ago0xe41d46…b67316
0xf2f8…9aa50x7dbb…59e0EthereumEthereum$497.0970%0x323a…a4f239d ago0xef13ff…16be94
0xf2f8…9aa50x7dbb…59e0EthereumEthereum$945.7070%0x323a…a4f239d ago0x6f2bd7…bbed3a
0xf2f8…9aa50x7dbb…59e0EthereumEthereum$894.9970%0x323a…a4f240d ago0x5c45c4…903510
0xf2f8…9aa50x7dbb…59e0EthereumEthereum$2,043.0670%0x323a…a4f240d ago0x6b3418…e5b301
0xf2f8…9aa50x7dbb…59e0EthereumEthereum$119.8270%0x323a…a4f247d ago0x71e9c1…6f90a0
0xf2f8…9aa50x7dbb…59e0EthereumEthereum$565.9970%0x323a…a4f247d ago0x6ccf10…9c2b8d
0xf2f8…9aa50x7dbb…59e0EthereumEthereum$673.4870%0x323a…a4f250d ago0xd85d97…094924
0xf2f8…9aa50x7dbb…59e0EthereumEthereum$3,271.7070%0x323a…a4f252d ago0xdbf2ac…60602d
0xf2f8…9aa50x7dbb…59e0EthereumEthereum$332.0670%0x323a…a4f256d ago0x139819…32a21c
0xf2f8…9aa50x7dbb…59e0EthereumEthereum$5,484.2870%0x323a…a4f258d ago0x72089a…917b9d
0xf2f8…9aa50x7dbb…59e0EthereumEthereum$1,217.4770%0x323a…a4f260d ago0x2c00d2…90c85a

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

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

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: 0xf2f8…9aa5

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