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,255 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%daydreams323d ago0x798c39…2226f6
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams323d ago0xa91f6c…b6e6e7
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams323d ago0x854ac4…fab64f
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams324d ago0xda0844…3ae8c3
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams324d ago0x9f68a3…3ba275
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams324d ago0xe3c909…2a6729
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams324d ago0x2a25a6…b7f249
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams324d ago0xf5bc13…ebff26
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams324d ago0xf3e1e3…28b5dc
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams324d ago0x53fd09…0a00f7
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams324d ago0xe82f0b…fae73c
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams324d ago0x7fd13a…17dc2b
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams324d ago0xecaf83…1bc08d
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams324d ago0x892a18…5b3702
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams324d ago0x200b2d…482166
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams324d ago0x2f908c…28365b
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams325d ago0x7828e3…13f251
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams325d ago0xd37219…736bb9
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams325d ago0xeb9a46…ba395b
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams325d ago0x591b13…a9db75
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams325d ago0xc05258…cfcac4
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams325d ago0x92577a…0b32f6
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams325d ago0x2b9144…5c1a29
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams325d ago0xe81489…600366
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams325d ago0xc50190…d2eef4

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.