AgentReport

0x94bc…d1e9

0x94bc909412b6c9f36ab9c3a81850517dc924d1e9Explorer
Paid out
$31.10
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
85
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $31.10 of the $847.31M Roundhouse has indexed across 1,331,176 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (85)

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

$31.10 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.

  • 0xef43…6c7f · last paid 288d ago
    $31.10
    85 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

MayJunJulAugSepOct
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0xef43…6c7f$31.10$0.0085288d 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 85 observed settlements.

Organic volume $31.10 of $31.10 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x94bc…d1e90xef43…6c7fBase$0.50100%virtuals320d ago0xfae12f…2b20d1
0x94bc…d1e90xef43…6c7fBase$0.50100%virtuals320d ago0xb1a28a…471297
0x94bc…d1e90xef43…6c7fBase$0.05100%virtuals320d ago0x87650d…56d0df
0x94bc…d1e90xef43…6c7fBase$0.50100%virtuals320d ago0x999512…d8d3cf
0x94bc…d1e90xef43…6c7fBase$0.05100%virtuals320d ago0xd39cc7…0533ba
0x94bc…d1e90xef43…6c7fBase$0.50100%virtuals320d ago0x6c1842…300dc3
0x94bc…d1e90xef43…6c7fBase$0.05100%virtuals320d ago0x797061…018173
0x94bc…d1e90xef43…6c7fBase$0.50100%virtuals320d ago0x161309…982c71
0x94bc…d1e90xef43…6c7fBase$0.05100%virtuals320d ago0xa59570…a7a583
0x94bc…d1e90xef43…6c7fBase$0.50100%virtuals320d ago0x584b9f…e6f4ff
0x94bc…d1e90xef43…6c7fBase$0.05100%virtuals320d ago0xe8735f…ef47ff
0x94bc…d1e90xef43…6c7fBase$0.50100%virtuals320d ago0x537919…18ffbd
0x94bc…d1e90xef43…6c7fBase$0.05100%virtuals320d ago0xf2e8bb…34f1bc
0x94bc…d1e90xef43…6c7fBase$0.50100%virtuals320d ago0x24c26c…a245ac
0x94bc…d1e90xef43…6c7fBase$0.05100%virtuals320d ago0x898c0b…b0bd44
0x94bc…d1e90xef43…6c7fBase$0.50100%virtuals320d ago0xa588ed…586a83
0x94bc…d1e90xef43…6c7fBase$0.05100%virtuals320d ago0xdd359c…c56a6a
0x94bc…d1e90xef43…6c7fBase$0.50100%virtuals320d ago0xbf575c…963846
0x94bc…d1e90xef43…6c7fBase$0.05100%virtuals320d ago0x613f64…c0bcf3
0x94bc…d1e90xef43…6c7fBase$0.50100%virtuals320d ago0x1e6b2a…c007a2
0x94bc…d1e90xef43…6c7fBase$0.05100%virtuals320d ago0xd045d3…bc1155
0x94bc…d1e90xef43…6c7fBase$0.50100%virtuals320d ago0x6180a6…19e137
0x94bc…d1e90xef43…6c7fBase$0.05100%virtuals320d ago0x7c518c…495b98
0x94bc…d1e90xef43…6c7fBase$0.50100%virtuals326d ago0x7216f9…bed1c9
0x94bc…d1e90xef43…6c7fBase$0.01100%virtuals326d ago0xbbe3b2…b07ba0

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

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

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: 0x94bc…d1e9

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