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%daydreams348d ago0xb7762e…43ef6e
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams348d ago0x2bb0fd…e8dfeb
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams348d ago0x70b0de…ce8cb8
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams348d ago0xbd0490…13f70e
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams348d ago0x4e019c…1a1f67
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams348d ago0x0d03ca…5d1ee3
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams348d ago0x673d92…1942ff
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams349d ago0x504a99…90f798
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams349d ago0xb33f5e…e8bbdc
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams349d ago0xc4169e…56c55e
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams349d ago0x1919df…51f2e3
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams349d ago0x2500ae…add7ed
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams350d ago0x2e515d…b46480
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams350d ago0xe34112…0f2af8
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams350d ago0x7fe16d…e615c1
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams350d ago0xe39df9…2d3dfb
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams350d ago0x996038…c7f693
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams351d ago0x9926f5…92af65
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams351d ago0x2c6a0c…65210f
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams351d ago0x6b9938…b6d172
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams351d ago0x28291e…6990f3
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams351d ago0x7cff97…cfd81d
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams351d ago0x2852d6…fc1dcf
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams351d ago0xd1fc85…0cc731
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams352d ago0xa528ab…65434c

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.