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%daydreams337d ago0xa57061…c81364
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams337d ago0xbe9406…168c82
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams337d ago0x18674d…8f49fc
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams337d ago0x12ae05…5a3071
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams338d ago0xf3ad96…91573e
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams338d ago0xeeb0b8…dcc3db
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams338d ago0x80d565…abcf7c
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams339d ago0x951780…e49b7e
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams339d ago0x66d55e…7c9c12
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams339d ago0xc3188d…535ab8
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams339d ago0x795c15…7ca98b
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams339d ago0x3b277e…fc813b
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams339d ago0xcb428c…bb0472
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams339d ago0x89ace8…7979b2
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams340d ago0x884dae…7bc845
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams340d ago0xd02574…5ee5ee
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams340d ago0x22539c…c81e41
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams340d ago0x813ed6…cb10a2
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams340d ago0x0b3ca0…9a7b47
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams340d ago0x364f4c…061f06
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams340d ago0xa42f92…034359
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams340d ago0x2dc81f…e19e0d
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams340d ago0x2a30b1…633c3c
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams340d ago0x1e4f97…1d3331
0x0f32…cd890x6482…b779BaseBase$0.0001100%daydreams340d ago0x171973…c35d7c

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.