AgentReport

0xfc64…d381

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

Paid $0.03 of the $3070.29M Roundhouse has indexed across 1,403,290 wallets — less than 0.0001% of it.

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

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.032541

$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 277d ago
    $0.03
    254 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.00254277d 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 254 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xfc64…d3810x6482…b779BaseBase$0.0001100%daydreams347d ago0x3fa717…906532
0xfc64…d3810x6482…b779BaseBase$0.0001100%daydreams347d ago0xe79906…12568c
0xfc64…d3810x6482…b779BaseBase$0.0001100%daydreams347d ago0x1c37a7…5e27c5
0xfc64…d3810x6482…b779BaseBase$0.0001100%daydreams347d ago0xa4d8ba…f22a01
0xfc64…d3810x6482…b779BaseBase$0.0001100%daydreams347d ago0x3310fe…b1195d
0xfc64…d3810x6482…b779BaseBase$0.0001100%daydreams347d ago0xdd0bf0…bb2025
0xfc64…d3810x6482…b779BaseBase$0.0001100%daydreams347d ago0x9a18ad…dd45f8
0xfc64…d3810x6482…b779BaseBase$0.0001100%daydreams348d ago0x86d7a8…2a26ed
0xfc64…d3810x6482…b779BaseBase$0.0001100%daydreams348d ago0x1336ca…ba5c32
0xfc64…d3810x6482…b779BaseBase$0.0001100%daydreams348d ago0xeaa200…9c2f3c
0xfc64…d3810x6482…b779BaseBase$0.0001100%daydreams348d ago0x4c3413…40a699
0xfc64…d3810x6482…b779BaseBase$0.0001100%daydreams348d ago0x53af9c…c5bd55
0xfc64…d3810x6482…b779BaseBase$0.0001100%daydreams348d ago0x34f7b4…ac9060
0xfc64…d3810x6482…b779BaseBase$0.0001100%daydreams348d ago0x61a44c…8e63c7
0xfc64…d3810x6482…b779BaseBase$0.0001100%daydreams348d ago0x37c79d…e7bd65
0xfc64…d3810x6482…b779BaseBase$0.0001100%daydreams348d ago0x478898…953c17
0xfc64…d3810x6482…b779BaseBase$0.0001100%daydreams349d ago0x0d91b3…069365
0xfc64…d3810x6482…b779BaseBase$0.0001100%daydreams349d ago0xffdd7c…255ea0
0xfc64…d3810x6482…b779BaseBase$0.0001100%daydreams349d ago0x668ad6…3574d6
0xfc64…d3810x6482…b779BaseBase$0.0001100%daydreams349d ago0x7a0ec4…d30cbb
0xfc64…d3810x6482…b779BaseBase$0.0001100%daydreams349d ago0x5bbd56…0c4e32
0xfc64…d3810x6482…b779BaseBase$0.0001100%daydreams349d ago0xab3048…c3b4b2
0xfc64…d3810x6482…b779BaseBase$0.0001100%daydreams350d ago0xa4fc94…0cc79e
0xfc64…d3810x6482…b779BaseBase$0.0001100%daydreams350d ago0x5e0763…5e49bd
0xfc64…d3810x6482…b779BaseBase$0.0001100%daydreams350d ago0xf90441…4595eb

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

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

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: 0xfc64…d381

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