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%daydreams348d ago0x44e15a…6b11d7
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams349d ago0x1d2ffc…0139af
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams349d ago0xba9adf…d79af2
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams349d ago0x721e0e…4130e5
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams349d ago0xe18652…18805d
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams349d ago0x57bf4f…a92bed
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams349d ago0x66c0da…3fbebd
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams349d ago0x6f8aba…4ccd55
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams350d ago0x12232d…6c9b48
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams350d ago0xcd6cf6…a64a45
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams350d ago0x828764…d33def
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams350d ago0xa86f31…2e5118
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams350d ago0x4ae1c3…a766dc
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams350d ago0x2ff06d…3ecbd0
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams351d ago0x8fe55b…25c8a0
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams351d ago0x4fffa7…9f2841
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams351d ago0xd37f43…258162
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams352d ago0xd3d277…652e1e
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams352d ago0x8b0ca9…7cd394
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams352d ago0xd54b83…67c645
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams352d ago0x07012c…58b933
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams352d ago0xcc87fb…7bcc58
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams352d ago0x1bf5bf…a4dd68
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams352d ago0xc1840e…727256
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams352d ago0xc7f97a…68d15c

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.