Usage & billing

Charges depend on the model, group and rules applicable to each request. The public catalog does not replace account-specific terms.

Common billing components

• Input: Prompts, conversation history and other content counted by the model's billing rules.
• Output: Generated content; some models also bill reasoning usage.
• Cache: Reads and writes are priced separately and should not be counted twice as input.
• Per request or image: Image tasks and other operations may use different billing units.

A simple estimate

Estimated cost = input tokens / 1,000,000 * input price
               + output tokens / 1,000,000 * output price

This formula only applies to basic text requests without caching, tiers or additional conditions. 1M tokens does not mean one million Chinese characters.

Checking charges

Find a request by time, key and model in usage history. Check tokens, cost and available cache details. A timeout, cancellation or incomplete response does not necessarily mean no usage occurred.

Final prices and balance units are shown in the console. Models and retail pricing are still being configured.