AgentReport

0xf1be…b590

0xf1bed0458cb15855bedfff2ed38d9639500db590Explorer
Paid out
$11,409.06↑ 34%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
254↓ 25%
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $11,409.06 of the $3068.58M Roundhouse has indexed across 1,402,722 wallets — 0.0004% of it.

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

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%$11,409.062541

$11,409.06 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 3d ago
    $11,409.06
    254 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$11,409.06$0.002543d 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 254 observed settlements.

Organic volume $11,409.06 of $11,409.06 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf1be…b5900x7dbb…59e0EthereumEthereum$17.0570%0x323a…a4f2308d ago0x3508d8…1bd45a
0xf1be…b5900x7dbb…59e0EthereumEthereum$10.5170%0x323a…a4f2313d ago0x0ee390…bc4fb1
0xf1be…b5900x7dbb…59e0EthereumEthereum$14.5870%0x323a…a4f2313d ago0x9bc559…1c32d4
0xf1be…b5900x7dbb…59e0EthereumEthereum$83.4770%0x323a…a4f2315d ago0x735076…75db3e
0xf1be…b5900x7dbb…59e0EthereumEthereum$68.0970%0x323a…a4f2318d ago0xd89c2f…503c9d
0xf1be…b5900x7dbb…59e0EthereumEthereum$155.3670%0x323a…a4f2320d ago0x280ce4…4b5ad0
0xf1be…b5900x7dbb…59e0EthereumEthereum$106.2370%0x323a…a4f2321d ago0xb6104a…2643d2
0xf1be…b5900x7dbb…59e0EthereumEthereum$339.6470%0x323a…a4f2322d ago0x177944…a3d16d
0xf1be…b5900x7dbb…59e0EthereumEthereum$31.1370%0x323a…a4f2325d ago0x698cf5…afe237
0xf1be…b5900x7dbb…59e0EthereumEthereum$40.8670%0x323a…a4f2327d ago0xe201f4…0b52d4
0xf1be…b5900x7dbb…59e0EthereumEthereum$35.9970%0x323a…a4f2329d ago0x7c6661…c9ed06
0xf1be…b5900x7dbb…59e0EthereumEthereum$20.2870%0x323a…a4f2332d ago0xab61d2…f2cdec
0xf1be…b5900x7dbb…59e0EthereumEthereum$16.9570%0x323a…a4f2332d ago0xf9405a…498268
0xf1be…b5900x7dbb…59e0EthereumEthereum$17.1370%0x323a…a4f2335d ago0x2433d2…9ca9a5
0xf1be…b5900x7dbb…59e0EthereumEthereum$6.1970%0x323a…a4f2336d ago0x1043d1…7e31e5
0xf1be…b5900x7dbb…59e0EthereumEthereum$41.7770%0x323a…a4f2339d ago0x8b9f89…d5fabf
0xf1be…b5900x7dbb…59e0EthereumEthereum$159.7670%0x323a…a4f2341d ago0x17d0f5…321f0b
0xf1be…b5900x7dbb…59e0EthereumEthereum$87.1070%0x323a…a4f2342d ago0xa467ee…983f3f
0xf1be…b5900x7dbb…59e0EthereumEthereum$73.7570%0x323a…a4f2343d ago0x64d487…cfacd8
0xf1be…b5900x7dbb…59e0EthereumEthereum$17.4870%0x323a…a4f2346d ago0x8f289f…253f1e
0xf1be…b5900x7dbb…59e0EthereumEthereum$24.4070%0x323a…a4f2346d ago0xee0869…ee53ea
0xf1be…b5900x7dbb…59e0EthereumEthereum$94.2170%0x323a…a4f2349d ago0xcc7e26…29bf53
0xf1be…b5900x7dbb…59e0EthereumEthereum$76.8170%0x323a…a4f2350d ago0xd770c1…ca2988
0xf1be…b5900x7dbb…59e0EthereumEthereum$24.0470%0x323a…a4f2352d ago0x84aa88…b3f16a
0xf1be…b5900x7dbb…59e0EthereumEthereum$69.3870%0x323a…a4f2356d ago0x32a9fc…b71475

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

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

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: 0xf1be…b590

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