AgentReport

0xf0f0…5fde

0xf0f05037b25ae68136e79f415ee08a3d7ed05fdeExplorer
Paid out
$10,284.13↑ 127%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
52↑ 100%
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $10,284.13 of the $3063.55M Roundhouse has indexed across 1,399,142 wallets — 0.0003% of it.

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

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%$10,284.13521

$10,284.13 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 2d ago
    $10,284.13
    52 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$10,284.13$0.00522d 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 52 observed settlements.

Organic volume $10,284.13 of $10,284.13 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf0f0…5fde0x7dbb…59e0EthereumEthereum$100.7170%0x323a…a4f292d ago0xc493b7…8fc234
0xf0f0…5fde0x7dbb…59e0EthereumEthereum$40.0070%0x323a…a4f296d ago0xfca488…cdd26b
0xf0f0…5fde0x7dbb…59e0EthereumEthereum$408.8070%0x323a…a4f2105d ago0xcd73d7…b63900
0xf0f0…5fde0x7dbb…59e0EthereumEthereum$399.5070%0x323a…a4f2107d ago0xbdebce…052570
0xf0f0…5fde0x7dbb…59e0EthereumEthereum$82.1070%0x323a…a4f2117d ago0xe1a488…9f9bb1
0xf0f0…5fde0x7dbb…59e0EthereumEthereum$76.0070%0x323a…a4f2133d ago0xfee3c9…6efd42
0xf0f0…5fde0x7dbb…59e0EthereumEthereum$99.9070%0x323a…a4f2156d ago0x20bb23…c7a04b
0xf0f0…5fde0x7dbb…59e0EthereumEthereum$99.8050%0x323a…a4f2158d ago0x44c680…78a76d
0xf0f0…5fde0x7dbb…59e0EthereumEthereum$78.7070%0x323a…a4f2165d ago0x465f70…e5632b
0xf0f0…5fde0x7dbb…59e0EthereumEthereum$41.0070%0x323a…a4f2167d ago0xfeffc2…74525e
0xf0f0…5fde0x7dbb…59e0EthereumEthereum$300.5070%0x323a…a4f2173d ago0x7c7df9…d193e1
0xf0f0…5fde0x7dbb…59e0EthereumEthereum$30.0070%0x323a…a4f2174d ago0x9e7282…758c5d
0xf0f0…5fde0x7dbb…59e0EthereumEthereum$101.2570%0x323a…a4f2174d ago0xa62a51…1bf41f
0xf0f0…5fde0x7dbb…59e0EthereumEthereum$190.0070%0x323a…a4f2183d ago0x9be722…388a01
0xf0f0…5fde0x7dbb…59e0EthereumEthereum$230.0070%0x323a…a4f2194d ago0xa44dc6…3ec10b
0xf0f0…5fde0x7dbb…59e0EthereumEthereum$100.0070%0x323a…a4f2199d ago0x4ff48c…19a83a
0xf0f0…5fde0x7dbb…59e0EthereumEthereum$209.0070%0x323a…a4f2210d ago0xf365a4…f5b63d
0xf0f0…5fde0x7dbb…59e0EthereumEthereum$209.9070%0x323a…a4f2218d ago0xf988ed…54e2ac
0xf0f0…5fde0x7dbb…59e0EthereumEthereum$446.4070%0x323a…a4f2230d ago0xf4a1c7…679260
0xf0f0…5fde0x7dbb…59e0EthereumEthereum$369.4270%0x323a…a4f2240d ago0xa983b7…942e6a
0xf0f0…5fde0x7dbb…59e0EthereumEthereum$69.4070%0x323a…a4f2254d ago0xd44541…b0e12b
0xf0f0…5fde0x7dbb…59e0EthereumEthereum$101.0070%0x323a…a4f2255d ago0x548be4…ee05b9
0xf0f0…5fde0x7dbb…59e0EthereumEthereum$220.0070%0x323a…a4f2261d ago0x22a6f1…badf6f
0xf0f0…5fde0x7dbb…59e0EthereumEthereum$803.5070%0x323a…a4f2265d ago0x1e7330…2ac910
0xf0f0…5fde0x7dbb…59e0EthereumEthereum$250.0070%0x323a…a4f2282d ago0x18084b…7c3b09

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

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

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: 0xf0f0…5fde

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