Router One subscription plans are live. You can now use Pro, Max, or Ultra for predictable monthly access, while wallet pay-per-token billing remains available for flexible usage and calls outside plan coverage.
This update makes the pricing story consistent across the homepage, FAQ, pricing page, docs, and machine-readable LLM reference files. Router One now supports two public billing paths: prepaid wallet credits and monthly subscription plans.
What is live today
- Pro, Max, and Ultra subscriptions. Monthly plans are available on the pricing page for users who prefer predictable access.
- Prepaid wallet billing. Top up balance first, then spend by token usage across supported models outside plan coverage.
- Model-level rates. The model marketplace remains the source of truth for per-model input, output, and capability details.
- China-friendly payment rails. Wallet top-ups support WeChat Pay, Alipay, Stripe, and USDT/USDC where available.
- Request traces. Each model call can be traced for routing, provider, model, cost, latency, and fallback behavior.
- Budget controls. Give each coding tool or project a separate API key with its own maxSpend cap, so one runaway workload cannot consume the whole wallet.
See the pricing methodology for how wallet charging, subscription economics, checkout fees, and rate changes are explained.
How wallet billing and subscriptions coexist
Wallet billing is still the most flexible way to pay for irregular API usage. Subscriptions add a predictable monthly option on top of that wallet model.
- Choose a subscription when you want predictable monthly access.
- Keep wallet balance for pay-per-token usage outside plan coverage.
- Use wallet balance when you prefer a one-time plan period instead of card auto-renewal.
- Review traces after high-cost sessions to see which model, route, and billing path applied.
Plan terms, coverage, limits, cancellation, and renewal behavior are governed by the public pricing page and the applicable plan terms shown at checkout.
How to budget coding agents
For coding agents like Claude Code, Codex, and Cline, start with the expected intensity of usage:
- Light or bursty usage: keep wallet pay-per-token billing.
- Steady daily usage: compare Pro, Max, and Ultra on the pricing page.
- Team or production usage: set API key budgets and review trace data before raising limits.
- Model exploration: use Model Marketplace to compare pricing, context, and capabilities.
The main rule is simple: subscriptions help stabilize recurring usage, while wallet balance remains the fallback for flexible workloads and model calls outside plan coverage.
Where to check current terms
Use these pages as the canonical references:
- Pricing for current subscription plans.
- Pricing methodology for wallet billing, checkout fees, and rate-change rules.
- Model Marketplace for model-level pricing and capabilities.
- Refund Policy for unused credits, consumed credits, bonus credits, and subscription cancellation rules.