Cheapest frontier models per 1M tokens

Published 2026-10-17 · Updated 2026-10-26

Price-per-token comparisons lie in boring ways, so a few ground rules first: always compare input and output separately (output is usually 3–10× input), check whether cached-input pricing exists, and remember that a chatty model that writes more tokens to reach the same answer costs more than the table implies.

Reading the OpenRouter pricing fields

The /models endpoint prices in dollars per token. Multiply by a million for the number everyone quotes. prompt is input, completion is output, and input_cache_read, when present, is the discounted price for re-sent context.

The cheap end of the frontier

As of late October 2026, the pattern across the catalog:

A fair way to compare for your workload

  1. Estimate your real input:output ratio, chat apps are often 4:1 input-heavy, summarization 10:1, agents 20:1.
  2. Price a representative request, not a token. input_tokens × prompt + output_tokens × completion.
  3. Add the cheapest-provider tax: rate limits and queueing cost engineering time too.

The catalog on this site carries the per-token numbers for each model, check the model page for the exact figures before committing a workload to a provider.