Check estimated credits while composing
Understand pre-send estimates, Auto/Premium messages and options for managing high usage.
Updated: September 2026
Screens show real UI components with fictional training names, emails and values. No accounts were changed and no emails were sent. Select an image to open it at full size.
1. Type a request and check the estimate
Choose a model directly and enter your request. Estimated credits: number~ appears near the composer. Input, model and attachment changes may trigger recalculation. Wait for the current estimate before reviewing it.
The 3,200~ figure is fictional training data, not a quote for the displayed prompt.
2. Understand the approximation
The estimate is not a final charge, a maximum or your remaining balance. Reasoning depth, output length, search, tools and attachment handling may affect actual usage. Hover over or select the estimate to read its explanation.
| Display | Meaning | Action |
|---|---|---|
| Estimated credits: number~ | Reference value for estimable conditions | Review your budget before sending |
| Calculating | Updating for current input | Wait and check again |
| Difficult to estimate | No usable estimate is available | This does not mean free; check input, model and status |
| After model selection | Automatic routing has not selected the execution model | See Auto/Premium below |
3. Auto and Premium may not show a number yet
Routing selects a model based on the request, so the composer cannot establish the amount beforehand. This message does not mean free or fixed-price use. For pre-send comparisons, select a model directly. After the task, check credit usage.
4. Options when estimated usage is high
| Option | Effect and consideration |
|---|---|
| Exclude earlier conversation context | Keeps the history but reduces context for subsequent requests. Restate necessary requirements. |
| Summarize the conversation | Shortens accumulated context. The summarization itself also consumes credits. |
| Switch models | Compare a lower-cost alternative when available. Capabilities and quality vary. |
| Reduce input scope | Include only relevant documents and specify the required output length. |
Controls depend on conversation state and availability. Reducing conversation context does not eliminate image/video base generation costs; inspect generation settings too.
5. Workshop exercise
With the same model selected, type a short request and a longer one and observe the estimates without sending. Switch to Auto and compare its after-model-selection message. If you send a request, compare actual usage afterward and discuss the difference.
Remember: Use the estimate before sending and actual usage after completion.
Was this answer helpful?

