Pricing

Pricing follows the provider mode.

Arxivo separates managed cloud credits, BYOK platform usage, and local desktop execution. The live credit ledger uses 100 managed credits per estimated USD for Arxivo Managed runs; BYOK and Local runs are metered separately.

Create accountView your balance

Cloud model credits

Arxivo Managed

Consumes managed credits when Arxivo runs a cloud model for you.
Runs reserve credits before execution, then consume or refund based on outcome.
BYOK provider tokens and local inference are not billed as managed credits.

Your provider account

BYOK

Provider token cost is paid to your provider; Arxivo records usage for audit.
Ledger entries are meter-only — no managed credit reserve or consume.
Arxivo does not double-charge for provider tokens you already pay for.

Desktop / local worker

Local

Local inference does not spend managed model credits.
Runs are recorded with zero managed credit cost while execution stays local.
Compute runs on your machine; cloud fallback requires a new estimate and confirmation.

Billing policy

Live ledger rules

These rules match the backend credit ledger shipped in TAN-4230. Subscription tiers, Stripe checkout, and public list prices remain separate protected work.

Estimate first

Agent work shows provider mode, model route, and expected managed credits before chargeable cloud execution.

Reserve → settle

Managed runs reserve credits at start, consume on useful output, and refund reserved credits on failed or canceled runs.

Separate ledgers

Managed credits (100 credits per estimated USD), BYOK meter-only events, and Local zero-credit events stay distinct.

Transparency

Usage history records provider, model, task type, tokens, and whether Arxivo credits were charged.

Provider disclosure stays visible.

Managed routes disclose cloud processing and credit estimates. BYOK routes disclose provider billing. Local routes disclose desktop/local worker requirements.

Review provider status