Claude Haiku 4.5 vs GPT-5 nano

Cheap-tier models for classification and routing.

Prices verified 4 Aug 2026
Input / 1M$1.00
Output / 1M$5.00
Cached input / 1M$0.100
Batch50% off
Context200K tokens
Blended (3:1)$2.00
Input / 1M$0.050
Output / 1M$0.400
Cached input / 1M$0.00500
Batch50% off
Context400K tokens
Blended (3:1)$0.138

Monthly cost by workload shape

The same volume costs very different amounts depending on the shape of the traffic. No caching or batch applied.

WorkloadClaude Haiku 4.5GPT-5 nanoDifference
Customer support chatbot
50K/day · 800 in / 300 out
$3,500.60$243.52GPT-5 nanosaves $3,257.08Model it →
RAG / search answers
20K/day · 3000 in / 400 out
$3,044.00$188.73GPT-5 nanosaves $2,855.27Model it →
Agent / tool-use loop
8.0K/day · 2500 in / 600 out
$1,339.36$88.88GPT-5 nanosaves $1,250.48Model it →
Batch summarization
100K/day · 5000 in / 500 out
$22.8K$1,369.80GPT-5 nanosaves $21.5KModel it →
Code assistant
15K/day · 2000 in / 800 out
$2,739.60$191.77GPT-5 nanosaves $2,547.83Model it →

Frequently asked questions

Which is cheaper, Claude Haiku 4.5 or GPT-5 nano?

At a typical 3:1 input-to-output ratio, GPT-5 nano is cheaper: $0.138 blended per 1M tokens against $2.00. That holds at every input:output ratio — one model is cheaper on both rates.

What is the price difference between Claude Haiku 4.5 and GPT-5 nano?

Claude Haiku 4.5: $1.00 input, $5.00 output per 1M tokens. GPT-5 nano: $0.050 input, $0.400 output. That is 20.0x on input and 12.5x on output.

Does prompt caching change the answer?

Claude Haiku 4.5 caches input at $0.100/1M and GPT-5 nano caches at $0.00500/1M. For input-heavy workloads with repeated context, caching can matter more than the base rate difference — model both in the calculator rather than comparing rate cards.

This page compares published prices only. It makes no claim about which model performs better on any task — that depends entirely on your evaluations.

Rate cards decide nothing on their own.

Most teams run several models at once. Finitizer TokenOps shows what each one actually costs you in production, by team and feature, so a routing decision is made on data rather than on a price page.