GPT-5 ships as a router, not a model picker
OpenAI released GPT-5 into its API platform on Aug 7 in three sizes — gpt-5, gpt-5-mini and gpt-5-nano — reporting 74.9% on SWE-bench Verified, 88% on Aider polyglot, 69.6% on Scale MultiChallenge and 96.7% on tau2-bench telecom, a tool-calling benchmark published two months earlier. In ChatGPT it replaces GPT-4o, o3, o4-mini, GPT-4.1 and GPT-4.5 behind a real-time router that decides between a fast answer and reasoning; the API adds a verbosity parameter, a minimal reasoning effort level, and custom tools that call with plaintext constrained by context-free grammars instead of JSON.
Pricing is $1.25 per million input tokens and $10 per million output for gpt-5, $0.25/$2 for mini and $0.05/$0.40 for nano — TechCrunch reported the flagship undercuts Anthropic's Claude Opus 4.1 at $15/$75 by enough to start a price war. Within 24 hours Altman acknowledged a bumpy rollout on Reddit, API traffic had doubled, and OpenAI restored GPT-4o access for Plus subscribers and promised to make the router's model choice visible.

WHY IT MATTERS
Once a router sits between your prompt and the model, latency, cost and reliability become runtime variables you cannot pin from the client side — and the same policy that produced the launch week's complaints can be retuned without a version bump. Pin snapshot IDs, measure dollars per resolved task on your own workloads, keep a fallback model wired in, and instrument which variant actually served each request before you move production traffic.
