Skip to main content
Radar

Five or fewer confirmed AI changes, with original sources, on mornings when something changed.A free source-linked morning brief.

See the free Radar Brief
OpenAI logo
Model A
o1

OpenAI

47.89/100

Estimated · Public rank #154

90% interval 38.853.6

o1 vs o1-preview

Updated September 4, 2026. Public scores include evidence status and uncertainty. They are not guarantees for a specific workload. This is a same-family comparison, so migration details appear when the source data supports them.

OpenAI logo
Model B
o1-preview

OpenAI

47.79/100

Supported · Public rank #155

90% interval 31.564.1

Decision reading

The public evidence has no benchmark result shared by both models, so it does not support a quality verdict. Use the documented cost, context, and runtime rows instead.

0 results are shared. Category rows resting on Estimated evidence or different benchmark sets are marked directional and do not name a winner.

Share or export

Share on XLinkedInSocial cardCSVJSON

Which one for your work

Recommendations appear only when a shared evidence basis or an explicit operating constraint supports the call. Secondary and unsupported use cases stay disclosed below the initial list.

No workload recommendation clears the current evidence threshold.

Use the matched evidence, workload costs, and sourced specifications below instead of treating a point score as a universal answer.

Show secondary and unsupported calls
  • Coding work

    Code generation, repair, and software-engineering tasks

    Not enough matched evidence

    O1 and o1-preview are scored on Estimated evidence for coding, so the reading is directional rather than like-for-like.

    Confidence: limited

  • Agentic work

    Tool use, computer use, and multi-step task completion

    Not enough matched evidence

    O1 and o1-preview are not ranked on the public lane for agentic, so no winner is named for agentic.

    Confidence: limited

  • Long documents

    Prompts that approach the documented context limit

    No clear pick

    The documented context windows are equal.

    Confidence: documented

  • Chat turn cost

    1K fresh input + 500 output tokens

    No clear pick

    A complete comparable API-rate estimate is not available for both models.

    Confidence: listed-rates

  • Cache-heavy agent loop cost

    200K cached + 20K fresh input + 10K output tokens

    Not enough matched evidence

    The page does not recommend a cost winner because at least one model cannot fit the stated workload in one request. o1 does not fit this workload in one request. o1-preview does not fit this workload in one request. o1 has no published cached-input rate, so cached tokens use its listed input rate. o1-preview has no published cached-input rate, so cached tokens use its listed input rate.

    Confidence: rate-fallback

  • Repository review cost

    50K fresh input + 3K output tokens

    No clear pick

    A complete comparable API-rate estimate is not available for both models.

    Confidence: listed-rates

What is actually comparable

Shared results can support a head-to-head reading. Results present for only one model describe coverage, not superiority.

Shared results
0
o1 only
4
o1-preview only
0
Like-for-like categories
0 / 8

2 categories rest on Estimated evidence or different evidence sets. Those rows remain visible for coverage context but do not name a winner.

Category results, on a stated basis

Each row shows the public-lane category score for both models: the BenchAlign lane for agentic, coding, and knowledge, and the weighted public rows elsewhere, with the same rank each model page reports. A row is like-for-like only when both scores rest on Supported evidence or the same weighted set. Directional and not-comparable rows remain visible, but they never receive a winner.

Coding

Directional only
o1
46.1
Estimated · #101/183
o1-preview
45.8
Estimated · #104/183
Basis
BenchAlign lane · 0 vs 0 public rows
Reading
Directional only

Knowledge

Directional only
o1
46.6
Supported · #106/181
o1-preview
46.5
Estimated · #108/181
Basis
BenchAlign lane · 2 vs 0 public rows
Reading
Directional only

Agentic

Not comparable
o1
Not ranked
o1-preview
Not ranked
Basis
BenchAlign lane · 0 vs 0 public rows
Reading
Not comparable

Reasoning

Not comparable
o1
66.5
Unranked · 2 rankable rows
o1-preview
Not ranked
Basis
Provisional lane · 0 vs 0 weighted rows
Reading
Not comparable

Math

Not comparable
o1
32.6
Unranked · 1 rankable row
o1-preview
Not ranked
Basis
Provisional lane · 1 vs 0 weighted rows
Reading
Not comparable

Multilingual

Not comparable
o1
Not ranked
o1-preview
Not ranked
Basis
Provisional lane · 0 vs 0 weighted rows
Reading
Not comparable

Multimodal

Not comparable
o1
Not ranked
o1-preview
Not ranked
Basis
Provisional lane · 0 vs 0 weighted rows
Reading
Not comparable

Instruction following

Not comparable
o1
85.7
#39/120
o1-preview
Not ranked
Basis
Provisional lane · 0 vs 0 weighted rows
Reading
Not comparable

Ranks count the models scored in each category’s lane, so the agentic, coding, and knowledge denominators (BenchAlign) differ from the provisional-lane categories. Unranked scores sit on the lane’s scale but never name a winner. Like-for-like rows within 0.5 points read as a practical tie.

Shape of the matched evidence

Only shared public evidence is shown. Sparse evidence stays a ruled list rather than being closed into a radar shape.

A shared-evidence shape is not available.

BenchLM does not draw a radar or infer missing axes when the matched evidence is too sparse.

What each workload costs

Three fixed token mixes turn per-token rates into comparable decisions. Each scenario states context fit and whether cached input had to fall back to the published list-input rate.

Chat turn

1K fresh input + 500 output tokens

o1
$0.045
Fits in one request
o1-preview
$0.045
Fits in one request

Modeled costs are equal

Costs use the listed standard API rates.

Repository review

50K fresh input + 3K output tokens

o1
$0.93
Fits in one request
o1-preview
$0.93
Fits in one request

Modeled costs are equal

Costs use the listed standard API rates.

Cache-heavy agent loop

200K cached + 20K fresh input + 10K output tokens

o1
$3.90
Does not fit in one request
Cached input priced at the published list-input rate
o1-preview
$3.90
Does not fit in one request
Cached input priced at the published list-input rate

o1 does not fit this workload in one request. o1-preview does not fit this workload in one request. o1 has no published cached-input rate, so cached tokens use its listed input rate. o1-preview has no published cached-input rate, so cached tokens use its listed input rate.

Specification differences

Sourced differences are shown directly. Missing facts stay explicit instead of being inferred from a model name or family.

Context window

Maximum documented context; output-token limits may be lower.

o1

200K

o1-preview

200K

API model ID

o1

Not sourced

o1-preview

Not sourced

Cached-input rate

A missing cached-input rate falls back to the listed input rate only in the stated workload estimate.

o1

Not published

o1-preview

Not published

Documented inputs

o1

Not sourced

o1-preview

Not sourced

Documented outputs

o1

Not sourced

o1-preview

Not sourced

Provider availability

o1

Not sourced

o1-preview

Not sourced

Reasoning profile

o1

Reasoning

o1-preview

Reasoning

Weight access

o1

Proprietary

o1-preview

Proprietary

License

o1

Proprietary

o1-preview

Proprietary

Release date

o1

2024-12-01

o1-preview

2024-09-12

If you are considering the documented upgrade path
Deployment change
Both entries list OpenAI as the provider. Confirm endpoint, model ID, limits, and feature support before switching.
Quality signal
The public evidence has no benchmark result shared by both models, so it does not support a quality verdict.
Workload cost
Repository review: $0.93 vs $0.93. Cache-heavy agent loop: $3.90 vs $3.90.
Context tradeoff
Both models list 200K.

Run the same representative tasks against both endpoints before changing production traffic.

Benchmark evidence

The full public result ledger is available for audit without forcing a wide desktop table onto a phone.

Browse raw public benchmark evidence4 rows

Knowledge

  • MMLU

    o191.8%
    Source
    o1-preview

    Not directly comparable

  • GPQA

    o175.7%
    Source
    o1-preview

    Not directly comparable

Math

  • FrontierMath v2 (Tiers 1-3)

    o19.310%
    Source
    o1-preview

    Not directly comparable

Instruction following

  • IFEval

    o192.2%
    Source
    o1-preview

    Not directly comparable

Frequently asked questions

Which is better, o1 or o1-preview?

The public evidence has no benchmark result shared by both models, so it does not support a quality verdict. The page therefore keeps the decision tied to the specific documented workload.

Which is better for coding, o1 or o1-preview?

o1 scores higher for coding on the public lane, 46.1 to 45.8. O1 and o1-preview are scored on Estimated evidence for coding, so the reading is directional rather than like-for-like. BenchLM does not name a winner for coding from a directional reading; read the shared benchmark rows directly and test the models on the same task set.

Which is better for agentic tasks, o1 or o1-preview?

O1 and o1-preview are not ranked on the public lane for agentic tasks, so no winner is named for agentic tasks.

Which costs less, o1 or o1-preview?

For the stated presets, chat costs $0.045 on o1 and $0.045 on o1-preview; repository review costs $0.93 and $0.93; the cache-heavy agent loop costs $3.90 and $3.90. o1 does not fit this workload in one request. o1-preview does not fit this workload in one request. o1 has no published cached-input rate, so cached tokens use its listed input rate. o1-preview has no published cached-input rate, so cached tokens use its listed input rate.

Which has the larger context window, o1 or o1-preview?

Both models list the same context window, 200K.

Related comparisons

Last updated September 4, 2026

Watch o1 vs o1-preview

One weekly email when material rank, price, or benchmark evidence changes make this matchup worth revisiting.

Read a sample issue

Join 2,000+ readers.