o1-minivsQwen2
o1-mini | Qwen2 | |
|---|---|---|
| Specifications | ||
ParametersA rough measure of how big the model is. More parameters usually means more capable and more expensive to run, though it is a poor guide on its own — a smaller, newer model often beats a larger, older one. | — | 72B |
Context windowHow much text the model can hold in mind at once — your question, any documents you attach, the conversation so far, and its own reply. Go past it and the earliest part falls out of view. | 128k | 128k |
| 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. | $1.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. | $4.40 | — |
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.55 | — |
| BenchmarksPublished by one model only | ||
GPQA DiamondScience — Graduate-level science questions in biology, physics, and chemistry — hard enough that subject-matter PhDs score around 65%. Higher is better. | 60% | — |
| Overview | ||
| Company | OpenAI | Qwen |
| Release date | Sep 12 2024 | Jun 6 2024 |
| Access | Proprietary | Open Weight |
Other comparisons
Frequently asked questions
o1-mini and Qwen2 don't publish scores on any of the same benchmarks, so there's no direct head-to-head comparison. Only o1-mini has a verified first-party API price: $1.10 per million input tokens and $4.40 per million output tokens. No pay-as-you-go API rate is tracked for Qwen2. Qwen2 shipped 98 days before o1-mini, so benchmark comparisons should account for the intervening progress.
Context windows are 128k (o1-mini) vs 128k (Qwen2). o1-mini is proprietary, while Qwen2 is open weight.
Direct benchmark comparisons are unavailable — o1-mini and Qwen2 don't publish scores on any of the same benchmarks.