Compare AI models
| Specifications | ||
ParametersThe learned values that shape how a model responds. B means billion and T means trillion. For mixture-of-experts models, the total count is larger than the number active for each token. Parameter count alone does not measure quality. | 236B | — |
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. | 128k | 400k |
| API pricingUSD per 1M tokens · lower wins | ||
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 |
Cheapest outputLowest output rate across every provider on OpenRouter, the lab included. May come from a different provider than the cheapest input. | — | $14.00Azure |
| — | $1,050Azure | |
| These models have no shared benchmark scores. | ||
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. | — | 45% |
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. | 19% | — |
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. | — | 46% |
LiveCodeBenchCompetitive coding — Coding problems published so recently the AI can't have seen them in training — a contamination-free test of raw programming skill. Higher is better. | 39.7% | — |
HumanEvalFunction synthesis — 164 small Python problems: the AI is given a function's description and has to write the working function. This was the coding benchmark of the GPT-3.5 and GPT-4 era, before the field moved to fixing real bugs in real repositories. Higher is better. | 87.2% | — |
| Overview | ||
| Company | DeepSeek | OpenAI |
| Release date | Jul 24 2024 | Dec 18 2025 |
| Access | Open Weight | Closed |
| Model details | View model | View model |
Other comparisons
DeepSeek Coder V2-0724vsClaude Fable 5.2GPT-5.2-CodexvsClaude Fable 5.2DeepSeek Coder V2-0724vsGemini 4 HydrogenGPT-5.2-CodexvsGemini 4 HydrogenDeepSeek Coder V2-0724vsMuse EmberGPT-5.2-CodexvsMuse EmberDeepSeek Coder V2-0724vsGrok 4.7GPT-5.2-CodexvsGrok 4.7DeepSeek Coder V2-0724vsMistral Large 4GPT-5.2-CodexvsMistral Large 4DeepSeek Coder V2-0724vsKimi K3.1 ProGPT-5.2-CodexvsKimi K3.1 ProFrequently asked questions
DeepSeek Coder V2-0724 and GPT-5.2-Codex don't publish scores on any of the same benchmarks, so there's no direct head-to-head comparison. DeepSeek Coder V2-0724 shipped 512 days before GPT-5.2-Codex, so benchmark comparisons should account for the intervening progress.
Context windows are 128k (DeepSeek Coder V2-0724) vs 400k (GPT-5.2-Codex). DeepSeek Coder V2-0724 is open weight, while GPT-5.2-Codex is closed.
Direct benchmark comparisons are unavailable — DeepSeek Coder V2-0724 and GPT-5.2-Codex don't publish scores on any of the same benchmarks.