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 $3068.58M Roundhouse has indexed across 1,402,396 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%daydreams352d ago0x0cd679…62505d
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams353d ago0x4c2797…1194b2
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams353d ago0x954856…633be5
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams353d ago0x4f57ad…4c808a
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams353d ago0x047d46…0e5937
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams353d ago0x191974…624933
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams354d ago0x2a3dd3…460bbb
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams354d ago0xf0b951…ffe710
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams355d ago0x25e6de…85eddc
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams355d ago0x552ce9…3b3687
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams355d ago0x842157…6702ee
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams355d ago0x033e5c…43a6d4
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams355d ago0x66cdd6…631e7d
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams356d ago0x7654b1…b97314
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams356d ago0x59a6f7…460187
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams356d ago0x881b0a…039e68
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams356d ago0xae1dfe…a4d0fd
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams356d ago0x87d532…66a9c1
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams356d ago0x8ef729…a79bec
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams357d ago0x31b2b9…ca23e0
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams357d ago0x744227…ad1b15
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams357d ago0x9cabd8…b5f104
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams357d ago0xed4dd5…1ebda4
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams358d ago0xa855cb…0ed374
0xf785…89f40x6482…b779BaseBase$0.0001100%daydreams358d ago0x34cf63…19fa5f

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.