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. | 671B | — |
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 | 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. | — | $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. | — | $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.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. | $0.27SiliconFlow | $0.05OpenAI |
Cheapest outputLowest output rate across every provider on OpenRouter, the lab included. May come from a different provider than the cheapest input. | $1.00SiliconFlow | $0.25OpenAI |
| $104SiliconFlow · fp8 | $45.00OpenAI list price | |
| 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. | — | 59% |
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. | 68.4% | — |
SWE-Bench MultilingualMultilingual coding — Like SWE-Bench, but the coding problems span many programming languages, not just one. Tests how broadly the AI can code. Higher is better. | 57.8% | — |
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% |
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. | — | 77% |
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% |
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. | 74.9% | — |
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% |
GPQA DiamondScience — Graduate-level science questions in biology, physics, and chemistry — hard enough that subject-matter PhDs score around 65%. Higher is better. | 80.7% | — |
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. | — | 1383 |
| Overview | ||
| Company | DeepSeek | OpenAI |
| Release date | Sep 22 2025 | Sep 22 2026 |
| Access | Open Weight | Closed |
| Model details | View model | View model |
Other comparisons
DeepSeek V3.1 TerminusvsClaude Haiku 5.5GPT-6 LunavsClaude Haiku 5.5DeepSeek V3.1 TerminusvsGemini 4 ArgonGPT-6 LunavsGemini 4 ArgonDeepSeek V3.1 TerminusvsMuse Spark OpenGPT-6 LunavsMuse Spark OpenDeepSeek V3.1 TerminusvsGrok 4.7GPT-6 LunavsGrok 4.7DeepSeek V3.1 TerminusvsMistral Large 4GPT-6 LunavsMistral Large 4DeepSeek V3.1 TerminusvsKimi K3GPT-6 LunavsKimi K3Frequently asked questions
DeepSeek V3.1 Terminus and GPT-6 Luna don't publish scores on any of the same benchmarks, so there's no direct head-to-head comparison. Only GPT-6 Luna has a verified first-party API price: $0.10 per million input tokens and $0.50 per million output tokens. No pay-as-you-go API rate is tracked for DeepSeek V3.1 Terminus. DeepSeek V3.1 Terminus shipped 365 days before GPT-6 Luna, so benchmark comparisons should account for the intervening progress.
Context windows are 128k (DeepSeek V3.1 Terminus) vs 1.05M (GPT-6 Luna). DeepSeek V3.1 Terminus is open weight, while GPT-6 Luna is closed.
Direct benchmark comparisons are unavailable — DeepSeek V3.1 Terminus and GPT-6 Luna don't publish scores on any of the same benchmarks.