Reasoning Tokens
What are reasoning tokens?
Reasoning tokens are tokens a language model generates while working through a problem before giving its final answer. They are usually billed as output tokens, even when they are not shown.
Updated November 2026 · 5 min read
Reasoning tokens are the intermediate steps a reasoning model produces as it thinks through a problem. Models designed for reasoning break a task into parts, consider approaches, check their work and revise before writing a final answer. Each of those steps is generated as tokens, just like the answer itself. Depending on the provider, this reasoning may be hidden, summarized or shown in full, but in most cases it is billed at the output token rate.
Reasoning improves results on complex tasks, such as multi-step analysis, mathematics, planning and difficult coding problems. It also changes the economics of a model call. A short question can produce thousands of reasoning tokens before a brief answer, so the visible length of a response says little about its cost. For IT financial management, reasoning tokens are an increasingly important and often overlooked part of AI spending, and controlling them is a key lever for managing the cost of more capable models.
Definition of Reasoning Tokens
Reasoning tokens are AI tokens produced by a model during an internal reasoning process that precedes or accompanies its final response. They are sometimes called thinking tokens.
The approach is part of a broader shift often described as test-time compute, in which models spend more computation while answering a question, rather than relying only on what was learned in training, in order to reach better answers.
How Reasoning Is Billed
Reasoning tokens are generated in the same way as visible output, one token at a time, so providers usually count them as output tokens and charge the output rate.
Some providers show the reasoning, some show a summary and some hide it entirely. In all cases, the usage data returned with the response normally reports how many reasoning tokens were used.
Because output tokens are priced higher than input, reasoning can quickly become the largest part of a request's cost, as described in input and output tokens.
Controlling Reasoning
Many reasoning models let developers set how much reasoning to allow, through settings such as a reasoning effort level or a maximum budget of thinking tokens.
Lower settings are faster and cheaper but may reduce quality on hard problems. Higher settings improve difficult answers but cost more and take longer.
Some models decide for themselves how much to reason based on the difficulty of the request, which makes costs less predictable from one call to the next. Two requests that look alike to a user can differ several times over in cost, depending on how hard the model judges each one to be.
Importance of Reasoning Tokens in IT Financial Management
Reasoning tokens can multiply the cost of a request several times over. An organization that switches an application to a reasoning model, or raises its reasoning setting, may see costs rise sharply without any change in the number of requests.
Because reasoning is often hidden, it can be missed by teams that estimate costs from the length of visible answers.
Tracking reasoning tokens as a separate measure is therefore essential for understanding and forecasting the cost of applications that use reasoning models. It is also the only way to see whether a change in reasoning settings, rather than a change in usage, explains a rise in spending.
When Reasoning Pays
For complex tasks, reasoning can make a model accurate enough to replace a more expensive alternative, such as several model calls or human review. In these cases the extra tokens are a good investment.
For simple tasks, such as classifying a message or extracting a field, extensive reasoning adds cost and delay without improving the result.
The right question is not whether reasoning is expensive but whether it lowers the cost per task at the required quality.
Predictability
Reasoning makes the cost of each request more variable, because the amount of thinking depends on the problem. Budgets and forecasts need to allow for this variability.
Setting reasoning budgets and monitoring the distribution of reasoning tokens per request, not just the average, helps identify outliers that drive costs.
For customer-facing products, unpredictable reasoning costs can affect margins, especially when customers can submit requests without limits.
How to Manage Reasoning Tokens
Managing reasoning tokens involves measuring them, matching reasoning levels to the difficulty of each task and testing whether reasoning improves results.
Reasoning should be treated as a setting to tune for each use, not a default to leave at its maximum.
Measuring Reasoning
Record reasoning tokens separately from visible output for each request, along with the model, the reasoning setting and the application.
Track reasoning tokens per request and per task, including high percentiles, and alert on sudden increases.
Include reasoning costs in showback reports so teams can see how their choice of model and settings affects spending. Teams that see the cost of their reasoning settings tend to tune them more carefully.
Matching Reasoning to Tasks
Use reasoning models or higher reasoning settings for complex tasks, and standard models or low settings for simple ones. An LLM router can send each request to the right model and setting.
Test each application at several reasoning levels, comparing quality and cost, and choose the lowest level that meets the quality bar.
Set maximum reasoning budgets to limit the cost of outliers, and review them as models and prices change. Newer models often reach the same quality with less reasoning, so settings chosen a year ago may no longer be the most economical.
Examples of Reasoning Tokens in IT Financial Management
The examples below show reasoning tokens affecting cost and the decisions taken in response.
Both use an illustrative output price of $15 per million tokens. The first finds hidden reasoning costs, and the second tunes reasoning to the task.
In each, measuring reasoning tokens separately revealed where the money was going.
Finding Hidden Costs
A company moves its customer email classifier to a reasoning model to improve accuracy. Visible answers remain a single label of about 10 tokens, but monthly costs rise from $2,000 to $20,000.
Usage data shows each request generating an average of 1,200 reasoning tokens. At 1 million emails a month, that adds 1.2 billion output tokens, or $18,000.
Testing shows accuracy improves by only one percentage point. The company returns the classifier to a standard model and uses the reasoning model only for the 5% of emails the classifier marks as uncertain.
Tuning Reasoning Effort
Another company uses a reasoning model to analyze contract risks. At the highest reasoning setting, each contract uses about 20,000 reasoning tokens, costing $0.30 in reasoning alone.
It tests three settings on 200 contracts reviewed by lawyers. The medium setting uses about 7,000 reasoning tokens, or $0.105, and matches the highest setting's accuracy on 98% of contracts.
The company adopts the medium setting and keeps the highest one for contracts above a certain value, reducing reasoning costs by about 60%. The lawyers' review time does not change, because the flagged risks are the same.
Conclusion
Reasoning tokens are the tokens a model generates while thinking through a problem before answering. They are usually billed as output tokens, may be hidden from the user, and can make up most of the cost of a request.
In IT financial management, reasoning tokens make AI costs higher and less predictable, but they can also lower the cost of completing hard tasks well. Measuring reasoning separately, matching reasoning levels to task difficulty, setting budgets and testing quality at each level help organizations pay for reasoning only where it adds value.
Related terms
AI Tokens
AI tokens are the small units of text, such as words or parts of words, that language models read and write, and the unit most AI services use to measure and charge for usage.
Input and Output Tokens
Input tokens are the tokens sent to a language model in a request, and output tokens are the tokens it generates in response. Most AI services price output tokens several times higher.
Cost per Task
Cost per task is the full cost of completing one unit of AI-assisted work, such as a resolved support request or a processed document, including every model call, tool and retry involved.
LLM Router
An LLM router is a system that decides which language model should handle each request, sending simple requests to cheaper, faster models and complex ones to more capable models, to balance cost and quality.