How AI pricing works
AI pricing usually looks confusing because providers bill in token units instead of in plain requests. In practice, most cost comes from three buckets: the prompt you send in, the response the model sends back, and any cached context the provider can reuse at a discount.
Once you separate those buckets, the pricing model gets much easier to reason about. A support bot with short prompts and long answers has a different cost profile than a retrieval-heavy app with large prompts and brief answers.
Input cost
This is what you pay for the text, instructions, and context you send to the model. Long prompts, large retrieval chunks, and repeated boilerplate all push this up.
Output cost
This is what you pay for the model’s answer. In many production flows, output is the dominant cost because long responses add up fast.
Cached input
Some providers discount repeated context. If your system prompt or reference material is stable across requests, caching can materially lower cost.
The three questions that matter most
The easiest way to estimate AI cost is to stop asking “what does this model cost?” and start asking three narrower questions.
- How many tokens am I sending on each request?
- How many tokens am I getting back on each response?
- How often does that request happen in a day or month?
Once you know those numbers, the rest is multiplication. That is why the calculator on this site focuses on per-request cost first and monthly cost second.
A simple example
Imagine a workflow that sends a 1,200-token prompt and gets back a 2,400-token answer. If that happens once, the cost is tiny. If it happens 500,000 times a month, the same workflow becomes a real budget line.
That is why monthly usage matters more than a single “price per million tokens” line. Rate cards tell you the unit price. Operations volume determines whether the unit price is a rounding error or a problem.
Where teams overspend
- Repeating long instructions on every request.
- Asking for longer answers than the product actually needs.
- Running expensive models on routing, labeling, or extraction tasks.
- Ignoring cached-input discounts when context barely changes.
How to lower AI cost without wrecking quality
The best cost cuts are usually boring. Trim repeated prompt boilerplate, set tighter output limits, route cheap work to cheaper models, and only keep large context blocks when they are pulling their weight.
The wrong way to optimize is to blindly slash tokens everywhere. Good optimization keeps the answers good enough for the job while removing waste from the edges.
Use this next
If you already know your approximate prompt and answer length, go straight to the AI cost calculator.
If token units still feel abstract, the best companion page is What is an AI token?.
Maintained by David K. · Last reviewed: July 23, 2026
Model token costs, request volume, and scenario-based monthly spend without guesswork.
Open calculatorCheck monthly payment with taxes, insurance, HOA, and a more realistic ownership picture.
Open calculatorWork backward from income, debts, and down payment into a realistic house budget band.
Open calculatorEstimate panel count, annual production, incentives, and a simple payback range.
Open calculator