identity

proprietary
OpenAI logo

gpt-5.4-nanoOpenAI

from /1M in$0.10openai inc.
context400K128K out
providers11 region
price spread2.0x2 endpoints
endpoints
2
regions
1
api
chat
released
March 2026

capabilities 5/8

visionreasoningtoolscachingweb searchjson schemacomputer useimage gen

The same weights cost 2.0x more on openai inc. than on openai inc.. That is what the endpoints table is for.

endpoints

2 / 1 region
Providers serving gpt-5.4-nano, with pricing and measured performance. Best value in each column is coloured.
#flags
1OpenAI Inc.Global400K$0.10$0.63$0.01no-train
2OpenAI Inc.Global400K$0.20$1.25$0.02no-train
provider price, no markupper 1M tokensblank where no qualifying sample

measured

through Sep 12

no measured traffic for this model yet. the endpoints table above carries provider pricing

benchmarks

artificial analysis
Benchmark scores, each normalised to 100
evalScore as a share of 100/100
GPQA Diamond81.7
τ²-Bench76.0
Coding Index56.1
SciCode47.2
Terminal-Bench Hard42.4
Humanity's Last Exam28.3
Intelligence Index21.2
7 evalsmean50.4

Scores from Artificial Analysis and public leaderboards, normalised to 100. Bar colour is the band, not the rank: green 80 and up, blue 55 and up, amber 30 and up. Benchmarks measure narrow skills, so test on your own workload before committing. Released 2026-03-17.

call it

model=
gpt-5.4-nano

requesty routes this id across every provider serving gpt-5.4-nano, picking on price and health and failing over automatically. the id stays valid when a provider changes underneath it

Base url is https://router.requesty.ai/v1 for every id here. One key reaches the whole catalog.

quickstart

openai compatible
main.py
from openai import OpenAI client = OpenAI(    api_key="YOUR_REQUESTY_API_KEY",    base_url="https://router.requesty.ai/v1",) response = client.chat.completions.create(    model="gpt-5.4-nano",    messages=[        {"role": "user", "content": "Explain quantum computing in one paragraph."},    ],) print(response.choices[0].message.content)

Change the base url, use your Requesty key, set the model to any id in the call pane. Existing OpenAI SDK code needs no other edit, and the same key reaches every other model in the catalog, so switching later is a one-parameter change. Browse all models

notes

reference

GPT-5.4 mini brings the core capabilities of GPT-5.4 to a faster, more efficient model optimized for high-throughput workloads. It supports text and image inputs with strong performance across reasoning, coding, and tool use, while reducing latency and cost for large-scale deployments. The model is designed for production environments that require a balance of capability and efficiency, making it well suited for chat applications, coding assistants, and agent workflows that operate at scale. GPT-5.4 mini delivers reliable instruction following, solid multi-step reasoning, and consistent performance across diverse tasks with improved cost efficiency.

questions 6

Which providers serve gpt-5.4-nano?
gpt-5.4-nano is available from 1 provider through Requesty: OpenAI Inc.. All endpoints share one OpenAI-compatible API and one key, and Requesty fails over between them automatically.
How much does gpt-5.4-nano cost?
Pricing starts at $0.10 per million input tokens and $0.63 per million output tokens on the cheapest provider. Prices vary by provider and region; the table above shows every endpoint. Requesty charges exactly what the upstream provider charges, with no markup.
Is gpt-5.4-nano open weights?
No. gpt-5.4-nano is a proprietary model from OpenAI, served through OpenAI's own API and licensed cloud platforms.
What is the context window of gpt-5.4-nano?
gpt-5.4-nano supports up to 400K tokens of context, with up to 128K output tokens per response. Some providers expose a smaller window; check the per-endpoint context column above.
How do I use gpt-5.4-nano with the OpenAI SDK?
Install the OpenAI SDK, set base_url to "https://router.requesty.ai/v1", set your API key to your Requesty key, and set the model to "gpt-5.4-nano" or any endpoint id from the table above. The quickstart section shows Python, JavaScript and cURL snippets.
Should I call gpt-5.4-nano by its managed id or a provider id?
Use the managed id, "gpt-5.4-nano". Requesty picks which of the 1 provider serves each request based on price and health, and fails over when one degrades, so the id keeps working while the routing changes underneath it. Send a provider id like "openai/gpt-5.4-nano:flex" only when you need one specific deployment and want no failover.

more from openai 6

Other OpenAI models
modelcontextfrom /Mproviders
gpt-6-astra1.1M$5.002
gpt-5.6-luna1.1M$0.103
gpt-5.6-terra1.1M$1.003
gpt-5.6-sol1.1M$2.503
gpt-5.5-pro1.1M$30.001
gpt-5.51.1M$2.503

route gpt-5.4-nano through one endpoint

One key for 1 provider on this model and 600+ others. No markup on provider prices, automatic failover, caching built in. Weekly aggregates in the measured pane come from production traffic routed through Requesty, one line per provider on a shared axis. Methodology

gpt-5.4-nano1 provider2 endpointsfrom $0.10 /1M inctx 400Kspread 2.0xupdated Sep 12