Compare AI models
| Specifications | ||
Context windowHow much information the model can work with in one request, measured in tokens — pieces of words or other data. This includes your question, attachments, conversation and reply. Limits can vary by model variant and provider. | 400k | 1.05M |
| API pricingUSD per 1M tokens · lower wins · base tier | ||
Input priceWhat you pay for everything you send the model — your question, plus any documents or earlier conversation you include with it. | $1.75 | $0.10 |
Output priceWhat you pay for the text the model writes back. It is normally the dearer half: producing an answer costs more than reading one. | $14.00 | $0.50 |
Cached input priceA reduced rate for text you send over and over. If every request starts with the same instructions or the same document, the provider keeps a copy ready and charges less to read it again. | $0.175 | $0.01 |
Cheapest inputLowest input rate across every provider on OpenRouter, the lab included. The cheapest endpoint may run a quantised build or a shorter context — see "Available from" on the model page. | $1.75Azure | $0.05OpenAI |
Cheapest outputLowest output rate across every provider on OpenRouter, the lab included. May come from a different provider than the cheapest input. | $14.00Azure | $0.25OpenAI |
| $1,050OpenAI list price | $45.00OpenAI list price | |
| Benchmarks | ||
BullshitBench v2Nonsense detection — Given a confidently-worded but nonsensical prompt, does the AI spot that it makes no sense and push back — instead of playing along and inventing an answer? The score is how often it clearly called out the nonsense. Higher is better. | 24% | 59% |
Next.js EvalsNext.js coding — Vercel's open eval of how well AI coding agents build and migrate real Next.js apps — measured as the share of tasks the agent completes successfully. Higher is better. | 68% | 86% |
threejsevalCommunity preference (Three.js) — Every model gets the same prompt — "the Eiffel Tower", "a glass fishbowl", "a robot arm picking toys into a box" — and builds a 3D scene in Three.js. Real people then see two scenes side by side, names hidden, and vote for the one they prefer. The votes become a chess-style Elo rating on threejseval.com, averaged across all the prompts. It measures whether the scene looks and moves right to a human eye, not whether the code passes a test. Higher is better. | 1153 | 1365 |
SWE-Bench VerifiedCoding — Real coding tasks pulled from open-source projects — the AI has to find and fix actual bugs. A human-checked version of the original SWE-Bench. Higher is better. | 85% | — |
DeepSWE 1.1Agentic coding — Artificial Analysis' independent test of deep, agentic software-engineering work — the AI has to plan and carry out substantial coding tasks end to end. (Version 1.1 of the test.) Higher is better. | — | 66.6% |
Supabase Evals · with skillsSupabase coding — Supabase's own open benchmark: a coding agent is dropped into a real Supabase project and asked to do real work — set up a schema, fix a broken security policy, debug an Edge Function — and every run is checked against a live Supabase stack. This is the headline number, where the agent has Supabase's own skills loaded, as most people building on Supabase would. The score is the share of scenarios it got right. Higher is better. | — | 75.4% |
Supabase Evals · no skillsSupabase coding — The same Supabase scenarios, but with none of Supabase's skills loaded — so it measures what the model already knows about building on Supabase, rather than how well it follows Supabase's supplied instructions. Higher is better. | — | 63.8% |
Terminal-Bench 4.0Agentic terminal coding — Can the AI work in a command-line terminal — running commands and finishing technical setup tasks the way a developer would? Version 4.0 recalibrated how much time, CPU and memory each task gets, removed eight tasks and fixed nineteen, so fewer runs fail for reasons that have nothing to do with the model. Scores are not comparable with earlier versions. Higher is better. | — | 16.36% |
ARC-AGI-2Abstract reasoning — Puzzle-style tests of abstract reasoning and pattern-finding — the kind of thing people find easy but AIs often struggle with. Higher is better. | — | 59.3% |
OSWorld-VerifiedAgentic computer use — Can the AI actually operate a computer — clicking, typing, and using real apps — to finish tasks on its own? Higher is better. | 64.7% | — |
| Overview | ||
| Company | OpenAI | OpenAI |
| Release date | Feb 5 2026 | Sep 22 2026 |
| Access | Closed | Closed |
| Model details | View model | View model |
Other comparisons
GPT-5.3-CodexvsClaude Haiku 5.5GPT-6 LunavsClaude Haiku 5.5GPT-5.3-CodexvsGemini 4 CarbonGPT-6 LunavsGemini 4 CarbonGPT-5.3-CodexvsMuse Spark OpenGPT-6 LunavsMuse Spark OpenGPT-5.3-CodexvsGrok 4.7GPT-6 LunavsGrok 4.7GPT-5.3-CodexvsDeepSeek-V4.1-Flash-1017GPT-6 LunavsDeepSeek-V4.1-Flash-1017GPT-5.3-CodexvsMistral Large 4GPT-6 LunavsMistral Large 4Frequently asked questions
GPT-6 Luna leads GPT-5.3-Codex on 3 of the 3 benchmarks they both report (BullshitBench v2, Next.js Evals, threejseval). GPT-6 Luna is cheaper on both input and output: $0.10 vs $1.75 per million input tokens, and $0.50 vs $14.00 per million output tokens. Figures are base-tier rates. GPT-5.3-Codex shipped 229 days before GPT-6 Luna, so benchmark comparisons should account for the intervening progress.
Context windows are 400k (GPT-5.3-Codex) vs 1.05M (GPT-6 Luna).
On BullshitBench v2, GPT-6 Luna leads at 59% vs GPT-5.3-Codex at 24%. On Next.js Evals, GPT-6 Luna leads at 86% vs GPT-5.3-Codex at 68%. On threejseval, GPT-6 Luna leads at 1365 vs GPT-5.3-Codex at 1153.