AgentReport

0x0f32…cd89

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

Paid $0.03 of the $3066.54M Roundhouse has indexed across 1,400,510 wallets — less than 0.0001% of it.

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

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

$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
    263 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.00263276d 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 263 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams345d ago0x848504…5a87c3
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams345d ago0x704dad…090383
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams345d ago0xf9c229…647e73
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams345d ago0x7d5ed0…00c263
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams345d ago0xb23d12…ae07f6
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams345d ago0x2d84d4…264b39
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams345d ago0x8689e5…59d5d2
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams346d ago0xae551d…32bbd7
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams346d ago0x2a6e74…24812c
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams346d ago0xc97884…8d6d25
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams346d ago0x1b29c7…187259
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams346d ago0x46d77c…ca9fbf
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams346d ago0x3254a9…a34403
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams346d ago0x2b5fc7…f06237
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams346d ago0x98bb1b…86db45
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams346d ago0x055892…10b5a5
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams346d ago0xbbc8f9…42e62a
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams347d ago0xc3c9ea…4a1f44
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams347d ago0x025d44…b34de2
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams347d ago0x02431f…0b3552
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams347d ago0x5926fe…95e89d
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams347d ago0x98a82d…77ce50
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams348d ago0x43ee49…b166df
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams348d ago0x0cd61c…fe263c
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams348d ago0xdfa993…6d91ae

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

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

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: 0x0f32…cd89

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