AgentReport

0xb94b…cd9d

0xb94b29e5fd071a5c38d3249a5de509d11a40cd9dExplorer
Paid out
$5,544.17↑ 4.5%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
41↓ 67%
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $5,544.17 of the $3063.55M Roundhouse has indexed across 1,399,142 wallets — 0.0002% of it.

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

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%$5,544.17411

$5,544.17 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 6d ago
    $5,544.17
    41 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$5,544.17$0.00416d 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 41 observed settlements.

Organic volume $5,544.17 of $5,544.17 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xb94b…cd9d0x7dbb…59e0EthereumEthereum$247.9470%0x323a…a4f26d ago0x9d3c96…d02810
0xb94b…cd9d0x7dbb…59e0EthereumEthereum$44.3670%0x323a…a4f27d ago0xf28e3e…c3c3c3
0xb94b…cd9d0x7dbb…59e0EthereumEthereum$148.5270%0x323a…a4f28d ago0x94224e…fe83ba
0xb94b…cd9d0x7dbb…59e0EthereumEthereum$44.3770%0x323a…a4f211d ago0x22fa40…08d4f4
0xb94b…cd9d0x7dbb…59e0EthereumEthereum$44.3970%0x323a…a4f218d ago0x4fcb55…f5cae6
0xb94b…cd9d0x7dbb…59e0EthereumEthereum$44.3770%0x323a…a4f232d ago0xe69d9a…95c53b
0xb94b…cd9d0x7dbb…59e0EthereumEthereum$70.6870%0x323a…a4f233d ago0xad1caa…bfe6d9
0xb94b…cd9d0x7dbb…59e0EthereumEthereum$115.5170%0x323a…a4f251d ago0x908458…9b3ce3
0xb94b…cd9d0x7dbb…59e0EthereumEthereum$93.1670%0x323a…a4f252d ago0xbc5036…6ae4c7
0xb94b…cd9d0x7dbb…59e0EthereumEthereum$44.5670%0x323a…a4f252d ago0xe94d43…68384a
0xb94b…cd9d0x7dbb…59e0EthereumEthereum$94.2270%0x323a…a4f253d ago0xaac9a3…e94efc
0xb94b…cd9d0x7dbb…59e0EthereumEthereum$44.3670%0x323a…a4f253d ago0xd9935a…672afc
0xb94b…cd9d0x7dbb…59e0EthereumEthereum$44.3770%0x323a…a4f253d ago0x3f6a2b…dba589
0xb94b…cd9d0x7dbb…59e0EthereumEthereum$34.4070%0x323a…a4f255d ago0x21c6c7…71f335
0xb94b…cd9d0x7dbb…59e0EthereumEthereum$691.0370%0x323a…a4f257d ago0x8b026e…90f88e
0xb94b…cd9d0x7dbb…59e0EthereumEthereum$34.4170%0x323a…a4f258d ago0x51065f…88150c
0xb94b…cd9d0x7dbb…59e0EthereumEthereum$345.6070%0x323a…a4f259d ago0xe42f3e…8ec3b6
0xb94b…cd9d0x7dbb…59e0EthereumEthereum$44.3870%0x323a…a4f260d ago0x0fbf9d…417c6d
0xb94b…cd9d0x7dbb…59e0EthereumEthereum$44.3950%0x323a…a4f261d ago0x4a93fb…9a32cc
0xb94b…cd9d0x7dbb…59e0EthereumEthereum$94.2950%0x323a…a4f261d ago0xbed0a5…53264c
0xb94b…cd9d0x7dbb…59e0EthereumEthereum$69.3670%0x323a…a4f265d ago0xcf3e1f…742bf8
0xb94b…cd9d0x7dbb…59e0EthereumEthereum$74.3450%0x323a…a4f266d ago0x951993…6c591f
0xb94b…cd9d0x7dbb…59e0EthereumEthereum$94.3170%0x323a…a4f266d ago0x313b2d…054ca1
0xb94b…cd9d0x7dbb…59e0EthereumEthereum$9.2970%0x323a…a4f266d ago0x399482…ac3540
0xb94b…cd9d0x7dbb…59e0EthereumEthereum$274.7670%0x323a…a4f267d ago0x996d77…30da62

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

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

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: 0xb94b…cd9d

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