If you've ever looked at an AI model pricing page and felt confused, you're not alone. "Per million input tokens" and "per million output tokens" sound like a foreign language if you're new to AI development. But understanding token pricing is essential—it's the single biggest factor in how much your AI application will cost to run.
In this article, we'll break down AI token pricing in plain English, explain why it matters, and show you how to estimate costs for your own projects.
What Is a Token?
A token is the basic unit of data that an AI language model processes. Think of tokens as the "words" the AI reads and writes—but they're not exactly the same as words.
Here's how it can break down:
- A common English word like "apple" might be 1 token
- A less common word like "extraordinary" might be 3-4 tokens (extra-ordin-ary)
- A single character like "!" might be 1 token
- A space between words is often part of the preceding token
As a rough rule of thumb, 1 token ≈ 4 characters in English text, or about ¾ of a word. So 100 tokens is approximately 75 words.
Different models use different tokenizers, so the exact token count for the same text can vary between providers. OpenAI, Anthropic, Google, and DeepSeek all have slightly different tokenization schemes.
Input Tokens vs Output Tokens: What's the Difference?
This is the most important distinction in AI pricing:
Input tokens (also called "prompt tokens") are the tokens you send to the model. This includes:
- Your system prompt or instructions
- The user's message
- Any context, documents, or examples you provide
- The conversation history in a chat application
Output tokens (also called "completion tokens") are the tokens the model generates in response. This includes:
- The model's answer
- Any code it writes
- Any reasoning or "thinking" tokens it produces
Output tokens are almost always more expensive than input tokens—often 3-5x more expensive. This makes sense when you think about it: generating text requires the model to do computation for each token, while processing input is relatively cheaper.
How Token Pricing Works in Practice
Let's look at a concrete example. Suppose you're building a customer support chatbot using a model that costs:
- $1.00 per million input tokens
- $5.00 per million output tokens
A typical customer support conversation might involve:
| Component | Token Count |
|---|---|
| System prompt | 200 tokens |
| Customer's question | 50 tokens |
| Conversation history (5 turns) | 1,000 tokens |
| Retrieved knowledge base context | 2,000 tokens |
| Total input tokens | 3,250 tokens |
| Model's response | 300 tokens |
| Total output tokens | 300 tokens |
The cost for this single conversation would be:
- Input cost: 3,250 / 1,000,000 × $1.00 = $0.00325
- Output cost: 300 / 1,000,000 × $5.00 = $0.0015
- Total cost: $0.00475 per conversation
That seems tiny—less than half a cent. But if you're handling 10,000 customer conversations per day, that's $47.50 per day, or about $1,425 per month. Scale to 100,000 conversations and you're looking at $14,250 per month.
This is why understanding token pricing matters. Small per-conversation costs add up fast at scale.
Why the Cheapest Model Isn't Always the Cheapest
Here's a counterintuitive truth: the model with the lowest token price isn't always the cheapest option. This is because of token efficiency.
More capable models can often complete the same task using fewer tokens. A smarter model might:
- Generate shorter, more direct answers instead of rambling
- Get the answer right on the first try instead of requiring multiple attempts
- Follow complex instructions without needing examples that would add to input tokens
- Use "effort" settings efficiently—a model at medium effort might match a cheaper model at max effort
For example, Artificial Analysis found that Anthropic's Claude Opus 5 at "medium" effort delivered similar performance to Moonshot's Kimi K3 at "max" effort. Even though Opus 5 has higher per-token prices, it might complete tasks using fewer total tokens, making the effective cost per task similar or even lower.
The "Effort" Setting Explained
Many modern AI models offer an "effort" or "thinking" setting that controls how much computation the model uses:
- Low effort: The model thinks less, generates fewer reasoning tokens, and is cheaper per task—but may make more errors
- Medium effort: A balanced setting that works well for most tasks
- High/Max effort: The model thinks more deeply, generates more reasoning tokens, and is more expensive—but more accurate on complex tasks
The effort setting affects both quality and cost. A model at high effort might generate 2,000 reasoning tokens before producing its final answer, while at low effort it might produce only 200 reasoning tokens.
This means the effective cost of using a model can vary by 10x or more depending on how you configure it.
Current AI Model Pricing Landscape (August 2026)
The AI pricing landscape has shifted dramatically in recent months. Here's a snapshot of current pricing for popular models:
| Model | Provider | Input Price (per M tokens) | Output Price (per M tokens) |
|---|---|---|---|
| GPT-5.6 Sol | OpenAI | $0.90 | $5.40 |
| Claude Opus 5 | Anthropic | $1.50 | $7.50 |
| GLM 5.2 | Zhipu AI | $0.03 | $0.09 |
| DeepSeek V4 Pro | DeepSeek | $0.11 | $0.33 |
| Qwen 3.8 Max | Alibaba | $1.09 | $3.26 |
Notice the massive range. GLM 5.2 costs about $0.03 per million input tokens, while Claude Opus 5 costs $1.50—50x more. But that doesn't mean GLM 5.2 is 50x cheaper to use in practice; it depends on the task, the effort setting, and how many tokens each model needs to complete it.
You can explore current pricing for hundreds of models on Qubax AI's model catalog.
How to Estimate Your AI Costs
Here's a practical framework for estimating your AI application costs:
Step 1: Determine your token usage per request
Run 100 representative requests through your application and measure:
- Average input tokens per request
- Average output tokens per request
Step 2: Calculate per-request cost
per_request_cost = (avg_input_tokens × input_price / 1M) + (avg_output_tokens × output_price / 1M)Step 3: Project monthly volume
monthly_cost = per_request_cost × daily_requests × 30Step 4: Add a 20% buffer
AI usage tends to grow over time as users discover features. Add a 20% buffer to your estimates.
Step 5: Compare models
Run the same calculation for 3-5 different models. You might be surprised which one offers the best value for your specific workload.
Common Pricing Pitfalls to Avoid
- Ignoring output token costs: Many developers focus on input token prices and forget that output tokens are typically 3-5x more expensive. If your application generates long responses, output costs will dominate.
- Not accounting for context: If you're building a chatbot, your conversation history grows with every turn. A 10-turn conversation has far more input tokens than a 1-turn conversation.
- Forgetting about reasoning tokens: Models that "think" before answering (like those with extended thinking capabilities) generate reasoning tokens that you pay for, even though they're not shown to the user.
- Not testing effort settings: Running a model at max effort when medium would suffice can multiply your costs unnecessarily.
- Not monitoring costs in production: Token costs can spike unexpectedly if users start sending longer prompts or if a bug causes infinite loops. Implement cost monitoring and alerts.
Tools to Help You Manage Token Costs
- Model gateways: Platforms like Qubax AI provide built-in cost tracking, budget limits, and automatic routing to cheaper models when possible.
- Tokenizers: Most providers offer tokenizers that let you count tokens before sending requests, so you can estimate costs upfront.
- Cost monitoring APIs: Track your spending across providers with unified dashboards.
- Caching: Many gateways offer prompt caching, which can dramatically reduce input token costs for repeated queries.
The Future of AI Pricing
The current price war suggests that AI token prices will continue to fall, especially for mid-tier models. However, frontier models—the most capable offerings from each lab—are likely to maintain premium pricing as long as they offer capabilities that cheaper models can't match.
For developers, this means:
- Building with multiple model support is more important than ever
- Cost optimization should be an ongoing process, not a one-time decision
- The gap between "good enough" and "best" models is narrowing, making cheaper models viable for more use cases
FAQ
What is a token in AI?
A token is the basic unit of text that an AI model processes. Roughly, 1 token equals 4 characters or ¾ of a word in English. Models charge based on the number of tokens they read (input) and generate (output).
Why are output tokens more expensive than input tokens?
Output tokens require the model to perform computation to generate each token, while input tokens only need to be processed (read). The computational cost of generating text is higher than processing it, which is reflected in the pricing.
How much does it cost to run an AI chatbot?
It depends on the model, your usage patterns, and volume. A customer support chatbot handling 10,000 conversations per day might cost anywhere from $15 to $500 per day, depending on whether you use a budget model like GLM 5.2 ($0.03/M input) or a premium model like Claude Opus 5 ($1.50/M input).
What is the effort setting in AI models?
The effort setting controls how much computational power a model uses to answer a question. Higher effort means more reasoning tokens and better accuracy, but higher costs. Lower effort is cheaper but may produce lower-quality answers.
How can I reduce my AI API costs?
Use a model gateway like Qubax AI to route simple queries to cheaper models, implement prompt caching, optimize your prompts to use fewer tokens, test different effort settings, and monitor your costs continuously.
Are Chinese AI models really cheaper than US models?
Yes, Chinese models like DeepSeek V4 Pro and GLM 5.2 are significantly cheaper per token than US models like GPT-5.6 Sol and Claude Opus 5. However, the real cost depends on how many tokens each model needs to complete your specific task.