This model is hosted by one provider. OpenRouter forwards every request to it directly — no routing decisions to make.
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.
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.
A cost-efficient variant of GPT Image 1 for high-quality image generation at reduced latency and cost via OpenAI's dedicated Images API.
GPT Image 1 Mini costs $2.50/M input tokens and $2.50/M output tokens, with separate rates for Cache Read at $0.25/M tokens, Text Input at $2.00/M tokens and Image Output at $8.00/M tokens.
GPT Image 1 Mini supports the 1:1, 3:2 and 2:3 aspect ratios and can generate up to 10 images per request.
GPT Image 1 Mini accepts text and images as input and returns images. Up to 16 reference images can be attached to one request for image editing.
GPT Image 2 and GPT Image 1 are other image models from OpenAI.
GPT Image 1 Mini was released on June 24, 2026.
| $2.00 | $8.00 | $0.25 | 0.14s | 82 tps |
Throughput
82tok/s
P50, best across providers
Latency
0.14s
P50, best provider
100.00%
99.53%
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.
