Traffic planning

AI Cost per 1,000 Requests Calculator

Estimate the API cost of 1,000 requests across GPT, Claude, Gemini, Mistral and other leading models using your average input and output token size.

Free · no signup · runs in your browser

Common workloads

Use the same unit across different AI features

Keep request count fixed at 1,000, then change the average token size to match the product experience you are planning.

1,000 chatbot requestsModel short support or product conversations with your expected prompt and response length.

1,000 agent requestsUse a larger token assumption when one user task triggers multi-step reasoning or repeated model calls.

1,000 summarization requestsIncrease input tokens for long documents and compare how model choice changes the unit cost.

What this calculator is for

Cost per thousand requests is a practical bridge between engineering metrics and business forecasting. It makes it easy to estimate a 10K, 100K or 1M request month without rebuilding a spreadsheet.

The math

Cost / 1K = 1,000 × token cost per request

Actual invoices can differ because providers may apply long-context pricing, caching rules, batch rates, tool-call fees, regional processing, negotiated contracts, taxes, or future pricing changes. Treat the output as a planning estimate.

Pricing sources

Current model rates are sourced from official provider pricing pages and verified on September 16, 2026. The methodology page records the source links and known limitations.

Related pricing tools

Compare a full monthly workload in the LLM API Cost Calculator, translate API spend into product margin with the AI Cost per User Calculator, or compare current rates in the AI model pricing directory.

Frequently asked question

Why use cost per 1,000 requests?

It gives teams a stable unit for comparing model choices and forecasting traffic scenarios while preserving the input/output token assumptions.

Can I use this estimate for a production budget?

Use it to create scenarios and catch order-of-magnitude mistakes. Before committing spend, verify the selected model's live provider pricing and compare the estimate with actual usage telemetry.