What does your prompt cost?

Every prompt has a price. Know it before you send.

Paste anything. See token counts and price across every major model — computed in your browser, not on a server.

Gateways and monitoring tools optimize spending you already have. Token Bench tells you what you’ll spend before you commit.

Try an example:
0 chars0 words0 lines

Monthly cost by model

%

Reply length is converted to tokens separately for each model, using how that model tokenized your text. Reasoning models bill their hidden thinking as output; if you use one, enter a typical figure from your API usage logs. The repeating part is anything sent unchanged every time, such as a system prompt, and is billed at the cached rate.

ModelIn /1MOut /1MContextPer requestPer monthvs cheapest

A month is 30 days. Rows marked est. use estimated token counts; use “get exact count” above for Claude and Gemini. Cache-write charges, batch discounts and negotiated rates aren’t included.

Mix two models

route routine requests to a cheaper model
%
%
%

The success rates are example values: replace them with what you measure by testing each model on your own requests. Costs are per completed task. When the routine model fails, the request is sent on to the hard model; when the hard model fails, it’s retried. Uses your prompt and the usage settings above, and assumes routine and hard requests are about the same size. It doesn’t include the cost of deciding where each request goes.

Batch & repo estimator

Drop many files at once for a combined token and cost total. Files are read locally and never uploaded.

FileCharsOpenAIClaudeGemini
No files yet

Open-model tokenizers

Exact counts for Llama 3, Mistral and Grok 1. The real tokenizer downloads once from Hugging Face, then runs offline in your browser.

—select a model to load its tokenizer

Prompt compressor

Strips filler, hedge words and citations to cut tokens. Rule-based, so dense technical prose may compress very little.

paste a prompt above

Multimodal calculator

Image, video and audio token counts using Google's published Gemini formulas.

0tokens · 0 image + 0 video + 0 audio
$0.00000

Caching savings

Model the cost of sending the same prompt repeatedly with prompt caching enabled. Uses the text from the main calculator.

paste text in the main calculator first

Token heatmap

See which parts of a prompt cost the most. Darker shading means more tokens for each character.

Token Game

Which text costs more AI tokens? Guess right to keep your streak going, and learn why as you play.

Streak 0Best 0
This costs
Does this cost more or fewer tokens?
?

Counted with o200k, the tokenizer behind OpenAI’s recent models. Other models split text differently, so their counts would differ, but the same kinds of text tend to be expensive everywhere.

Prompt Builder

Build a prompt from blocks. Every brick is one token. Fit the job inside the budget, without leaving out anything the job needs.

The job

Token budget0 / 0 tokens

Your prompt

Your prompt in cubes

One cube per token. Cubes above the dashed budget line turn red.

Blocks

Bricks are counted with o200k, the tokenizer behind OpenAI’s recent models. Savings are worked out at 10,000 requests a day on GPT-6.1 Sol, where every token in a prompt costs about $0.60 a month. In Hard, the reply’s length is an assumption based on typical replies: about 50 tokens for two sentences, 80 for 60 words, and 260 when nothing limits it, with Hindi replies about 2.6 times longer in tokens. Real replies vary.

Token Academy

Learn what AI tokens are, why they cost what they do, and how to spend fewer, through short games. Three levels, about fifteen minutes. No sign-up: your progress is saved in this browser.

Browser extension

See cost while you type — not after.

CHROME EXTENSION

Live cost inside ChatGPT, Claude and Gemini

A small overlay shows your running token count and cost as you write, so you catch an expensive prompt before you send it. Counting happens locally — no text leaves the page.

Coming soon

Submitted to the Chrome Web Store and awaiting review. This page will link to the listing once it’s approved.

API

Token counts and cost for any text, across every supported model. Free to use while in beta.

POST /api/v1/tokenize
curl -X POST https://whatdoesmypromptcost.com/api/v1/tokenize \
  -H 'content-type: application/json' \
  -d '{"text":"Hello world","models":["gpt-6.1-sol"]}'
Model list and live rates are public and unauthenticated at /api/v1/models

Status

beta

The API is free and open while in beta. There are no accounts or keys yet, and no published request limits — there is basic abuse protection, but we won't quote a number we can't guarantee. Build against it, but don't depend on it for anything critical until it's out of beta.

Paid tiers with committed limits and an SLA are planned. If you want to be told when they land, or you need higher volume sooner, get in touch.

Response fields

FieldMeaning
tokensToken count for that model
methodexact — counted with the real tokenizer · estimate — character ratio, no public tokenizer exists
input_cost_usdCost to send this text as input
fits_contextWhether it fits that model's context window

Case study: team cost dashboard

A concept for what per-team LLM cost tracking could look like. Built as a design exercise, not a live product.

ILLUSTRATION ONLY

Every number in this dashboard is randomly generated sample data. Nothing is connected to a backend, no accounts exist, and no real usage is being tracked. It exists to show the shape of the idea.

The problem it addresses

A calculator answers "what will this cost?" before you send a prompt. It doesn't answer "what did we spend last month, which team spent it, and why is it climbing?" — which is the question that actually reaches a finance or engineering lead once a company has several LLM features in production.

Two audiences, one surface

ViewAnswers
BusinessSpend over time, budget vs. cap, cost by team and project, which provider dominates
IT / developerRequest volume, error rate, latency, per-key rate-limit headroom, request log

What making it real would require

Authentication so each organisation sees only its own data, a database logging every API call, an SDK that wraps a customer's LLM calls to feed that log, and a scheduled job for budget alerts. That's a different product from a calculator — which is why it's shown here as a concept rather than shipped as a feature.

Contact

Token Bench is built by Vector & Value AI. Email is the best way to reach us.

[email protected]

A few details help us answer quickly:

A price looks wrongThe model name, a link to the provider’s pricing page, the price and currency it shows, and the date you checked it.
API accessRoughly how many requests a month you expect.
Research or dataWhich study or dataset you’re asking about.
Something’s brokenThe page address, your browser, and what you expected to happen.
Business enquiriesA line about your company and what you’re looking for.

Corrections backed by an official provider page are applied directly, and the “last verified” date in our FAQ is updated to match. Figures on this site are estimates for planning. They aren’t financial or procurement advice, and they don’t reflect negotiated enterprise rates.

FAQ

Gateways, routers and monitoring tools work on traffic that’s already running: they cache, reroute and report on requests your application is making. Token Bench works before that point. It tells you what a prompt will cost on each model, in your language, at your volume, and whether routing between models would be worth setting up, so you can decide before you commit to a provider or build the plumbing. Many teams will want both.
No. OpenAI and open-model counts run entirely in your browser using the real tokenizers. Nothing is uploaded, logged or stored. The only exception is if you click “get exact count” for Claude or Gemini — that sends your text to our server, which forwards it to the provider’s counting endpoint and returns just a number.
OpenAI counts use o200k, the tokenizer OpenAI published for its recent models, run in your browser. OpenAI hasn’t published a tokenizer for GPT-6, but independent tests found o200k matches GPT-6.1 Sol. Llama, Mistral and Grok 1 publish their tokenizers as open files, which the Open models tool runs offline. Anthropic and Google only expose token counting as an API call that needs a secret key, and a key can’t live safely in browser code, so those show a character-ratio estimate until you request an exact count. Current Grok models and DeepSeek publish no browser-usable tokenizer, so their counts are always estimates.
Usually within a few percent for ordinary English prose. They drift further on code, non-Latin scripts and heavily formatted text, where tokenizers behave differently. Treat estimates as a planning figure, not a billing figure.
Rates were last verified on 14 October 2026 against each provider’s official pricing page. Providers change prices without notice, so always confirm against your own billing dashboard before making a purchasing decision. Announced price changes are applied automatically on their date: Gemini 4 Argon rises from $2 / $10 to $4 / $20 per million tokens on 1 December 2026, and Gemini 3.8 Flash doubles on 1 January 2027. Rows with a coming change are labelled.
Most providers let you send requests in bulk and collect the results later, usually within 24 hours, in exchange for a discount. It suits work nobody is waiting on: classifying records, summarising an archive, running tests. It doesn’t suit chat or anything a user is watching. The discount varies: half price at OpenAI, Anthropic and Google, 20% on Grok 4.3, and none on Grok 4.7 or DeepSeek. One detail to watch: on Gemini 3.1 Pro, batch halves input and output but not cached input. Batch and caching discounts can be combined. OpenAI and Google also offer “flex” processing at the same prices as batch, for requests that return directly but more slowly. Tick “Batch processing” under the cost table to see batch prices.
Three reasons, all common. First, replies vary: the monthly figures assume the reply length you set, and output is priced three to five times higher than input, so longer replies than expected, or hidden reasoning tokens you didn’t include, move the total quickly. Second, some prices depend on when you call: DeepSeek charges double during its peak hours, which in India fall on weekday mornings and early afternoons (about 6:30–9:30 and 11:30–15:30), and the table shows DeepSeek’s off-peak rate. Gemini 3.8 Flash’s introductory rate also doubles on 1 January 2027. Third, the table uses standard list prices, and batch, regional, priority and negotiated rates all differ. Long-context pricing, where the whole request costs more once a prompt passes a model’s threshold, is applied automatically and marked in the table.
Yes — a single POST /api/v1/tokenize endpoint returns counts and cost for any text across all supported models. It’s free and in beta: there are no accounts or keys yet, and no published request limits. See the API page for details.
It removes conversational filler and hedge words. Text that’s already dense — academic papers, technical docs, minified code — has little for it to remove, so it correctly leaves it alone. Try the citation and aggressive toggles for academic prose.
For your bill, yes: you pay for every token. For the quality of the answer, not necessarily. Shortening a prompt can remove context the model needed, so after using the compressor, check that the answers haven’t got worse. The same is true of tokenizers themselves: recent research found that a tokenizer which splits text into fewer pieces doesn’t automatically help a model understand that text better. Treat a token count as a measure of cost, not of quality.
Input tokens are what you send; output tokens are what the model generates back. Output is usually priced three to five times higher. Set your expected reply length under the cost table and the monthly figures include both.