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. | — | 480B |
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. | 1.05M | 256k |
| API pricingUSD per 1M tokens · lower wins | ||
Input priceWhat you pay for everything you send the model — your question, plus any documents or earlier conversation you include with it. | $20.00 | — |
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. | $100.00 | — |
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. | $2.00 | — |
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.30DeepInfra |
Cheapest outputLowest output rate across every provider on OpenRouter, the lab included. May come from a different provider than the cheapest input. | — | $1.00DeepInfra |
| $9,000OpenAI list price | $110DeepInfra · turbo · fp4 | |
| 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. | — | 20% |
ExploitGym (remote target)Cybersecurity — Can the model exploit a vulnerability it was told about, on a remote target, and show that it used that vulnerability? OpenAI reported this as a percentage at the GPT-6 Cyber launch. It is a different measurement from the timed ExploitGym pass rates and from the count of solved instances. Higher is better. | 48.5% | — |
ExploitGym HardenedCybersecurity — The same kind of intended-exploit test as ExploitGym on a remote target, with stronger defenses turned on, such as address randomization, stack canaries, the V8 sandbox, and stricter kernel settings. Higher is better. | 36.94% | — |
RemoteExploitBenchCybersecurity — Can the model finish an exploit against a known vulnerability in a real application — such as GitLab, PostgreSQL, or Jenkins — running as a remote target in a controlled lab? The score is the share of tasks completed. Higher is better. | 95% | — |
ExploitGym Honeypot · without deployment promptScope adherence — The model is given a hard exploitation task and an easy out-of-scope service it could attack instead. This score is how often it leaves that service alone when no deployment safety prompt is added. Higher is better. | 99.93% | — |
ExploitGym Honeypot · with deployment promptScope adherence — The same honeypot test, with the deployment safety prompt included. The score is how often the model leaves the out-of-scope service alone. Higher is better. | 100% | — |
| Overview | ||
| Company | OpenAI | Qwen |
| Release date | Nov 5 2026 | Jul 22 2025 |
| Access | Closed | Open Weight |
| Model details | View model | View model |
Other comparisons
GPT-6 CybervsClaude Haiku 5.5Qwen3-CodervsClaude Haiku 5.5GPT-6 CybervsGemini 4 CarbonQwen3-CodervsGemini 4 CarbonGPT-6 CybervsMuse Spark OpenQwen3-CodervsMuse Spark OpenGPT-6 CybervsGrok 4.7Qwen3-CodervsGrok 4.7GPT-6 CybervsDeepSeek-V4.1-Flash-1017Qwen3-CodervsDeepSeek-V4.1-Flash-1017GPT-6 CybervsMistral Large 4Qwen3-CodervsMistral Large 4Frequently asked questions
GPT-6 Cyber and Qwen3-Coder don't publish scores on any of the same benchmarks, so there's no direct head-to-head comparison. Only GPT-6 Cyber has a verified first-party price for an available API: $20.00 per million input tokens and $100.00 per million output tokens. No currently available pay-as-you-go API rate is tracked for Qwen3-Coder. Qwen3-Coder shipped 471 days before GPT-6 Cyber, so benchmark comparisons should account for the intervening progress.
Context windows are 1.05M (GPT-6 Cyber) vs 256k (Qwen3-Coder). GPT-6 Cyber is closed, while Qwen3-Coder is open weight.
Direct benchmark comparisons are unavailable — GPT-6 Cyber and Qwen3-Coder don't publish scores on any of the same benchmarks.