AgentReport

0xf785…89f4

0xf7858470cfd1528fc095c83f79e248585a4d89f4Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
264
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3067.84M Roundhouse has indexed across 1,401,919 wallets — less than 0.0001% of it.

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

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

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

  • 0x6482…b779 · last paid 276d ago
    $0.03
    264 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
0x6482…b779$0.03$0.00264276d 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 264 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams346d ago0x30c2a8…0b61fa
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams346d ago0xd15b9e…e5727a
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams346d ago0x40185e…2d3186
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams346d ago0xd39295…3a6285
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams346d ago0x0dcd0c…bf4c88
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams346d ago0xff6f31…6f3bf9
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams346d ago0xeb2720…bfa728
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams346d ago0x6fd0a5…5b6c1d
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams346d ago0x2a4d2f…63304a
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams346d ago0x3a68dd…6dafd9
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams347d ago0x0a5853…03f94a
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams347d ago0xac5546…41b67c
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams347d ago0x8cf9cd…716ff6
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams347d ago0x5836cd…fc619b
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams347d ago0x36ad6c…a27f6c
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams348d ago0xae469a…f17a0d
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams348d ago0x8c042b…358c3f
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams348d ago0x359377…d42c00
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams348d ago0x14b732…bff7cc
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams348d ago0xa863af…4dc259
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams348d ago0x481d25…92262e
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams348d ago0x39cf3c…6fd498
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams348d ago0x881296…92604c
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams348d ago0x44bd94…7e4959
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams348d ago0x2f97ec…58ddc6

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

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

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: 0xf785…89f4

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