GPT-5.6 Sol (Azure) vs GPT-5.6 Sol
GPT-5.6 Sol is the lower-priced of the two on Router One at base-tier rates (GPT-5.6 Sol (Azure) and GPT-5.6 Sol: request input ≤ 272,000 tokens) — about 75% less on a 1M-input + 1M-output mix. Both carry a 1.05M context window. Both answer on /v1/chat/completions and /v1/responses (Codex CLI). GPT-5.6 Sol (Azure) is the Azure sales channel of the same base model as GPT-5.6 Sol: a separately priced product with an isolated routing pool — requests never fall back to the default channel, and a plan quota covers it only when the live plan response lists the channel id. GPT-5.6 Sol (Azure) is in no plan and bills the wallet; GPT-5.6 Sol counts against the Premium models allowance on Pro, Max and Ultra.
GPT-5.6 Sol (Azure) and GPT-5.6 Sol compared on current per-token rates, context window, and capabilities — both callable through one OpenAI-compatible endpoint that logs each request it forwards.
GPT-5.6 Sol (Azure) vs GPT-5.6 Sol: rates, context window, and capabilities
| Spec | GPT-5.6 Sol (Azure) | GPT-5.6 Sol |
|---|---|---|
| Input / 1M tokens | $3.00 | $0.50 |
| Output / 1M tokens | $15.00 | $4.00 |
| Cached input / 1M tokens | $0.30 | $0.25 |
| Context window | 1.05M | 1.05M |
| Capabilities | Chat, Streaming, Tool calling, Vision | Chat, Streaming, Tool calling, Vision |
| Subscription plans | Not in any plan — wallet | Premium models — Pro, Max, Ultra |
| Detail page | GPT-5.6 Sol (Azure) | GPT-5.6 Sol |
GPT-5.6 Sol (Azure): request input ≤ 272,000 tokens: Input $3.00 / 1M tokens, Output $15.00 / 1M tokens, Cache write $3.75 / 1M tokens, Cached input $0.30 / 1M tokens; request input > 272,000 tokens: Input $6.00 / 1M tokens, Output $22.50 / 1M tokens, Cache write $7.50 / 1M tokens, Cached input $0.60 / 1M tokens. The total input tokens in each request select the tier; its rates apply to the whole request, not only tokens above the threshold.
GPT-5.6 Sol: request input ≤ 272,000 tokens: Input $0.50 / 1M tokens, Output $4.00 / 1M tokens, Cache write $0.50 / 1M tokens, Cached input $0.25 / 1M tokens; request input > 272,000 tokens: Input $1.00 / 1M tokens, Output $4.50 / 1M tokens, Cache write $6.25 / 1M tokens, Cached input $0.50 / 1M tokens. The total input tokens in each request select the tier; its rates apply to the whole request, not only tokens above the threshold.
What does 1M tokens cost on GPT-5.6 Sol (Azure) vs GPT-5.6 Sol?
Base-tier rates: For a workload of 1M input plus 1M output tokens at current rates: GPT-5.6 Sol (Azure) comes to $18.00, GPT-5.6 Sol comes to $4.50 — GPT-5.6 Sol is about 75% cheaper on this mix. Real workloads skew heavily toward input tokens, so weigh the input rate by your own ratio; the cached-input row above is the posted catalog rate for that model.
Switch between GPT-5.6 Sol (Azure) and GPT-5.6 Sol without changing code
Both models are behind the same OpenAI-compatible endpoint, so an A/B test is a one-string change — same key, same code, and every request traced in the dashboard with its tokens, the wallet charge or plan quota it used, and latency:
curl https://api.router.one/v1/chat/completions \
-H "Authorization: Bearer sk-your-router-one-key" \
-H "Content-Type: application/json" \
-d '{"model": "azure/gpt-5.6-sol", "messages": [{"role": "user", "content": "Hello"}]}'
# Same request, other model — change one string:
# "model": "openai/gpt-5.6-sol"FAQ
Is GPT-5.6 Sol (Azure) cheaper than GPT-5.6 Sol?
Compared at base-tier rates (GPT-5.6 Sol (Azure) and GPT-5.6 Sol: request input ≤ 272,000 tokens). Input: GPT-5.6 Sol (Azure) $3.00 vs GPT-5.6 Sol $0.50 / 1M tokens; GPT-5.6 Sol has the lower rate. Output: GPT-5.6 Sol (Azure) $15.00 vs GPT-5.6 Sol $4.00 / 1M tokens; GPT-5.6 Sol has the lower rate. Total cost depends on the workload's input, output and cache usage. GPT-5.6 Sol (Azure): request input ≤ 272,000 tokens: Input $3.00 / 1M tokens, Output $15.00 / 1M tokens, Cache write $3.75 / 1M tokens, Cached input $0.30 / 1M tokens; request input > 272,000 tokens: Input $6.00 / 1M tokens, Output $22.50 / 1M tokens, Cache write $7.50 / 1M tokens, Cached input $0.60 / 1M tokens. The total input tokens in each request select the tier; its rates apply to the whole request, not only tokens above the threshold. GPT-5.6 Sol: request input ≤ 272,000 tokens: Input $0.50 / 1M tokens, Output $4.00 / 1M tokens, Cache write $0.50 / 1M tokens, Cached input $0.25 / 1M tokens; request input > 272,000 tokens: Input $1.00 / 1M tokens, Output $4.50 / 1M tokens, Cache write $6.25 / 1M tokens, Cached input $0.50 / 1M tokens. The total input tokens in each request select the tier; its rates apply to the whole request, not only tokens above the threshold. Rates change; the /models page is the live source of truth.
Is GPT-5.6 Sol (Azure) or GPT-5.6 Sol included in a Router One subscription?
GPT-5.6 Sol (Azure) is in no Router One plan, so every call bills the wallet per token. GPT-5.6 Sol counts against the Premium models allowance on Pro, Max and Ultra: Pro 300, Max 1,000 and Ultra 5,000 requests per 30-day cycle, shared by every model in that tier. GPT-5.6 Sol requests above its long-context threshold count as more than one quota request. Requests beyond a plan's allowance bill the wallet per token.
Can I switch between GPT-5.6 Sol (Azure) and GPT-5.6 Sol without changing code?
Yes. Both are served through the same OpenAI-compatible endpoint, so switching is changing the model string in the request — the key, base URL, and request shape stay identical.
Where do these numbers come from?
Specs and prices on this page render from the live Router One catalog — the same data as the /models page — and refresh with it. Pricing methodology is documented on /pricing-methodology. Rates on this page were read from the live catalog on 2026-11-11 (UTC) and refresh within the hour.