Pricing & billing
Use this page to understand how Routic charges, where to find the latest published model prices, and which part belongs to the docs site versus the console.
What this page is for
| Topic | Where to look |
|---|---|
| Latest published model prices | Model catalog |
| Charging rules and billing concepts | This page |
| Balance, recharge, invoices, and account actions | Console after sign-in |
How to read pricing on Routic
- Open the model catalog.
- Check the published model, code, context window, and listed input or output price.
- Use this page to understand how those prices are charged in practice.
Charging unit
Routic charges by the pricing unit shown for the model in the catalog.
Common cases include:
- Input tokens
- Output tokens
- Requests
- Pack or quota-based units
The exact unit follows the published model entry and the product definition linked to that entry.
Billing rule
The general calculation is:
Charge = measured usage × published unit price
In practice, this means:
- Token-priced models are charged by the counted input and output tokens.
- Request-priced products are charged by completed request count.
- Package-style products follow their listed quota or included usage rule.
Where usage and billing appear
- The docs explain the rule and pricing structure.
- The model catalog shows the current published price for each model.
- The console shows your account balance, usage records, recharge actions, and account-specific billing state.
Important notes
- Published prices may change over time. Use the current model catalog as the latest public reference.
- Final availability can vary by account, region, enabled products, or contract scope.
- If your team needs volume pricing, a broader model set, or rollout guidance, use Contact sales.