Model comparison
DeepSeek V3.1 vs GPT-5.2-Codex
Head-to-head evidence from 11 shared benchmark results across 5 categories. Overall scores shown here use the public BenchAlign v5 ranking lane.
Public leaderboard positions: DeepSeek V3.1 #95 (Supported); GPT-5.2-Codex #58 (Supported). Intervals and evidence labels describe ranking uncertainty, not a guarantee for a specific workload.
Evidence parity. DeepSeek V3.1 and GPT-5.2-Codex share 11 comparable benchmark results. 0 of 8 categories are comparable. 1 result is unique to DeepSeek V3.1; 4 to GPT-5.2-Codex.
Updated July 20, 2026- Shared results
- 11
- DeepSeek V3.1 only
- 1
- GPT-5.2-Codex only
- 4
- Comparable categories
- 0 / 8
Benchmark data for DeepSeek V3.1 and GPT-5.2-Codex is coming soon on BenchLM.
Confidence note. This is a partial-evidence comparison with 11 shared benchmark results across 5 evidence categories; 0 of 8 categories currently have scoreable aggregates for both models. Treat the verdict as directional until coverage is more balanced.
Why this result
BenchLM has partial data for these models, but not enough overlapping benchmark coverage to produce a fair score-level comparison yet.
GPT-5.2-Codex is priced at $1.75 input / $14.00 output per 1M tokens, versus $0.00 input / $0.00 output per 1M tokens for DeepSeek V3.1. GPT-5.2-Codex has the larger context window at 400K, compared with 128K for DeepSeek V3.1.
Category breakdown
Exact category averages are shown below. Not measured means BenchLM does not have enough sourced public coverage for that model and category.
Operational comparison
Runtime and commercial metrics are compared only when both models have a complete sourced value.
| Metric | DeepSeek V3.1 | GPT-5.2-Codex | Comparison |
|---|---|---|---|
| Input / output priceUSD per 1M tokens | DeepSeek V3.1$0 input / $0 output | GPT-5.2-Codex$1.75 input / $14 output | DeepSeek V3.1 has the lower combined listed price. |
| Generation speedtokens per second | DeepSeek V3.1Not available | GPT-5.2-Codex123 tok/s | A complete speed comparison is not available. |
| First-answer latencyseconds to first token | DeepSeek V3.1Not available | GPT-5.2-Codex87.34 s | A complete latency comparison is not available. |
| Context windowmaximum listed tokens | DeepSeek V3.1128K | GPT-5.2-Codex400K | GPT-5.2-Codex lists the larger context window. |
Benchmark Deep Dive
Agentic3 benchmarks
Coding2 benchmarks
Reasoning2 benchmarks
Knowledge6 benchmarks
| Benchmark | DeepSeek V3.1 | GPT-5.2-Codex | Result |
|---|---|---|---|
| Artificial Analysis Intelligence IndexSource | 21.1% | 40.1% | GPT-5.2-Codex leads |
| AA-GPQA DiamondSource | 73.5% | 89.9% | GPT-5.2-Codex leads |
| AA-HLESource | 6.3% | 33.5% | GPT-5.2-Codex leads |
| AA-Omniscience IndexSource | -41.1% | -2.5% | GPT-5.2-Codex leads |
| AA-Omniscience AccuracySource | 23.1% | 40.7% | GPT-5.2-Codex leads |
| AA-Omniscience Hallucination RateSource | 83.5% | 72.8% | GPT-5.2-Codex leads |
Multimodal2 benchmarks
Inst. Following1 benchmarks
| Benchmark | DeepSeek V3.1 | GPT-5.2-Codex | Result |
|---|---|---|---|
| AA-IFBenchSource | 37.8% | 77.6% | GPT-5.2-Codex leads |
Frequently Asked Questions (3)
Can I compare DeepSeek V3.1 and GPT-5.2-Codex on BenchLM yet?
Not fully yet. BenchLM is tracking both models, but the sourced benchmark breakdown for this comparison is still coming soon.
Why does this comparison show “coming soon”?
BenchLM only shows category winners and benchmark-level calls when we have sourced results that can be compared fairly. For these models, the public benchmark coverage is not complete enough yet.
What data is available for DeepSeek V3.1 and GPT-5.2-Codex today?
DeepSeek V3.1: $0.00 input / $0.00 output per 1M tokens GPT-5.2-Codex: $1.75 input / $14.00 output per 1M tokens Both model pages still include creator, context window, reasoning mode, and other metadata while benchmark coverage fills in.
Related Comparisons
Explore More
Choose a model with this week’s evidence
Join 2,000+ readers for ranking moves, pricing changes, and the claims that still need proof.
One email each week. Unsubscribe anytime.