Pricing Fallback snapshot · 43 models · 7 providers · snapshot reviewed September 16, 2026.
Chatbot cost

AI Chatbot Cost Calculator

Price a conversation, not just a single request.

Calculator

Estimate your workload

Change the assumptions on the left; read the modeled result on the right.

Method

How to read this estimate

Guide

What this calculator is for

A six-turn conversation is not simply six identical calls if prior messages are resent. This calculator approximates the history carried forward so you can budget a production support or assistant experience more realistically.

How to read the result

Cost per conversation represents one complete modeled interaction with its turns and history. Monthly cost multiplies it by conversation count. The input and output token totals explain why longer histories can make each conversation progressively more expensive.

The math

Monthly chatbot cost = modeled cost per conversation × conversations per month; input grows as repeated system prompts and conversation history are carried forward.

Pricing sources

Rates use the published TokenCOGS pricing registry and its September 16, 2026 fallback snapshot. Live values may differ; see methodology and source limitations before procurement.

Planning limitations

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.

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.

Why does increasing conversation turns raise costs quickly?

The model may receive part of earlier messages again on later turns. That repeated history increases input tokens in addition to the new replies.

Does conversation history increase cost?

Yes when prior turns are included in later requests. Trimming, summarizing or caching repeated context can reduce billed input.