identity

proprietary

gpt-5-nanoOpenAI

Name: gpt-5-nano
Brand: OpenAI
SKU: openai/gpt-5-nano
Price: 0.0250 USD
Availability: InStock

from /1M in$0.02openai

context400K128K out

providers26 regions

price spread2.2x8 endpoints

endpoints: 8
regions: 6
api: chat
released: August 2025
eu routing: available

capabilities 5/8

visionreasoningtoolscachingweb searchjson schemacomputer useimage gen

The same weights cost 2.2x more on microsoft azure ai than on openai. That is what the endpoints table is for.

endpoints

8 / 6 regions

Providers serving gpt-5-nano, with pricing and measured performance. Best value in each column is coloured.
#							flags
1	OpenAI	Global	400K	$0.02	$0.20	$0.0025	no-train
2	Microsoft Azure AI	Global	200K	$0.05	$0.40	$0.0050	zdr
3	OpenAI	Global	400K	$0.05	$0.40	$0.0050	no-train
4	Microsoft Azure AI	eastus2	200K	$0.05	$0.40	$0.0050	zdr
5	Microsoft Azure AI	francecentral	200K	$0.06	$0.44	$0.0055	zdr
6	Microsoft Azure AI	germanywestcentral	200K	$0.06	$0.44	$0.0055	zdr
7	Microsoft Azure AI	swedencentral	200K	$0.06	$0.44	$0.0055	zdr
8	Microsoft Azure AI	westeurope	200K	$0.06	$0.44	$0.0055	zdr

provider price, no markupper 1M tokensblank where no qualifying sample

measured

through Nov 2

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

benchmarks

artificial analysis

no published benchmark scores for this model

call it

model=

gpt-5-nano@eu

same routing, restricted to eu-hosted providers. use this id when data residency is a requirement; requests never leave the eu

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

quickstart

openai compatible

main.py

1from openai import OpenAI2 3client = OpenAI(4    api_key="YOUR_REQUESTY_API_KEY",5    base_url="https://router.requesty.ai/v1",6)7 8response = client.chat.completions.create(9    model="openai/gpt-5-nano:flex",10    messages=[11        {"role": "user", "content": "Explain quantum computing in one paragraph."},12    ],13)14 15print(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 nano is OpenAI's fastest, cheapest version of GPT-5. It's great for summarization and classification tasks.

questions 5

Which providers serve gpt-5-nano?

gpt-5-nano is available from 2 providers through Requesty: OpenAI, Microsoft Azure AI. All endpoints share one OpenAI-compatible API and one key, and Requesty fails over between them automatically.

How much does gpt-5-nano cost?

Pricing starts at $0.02 per million input tokens and $0.20 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-nano open weights?

No. gpt-5-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-nano?

gpt-5-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-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 "openai/gpt-5-nano:flex" or any endpoint id from the table above. The quickstart section shows Python, JavaScript and cURL snippets.

more from openai 6

Other OpenAI models
model	context	from /M	providers
gpt-6.1-terra	1.1M	$0.50	2
gpt-6.1-sol	1.1M	$1.00	2
gpt-6-luna	1.1M	$0.05	2
gpt-6-sol	1.1M	$1.00	2
gpt-6-astra	1.1M	$5.00	2
gpt-5.6-luna	1.1M	$0.10	3

route gpt-5-nano through one endpoint

One key for 2 providers 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