Short classifier
2,000 input tokens and 150 output tokens per request
Usually input-heavy; constrain the output format and use a smaller model if quality permits.
AI economics explainer · Checked August 13, 2026
How AI model pricing works when the model is only part of the bill
Learn what input and output tokens mean, why long context changes the calculation, where caching and batch processing fit, and how to estimate the cost of a completed workflow instead of trusting a headline API rate.
Michael Okeje
AI pricing and workflow economics research · Last updated August 13, 2026
The useful distinction: model call versus completed task
AI model pricing looks simple until you build something that people actually use. A provider displays a number per million input tokens and another per million output tokens. You multiply those numbers by an estimate, present a monthly total, and discover later that conversation history, retrieved documents, tool calls, retries, long answers, image inputs, and human review were not in the model. The arithmetic was correct. The model of the work was incomplete.
I think about AI cost in two stages. First, calculate the provider bill for a model call. Second, calculate the cost of a completed business task. The first number helps you choose a model and set a budget. The second tells you whether the product or workflow makes economic sense. A cheap model that produces unusable drafts can cost more than a premium model that is accepted with little repair. A low token price also does not protect an agent that loops through ten tool calls before reaching a result.
This guide explains the pricing mechanics without pretending that one table can remain correct forever. Provider prices, model names, cache rules, quotas, and discounts change. For current numbers, use the official pricing pages linked at the end and our maintained pricing reference at /llm-pricing-2026. The durable skill is knowing what to count, what to ask a vendor, and how to turn a sample trace into a defensible cost estimate.
Five layers appear on a real AI bill
The provider's token table is the foundation, not the entire budget. Map the layers before comparing vendors.
| Layer | What it includes | What to inspect |
|---|---|---|
| Input | The text, images, files, conversation history, system instructions, retrieved passages, and tool results sent into a model call. | Count tokens or provider-specific units. Long repeated context can dominate an application bill. |
| Output | The answer, structured data, code, reasoning-related output, or generated media returned by the model. | Set output limits and measure actual completion length. A generous maximum is not the same as actual use. |
| Modifiers | Caching, batch processing, priority tiers, data residency, long-context pricing, and model-specific discounts or premiums. | Read the provider's current pricing page and calculate each modifier separately instead of applying one blanket rate. |
| Tools | Search, retrieval, code execution, computer use, function calls, transcription, image generation, or external APIs used around the model. | A tool may have its own per-call, per-result, per-minute, or infrastructure charge. |
| Operations | Retries, queues, logs, storage, moderation, evaluation, monitoring, support, and human review. | These costs determine whether a workflow is affordable in production even when tokens are cheap. |
Providers expose different accounting fields and may change the names of models or features. Preserve the raw usage response in your own logs, then map it into a stable internal schema. That lets you compare a workflow over time even when the provider changes its dashboard.
The basic calculation
For a text call, start with a deliberately boring equation:
call cost = (input units × input rate) + (output units × output rate) + eligible modifiers
Rates are normally displayed per million tokens, so convert the usage before multiplying. If a request contains 20,000 input tokens, divide by 1,000,000 and multiply by the provider's current input rate. Do the same for output. Keep input and output separate because the rates can differ substantially and because workflow design changes their ratio.
Then move from calls to tasks:
task cost = model calls + tools + retries + infrastructure + review + support
This second equation is where a business case becomes honest. The numbers do not need to be perfect on day one. They do need to name the costs that could change the decision.
How the workload changes the answer
The same model can be inexpensive for one job and a poor fit for another. Estimate the shape of the workload, not only its average prompt.
Document reviewer
40,000 input tokens and 1,000 output tokens
Input context dominates; clean retrieval, chunking, and caching may matter more than shaving output.
Customer assistant
Conversation history plus retrieved policy on every turn
Measure repeated context, cache hits, tool calls, escalation, and long conversations rather than one isolated call.
Batch enrichment
Thousands of independent records with no immediate response requirement
An asynchronous batch tier may lower cost, but include validation, retry, queue, and delivery time.
Agent task
Several model turns plus search, code, database, and human approval
Count the whole trace. One successful task can contain many billable calls and failed attempts.
Start by defining the billable unit. Is it one chat turn, one answered question, one document processed, one customer case resolved, one report delivered, one code change merged, or one agent task completed? “Cost per request” is often too technical for a business decision. A user may trigger several requests to receive one answer, and a single request may be part of a longer workflow that still needs review. Name the outcome before choosing the denominator.
Then capture a real trace. Record the model identifier, provider, input token count, output token count, cache read and write counts where available, tool calls, retrieved context, retries, latency, errors, and human edits. Sample across easy, ordinary, and difficult cases. If you only measure a short demo prompt, you are estimating the best-looking path. Production cost is shaped by the tail: long conversations, repeated failures, oversized documents, and requests that need escalation.
Do not mix consumer plan economics with API economics. A monthly chat subscription may be excellent value for a person using a tool interactively, while an application calling an API needs usage billing, rate limits, data controls, logging, and support. The reverse can also be true: a small internal workflow may be cheaper with a team product than with a custom API integration once engineering and maintenance are counted. Compare the product that delivers the outcome, not only the model name.
For a first estimate, create three scenarios: expected, high-volume, and stress. Expected uses the median case and planned adoption. High-volume uses the forecasted busy period. Stress includes long context, retries, tool failure, and a higher-than-planned adoption rate. Set a spend alert and a hard operational limit where the provider supports one. Cost control is part of design, not something to add after a surprise invoice.
Six estimates that make AI budgets look better than they are
Using words instead of tokens
Words are a rough proxy and vary by language, punctuation, code, and formatting. Measure representative requests with the provider's tokenizer or actual usage fields.
Pricing only the happy path
Include retries, refusals, tool failures, long context, moderation, and escalation. A workflow is paid for when it reaches a useful result, not when the first call returns anything.
Assuming a maximum is an average
max_output_tokens, context limits, and rate limits are ceilings. Use observed distributions and cap output deliberately.
Ignoring repeated context
Conversation history, system instructions, retrieved policy, and tool results can be sent again on every turn. Inspect what the application actually transmits.
Treating caching as guaranteed
Caching has eligibility, expiry, minimum-size, placement, and provider-specific rules. Track hits and misses; do not put confidential material in a cache without understanding the terms.
Comparing model prices without quality
A lower price per token can be a false economy if it causes more retries, review, customer corrections, or failed tasks. Pair cost with an evaluation score.
A practical cost-estimation worksheet
- Name the completed outcome and the eligible volume per day, week, and month.
- Collect at least 30 representative traces, including difficult and failed examples.
- Record input, output, cache, tool, retry, latency, and escalation fields.
- Calculate median, high-percentile, and stress-case cost per completed outcome.
- Add software, storage, monitoring, engineering, support, and human review.
- Set a quality threshold and compare cost only among workflows that meet it.
- Set a spend alert, a rate-limit plan, and an owner who reviews variance.
- Recalculate when the model, prompt, retrieval corpus, tool, traffic, or review policy changes.
For current provider tables, compare the LLM pricing reference, then open the official provider pages below before making a purchase or publishing a cost claim. Our AI ROI guide explains how to separate cash savings, capacity, quality, risk, and strategic value.
Frequently asked questions
What are tokens in AI pricing?
Tokens are the chunks of text or other content that a model processes. Providers usually charge separately for input tokens sent to the model and output tokens generated by it. A token is not exactly a word: punctuation, spaces, numbers, code, and language affect tokenization. Your billing dashboard and provider tokenizer are the reliable way to measure a real request.
Why are output tokens usually more expensive than input tokens?
Generating output requires the model to run a decoding process for each generated token, while input processing and infrastructure are priced differently. The exact ratio varies by provider and model. A short prompt that requests a very long answer can cost more than a large document summarized into a short answer, so estimate both sides.
Does a ChatGPT or Claude subscription include API usage?
Usually not. Consumer or workplace subscriptions and developer APIs are separate products with separate billing, limits, and terms. Check the specific provider account and plan. Do not assume a paid chat subscription gives your application an API allowance.
How does prompt caching reduce AI cost?
Prompt caching lets a provider reuse a repeated prefix or context instead of processing it as a fresh input every time. Providers differ in cache eligibility, minimum size, time-to-live, write cost, read cost, and whether cache hits are implicit or explicitly configured. Measure cache hits and misses; a long prompt is not automatically cheaper just because caching exists.
What is the real cost of an AI agent?
An agent costs more than one model response. Include every model turn, tool call, retrieval step, browser or search charge, file or image processing, retries, failed actions, storage, orchestration, observability, human review, support, and the work required to correct errors. Estimate cost per completed task and the distribution of expensive runs, not only the average token price.