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%daydreams325d ago0x3694ee…bea7ef
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams326d ago0xaaabd8…f39c74
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams326d ago0xc76270…df9588
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams326d ago0x46f4a0…880aae
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams326d ago0x01e2ae…003464
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams326d ago0x6b1c95…5e2e59
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams326d ago0x64c2e2…188fa7
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams326d ago0x6c3d89…faebee
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams326d ago0x45eb4a…197de7
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams326d ago0x1efebc…536470
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams326d ago0xb672f6…fd8116
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams327d ago0x127f0c…a52fc7
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams327d ago0x42d73f…7e93eb
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams327d ago0x070409…ce6bc6
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams327d ago0x17a008…7140a4
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams327d ago0xaae89e…21631b
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams327d ago0x80f8e5…e5de64
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams327d ago0xa934db…29d830
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams327d ago0x08d901…199b56
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams328d ago0x3d5269…f66cd7
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams328d ago0x96814b…c9eb87
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams335d ago0x4db989…149793
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams337d ago0xc2059c…190db5
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams337d ago0x0af731…d45028
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams337d ago0x44e2e1…bf12e5

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.