AgentReport

0xfa47…f464

0xfa477912ba43fca9b00b4a01cca68ce93709f464Explorer
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 $3070.29M Roundhouse has indexed across 1,403,290 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 277d 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.00264277d 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
0xfa47…f4640x6482…b779BaseBase$0.0001100%daydreams349d ago0xdd5d0a…cfe919
0xfa47…f4640x6482…b779BaseBase$0.0001100%daydreams349d ago0x1d607c…afa30b
0xfa47…f4640x6482…b779BaseBase$0.0001100%daydreams349d ago0xb5d6b9…cdfd04
0xfa47…f4640x6482…b779BaseBase$0.0001100%daydreams349d ago0xc078cb…eed351
0xfa47…f4640x6482…b779BaseBase$0.0001100%daydreams349d ago0x32b267…001a0f
0xfa47…f4640x6482…b779BaseBase$0.0001100%daydreams349d ago0x382056…72b7bf
0xfa47…f4640x6482…b779BaseBase$0.0001100%daydreams349d ago0xfc01db…7d4311
0xfa47…f4640x6482…b779BaseBase$0.0001100%daydreams349d ago0x1d904d…f17705
0xfa47…f4640x6482…b779BaseBase$0.0001100%daydreams350d ago0xcfbe3b…cfb40b
0xfa47…f4640x6482…b779BaseBase$0.0001100%daydreams350d ago0x7a8232…dc8dcc
0xfa47…f4640x6482…b779BaseBase$0.0001100%daydreams350d ago0x69ba95…4dedc4
0xfa47…f4640x6482…b779BaseBase$0.0001100%daydreams350d ago0xe0b865…409dd9
0xfa47…f4640x6482…b779BaseBase$0.0001100%daydreams351d ago0xb281c0…221412
0xfa47…f4640x6482…b779BaseBase$0.0001100%daydreams351d ago0xac33c7…a493c7
0xfa47…f4640x6482…b779BaseBase$0.0001100%daydreams351d ago0x087b0e…7e6535
0xfa47…f4640x6482…b779BaseBase$0.0001100%daydreams351d ago0x64e694…9b7e9c
0xfa47…f4640x6482…b779BaseBase$0.0001100%daydreams351d ago0xeebf8c…74e26c
0xfa47…f4640x6482…b779BaseBase$0.0001100%daydreams351d ago0xc81183…7caca6
0xfa47…f4640x6482…b779BaseBase$0.0001100%daydreams351d ago0xb72fa3…0dd778
0xfa47…f4640x6482…b779BaseBase$0.0001100%daydreams351d ago0x03e30d…79d582
0xfa47…f4640x6482…b779BaseBase$0.0001100%daydreams351d ago0x8b6c4c…609bd7
0xfa47…f4640x6482…b779BaseBase$0.0001100%daydreams352d ago0x9ecb32…024d93
0xfa47…f4640x6482…b779BaseBase$0.0001100%daydreams352d ago0x304c48…14b955
0xfa47…f4640x6482…b779BaseBase$0.0001100%daydreams352d ago0x352c59…6f066a
0xfa47…f4640x6482…b779BaseBase$0.0001100%daydreams352d ago0x34460d…5f57e3

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

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

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: 0xfa47…f464

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