GPT-5.5 vs GPT-5 Mini
Compare GPT-5.5 and GPT-5 Mini on the metrics that decide an agent workload.
| Metric | GPT-5.5 | GPT-5 Mini |
|---|---|---|
| Provider | OpenAI | OpenAI |
| Input / 1M | $5.00 | $0.25 |
| Output / 1M | $30.00 | $2.00 |
| Cache read / 1M | $0.50 (−90%) | $0.03 (−90%) |
| Reuse-adj @55% | $9.39 | $0.59 |
| Context | 1.1M | 400K |
| Cache capture | 88% | 85% |
| Warm TTFT | 240ms (−67%) | 150ms (−63%) |
| Quality index | 96 | 82 |
Teal marks the better value in each row. Reuse-adjusted assumes 55% prefix reuse and a 25% output share.
Pick GPT-5.5 when it scores higher on the composite quality index, it carries the larger 1.1M context window, it captures more of the available reuse.
Pick GPT-5 Mini when it is cheaper once prefix reuse is priced in, it answers faster on warm cache hits.
GPT-5.5 leads on quality while GPT-5 Mini leads on reuse-adjusted cost. Send latency- and budget-sensitive volume to GPT-5 Mini and reserve GPT-5.5 for the hard requests. Zumik's aliases route between them automatically under policy.
GPT-5.5 vs GPT-5 Mini, answered.
Is GPT-5.5 or GPT-5 Mini cheaper?
At 55% prefix reuse, GPT-5.5 blends to about $9.39 per 1M tokens and GPT-5 Mini to about $0.59. GPT-5 Mini is cheaper on that basis.
Which has the larger context window?
GPT-5.5 has the larger window: 1.1M vs 400K tokens.
Which captures more reuse?
GPT-5.5 shows higher measured cache capture (88% vs 85%) in the Zumik corpus.
Let an alias pick for you.
Route to whichever model wins under current policy automatically. Zumik resolves the alias to the best fit per request, so you never hard-code a loser.