Costs
Model prices
Section titled “Model prices”The Input and Output fields use €/1 million tokens for the selected provider/model. Input represents the sent context; output represents the generated response. If you change the fields and save, you create custom prices for that provider/model pair.
The runtime looks up custom prices, per-provider configuration, the OpenRouter catalog, known tables and fallback values. The catalog may not match the tariff of your direct account. Confirm prices at the provider and correct them when necessary.
estimated cost = input tokens × input price / 1 000 000 + output tokens × output price / 1 000 000Summary and currency
Section titled “Summary and currency”- Session: visual accumulation of usage in the current panel.
- Today: records since the start of the local day.
- Week: records since Monday at midnight local time.
- Month: records since the first day of the local month.
- Models used this month: breakdown of costs and tokens by provider/model.
- Tokens used in the current session: input and output available to follow usage.
The display currency accepts EUR, USD, JPY, GBP, CNY and CHF. It applies only to the session; today/week/month totals stay in euros. Conversion uses public rates, cache or approximate offline values. It does not fix the catalog’s 1:1 price simplification.
Limits and retention
Section titled “Limits and retention”The last 2000 cost records stay on the device, without page text or conversations. Aggregates only cover records still retained; they are not a complete accounting history.
The limit in Preferences prevents starting another turn when the local accumulated value has already reached it. It does not prevent a turn from exceeding the value nor controls provider billing. Also set limits in your API account.
Ollama uses a zero price by default, which does not include electricity or hardware. Custom can also report zero when no known tariff exists: zero does not prove the endpoint is free.
