AI Chatbot Cost Calculator
Estimate model-token spend from active users, requests per user each month, and average tokens in every model call. The starting values are editable scenario inputs.
Choose a model
Set your usage
These are editable scenario inputs, not usage benchmarks.
Monthly model calls = active users × requests per user. Count each call sent to the model, including separate calls made during one visible chat turn.
Include system instructions, the latest message, and any conversation history sent with this call.
Include reasoning or thinking tokens if your provider bills them as output. This estimate does not infer them.
Review the estimate
Estimate for GPT-6 Luna at public standard text rates checked October 17, 2026.
Cost at different volumes
Each row keeps the same token assumptions.
| Active users | Requests / month | Monthly | Annual |
|---|---|---|---|
| 100 | 1.0K | $0.1500 | $1.83 |
| 1.0K | 10.0K | $1.50 | $18.25 |
| 10.0K | 100.0K | $15.00 | $182.50 |
| 100.0K | 1.0M | $150.00 | $1,825.00 |
Monthly estimates use 30 days. Annual estimates use 365 days.
Estimate covers public standard text input and output rates only. If your provider bills reasoning or thinking tokens as output, include them in your output-token estimate; this calculator does not infer them. It excludes cached-token pricing, batch discounts, external tools and search, embeddings, vector stores, hosting and infrastructure, negotiated discounts, free-tier credits, and image, audio, video, or voice usage.
Save your results
Get your cost estimate sent to your inbox. We'll also send tips on how to reduce your AI spending.
No spam. Unsubscribe any time.
What drives chatbot token spend
This calculator multiplies active users by requests per user per month. Each request is priced as one call to the selected model using your average input and output token counts.
A request can include more than the latest message. If your app sends system instructions, prior chat turns, or retrieved context again, include them in the average input tokens. Longer sent history raises input-token usage for that request, and the estimate prices the total prompt you enter.
