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%daydreams340d ago0xf74bc4…f776b0
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams341d ago0x03f428…b10be2
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams341d ago0x16f256…4f6247
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams341d ago0xbf2715…da52b4
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams341d ago0x46d6c8…41fb34
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams341d ago0x9fa38b…3f04cc
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams341d ago0x3ce30c…63605b
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams341d ago0x52a2a8…1cfd23
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams341d ago0xe309ae…475109
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams341d ago0xc44925…593b2a
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams341d ago0x0bd95c…83d204
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams341d ago0x4b3f7c…864e2e
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams342d ago0xb7c91f…7ea2d2
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams342d ago0xb24b12…94b429
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams342d ago0x66d242…7b90ec
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams342d ago0xfeb2b8…832813
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams342d ago0x04fc02…5a1571
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams342d ago0x532b24…3db665
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams342d ago0xed0027…91304c
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams342d ago0xd5f671…59e478
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams342d ago0xadc60b…68e41c
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams342d ago0x61d6e4…9c75ca
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams342d ago0x40a726…e890bf
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams343d ago0xccf53d…d3e427
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams343d ago0x42e40b…4315f6

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.