LLM Cost Estimator

Estimate your monthly LLM API bill from tokens and traffic, include caching and batch discounts, and compare the same workload across popular models.

1. Model

Prices are USD per 1M tokens. Pick a preset or enter your own.

$
per 1M input tokens
$
per 1M output tokens

2. Your workload

prompt, history, retrieved context

3. Discounts (optional)

Check your provider's terms. Cache and batch discounts vary.

%
%
%
applies to the whole request cost

Your estimate

Updates as you type.

Estimated monthly cost
-
Cost per request
-
Cost per 1,000 requests
-
Per day
-
Per year
-
If traffic grows 10×
-
monthly cost at ten times the volume

Same workload on other models

Your selected model. “×” shows how many times more than the cheapest.

Estimates from list prices only (reviewed Nov 2026). Excludes tax, fine-tuning, tool calls, image or audio tokens and negotiated discounts. Verify with your provider.

Know what each customer costs you

MetricaOS tracks tokens and cost per customer, per model and per feature in real time, so the bill never surprises you. Free plan, no credit card.

Start free with MetricaOS

How LLM API costs are calculated

Providers charge separately for input and output tokens, priced per million. The cost of a request is input tokens × input price + output tokens × output price, scaled to a million. Output tokens usually cost several times more than input tokens, so verbose answers drive the bill more than long prompts.

Two levers cut cost without changing the product: prompt caching (repeated context billed at a steep discount) and batch APIs (asynchronous work at a lower rate). Model choice matters most: the comparison above shows how far apart models can be on identical traffic.

Once you know your cost, the next step is pricing. Try the AI Pricing & Margin Calculator, and read about LLM cost tracking and attributing AI cost to customers.

Frequently asked questions

Common causes: conversation history growing the input on every turn, retries, system prompts counted on every request, tool or function-call tokens, and reasoning tokens that are billed as output. Measure actual token usage per request and plug in the averages.

Providers can bill repeated prefix tokens (such as a long system prompt or document) at a discount when they are served from cache. Enter the share of input tokens you expect to be cached and the discount your provider offers.

The presets are representative list prices that change often. Edit the price fields to match your provider's current pricing page.

No. It runs in your browser, and the share link keeps your inputs in the URL fragment, which is not sent to our servers.