GPT-5.5 is OpenAI’s frontier model designed for complex professional workloads, building on GPT-5.4 with stronger reasoning, higher reliability, and improved token efficiency on hard tasks. It features a 1M+ token context window (922K input, 128K output) with support for text and image inputs, enabling large-scale reasoning, coding, and multimodal workflows within a single system.
Modalities
In / Out Price
$5 / $30per 1M
Context
1M
Released
Apr 24, 2026
Knowledge Cutoff
Dec 2025
GPT-5.5 is OpenAI’s frontier model designed for complex professional workloads, building on GPT-5.4 with stronger reasoning, higher reliability, and improved token efficiency on hard tasks. It features a 1M+ token context window (922K input, 128K output) with support for text and image inputs, enabling large-scale reasoning, coding, and multimodal workflows within a single system.
GPT-5.5 costs $5.00/M input tokens and $30.00/M output tokens, with separate rates for Cache Read at $0.50/M tokens and Web Search at $10.00/1K calls.
GPT-5.5 has a 1,050,000 token context window. It supports up to 128,000 completion tokens.
Yes. GPT-5.5 accepts tools and tool_choice for function calling. It also supports structured outputs via a JSON schema in response_format.
GPT-5.5 accepts files such as PDFs, images and text as input and returns text.
GPT-5.5 is served by 3 providers on OpenRouter: OpenAI, Azure (US) and Amazon Bedrock (US). Requests are routed to the best available provider, with automatic failover to the others, and you can pin or exclude providers with provider routing.
GPT-5.5 was released on April 24, 2026. Its knowledge cutoff is December 1, 2025.
Different companies host the same model. OpenRouter routes your request to one of them based on the routing mode you pick — Balanced (price + speed), Nitro (fastest), or Exacto (highest tool-calling accuracy).
The average price customers actually pay for this model, next to the prices providers post. Caching and discounts mean the price actually paid is often well below the listed one.
Throughput is how fast the model writes (tokens per second — higher is better). Latency is total round-trip time (lower is better). TTFT is time-to-first-token — how long before you see anything appear (lower is better).
Uptime is the percentage of the past 3 days that at least one provider was responding to requests. Availability is the percentage of time that inference was successfully served. OpenRouter continuously monitors and uses the next-best provider when one returns an error.
Scores on standardized evaluations. Higher percentages are better — and rank percentile shows where this model lands among all models on OpenRouter.
Public apps that send the most traffic to this model. Good signal for what real production workloads look like — and a hint at which use cases this model is best suited for.
Token volume and request traffic to this model over time.
Drop-in code to call this model. OpenRouter's API is OpenAI-compatible — most SDKs work by just swapping the base URL. The only thing that changes between models is the model slug below.
| $5.00 | $30.00 | $0.50 | 2.07s | 44 tps | ||
| $5.00 | $30.00 | $0.50 | 3.58s | 35 tps | ||
| $5.50 | $33.00 | $0.55 | 5.70s | 49 tps | ||
| $5.50 | $33.00 | $0.55 | 3.43s | 8 tps | ||
| $5.50 | $33.00 | $0.55 | -- | -- |
Throughput
49tok/s
P50, best across providers
Latency
2.07s
P50, best provider
100.00%
99.64%
When an error occurs in an upstream provider, we can recover by routing to another healthy provider, if your request filters allow it. You can access per-provider uptime data programmatically through the Endpoints API. Learn more about our load balancing and customization options.
