OpenAI
o1
Released 
December 2024

OpenAI
o1

OpenAI's reinforcement-learning reasoning model for multi-step math, science, and coding problems needing deliberate step-by-step thinking.

Modality:
Text
Image

Output Speed *

N/A
tok/s

Intelligence Index *

23.9
/ 100

Context Window *

200000
tokens

Input price

90
Anytoken

Output price

360
Anytoken
o1: OpenAI's Reasoning Model for Hard Multi-Step Problems o1 is OpenAI's reasoning model, trained with large-scale reinforcement learning to produce a long internal chain of thought before answering. It is the production successor to o1-preview and sits at the reasoning-heavy end of OpenAI's lineup rather than the fast, general-purpose end. o1 spends inference-time compute planning responses, which materially improves accuracy on competition math, graduate-level science, and complex coding tasks. It supports text and image input, function calling, and structured outputs. The workload that benefits most is deliberate, correctness-critical problem solving where latency is acceptable in exchange for better reasoning. Start building with the o1 API on AnyAPI.ai

Performance

Where o1's Test-Time Reasoning Actually Pays Off

o1 is strongest on problems that reward deliberate, multi-step reasoning rather than fast recall. OpenAI reports it averaged 74% on the 2024 AIME with a single sample per problem, versus roughly 12% for GPT-4o, and it reaches PhD-level accuracy on the GPQA science benchmark. The reason is architectural: o1 generates an internal chain of thought and spends inference-time compute planning before answering. For production, this means o1 raises correctness on math-heavy, scientific, and algorithmic coding tasks, but each request consumes hidden reasoning tokens and takes noticeably longer, so it fits accuracy-critical steps rather than high-throughput serving.

Benchmarks

o1 on Independent Reasoning and Science Benchmarks

Independent and OpenAI-published evaluations position o1 as a reasoning specialist. On competitive programming, o1 ranks in roughly the 89th percentile on Codeforces, and it exceeds human PhD-level accuracy on GPQA physics, biology, and chemistry questions. Independent case studies of practical software work show a split picture: o1 achieves new state-of-the-art results on single-task web-app generation, unlocking problems non-reasoning models failed, but underperforms some non-reasoning frontier models on certain multi-task formats. Treat o1 as excellent for well-scoped reasoning and less predictable on loosely specified, format-sensitive tasks.

Output Speed

*
N/A
tok/s

Intelligence Index

*
23.9
/ 100

MMLU *

Broad world knowledge and problem-solving
84
%

GPQA *

PhD-level scientific reasoning across physics, biology, chemistry.
75
%

HLE *

Adherence to multi-step structured instructions.
7
%

LiveCodeBench *

Tool-calling reliability in long agentic loops.
68
%

Technical Specifications

What the model supports

o1 provides a 200,000-token context window and can generate up to 100,000 output tokens, but that output budget includes invisible reasoning tokens the model uses to think, so usable visible output is smaller than the cap suggests. It accepts text and image input and returns text only. Production features include function calling, structured outputs against a JSON Schema, and developer messages. Managing max_completion_tokens is essential to avoid truncated answers and runaway reasoning cost. Knowledge is current to October 2023, so time-sensitive facts require retrieval augmentation.
Verified Specifications — 
o1
*
Input modalities
Text
Image
output modalities
Text
Context window
200000
 tokens
Maximum output tokens
100000
Reasoning
No
Knowledge cutoff
December 2024
Pricing (standard)
90
 AnyTokens in
 / 
360
 AnyTokens out

Quickstart

Sample code for o1

import requestsurl = "https://api.anyapi.ai/v1/chat/completions"

payload = {
  "model": "o1",
  "messages": [
    {
    "role": "user",
    "content": [
        {
          "type": "text",
          "text": "Text prompt"
        },
        {
          "image_url": {
          "url": "https://upload.wikimedia.org/wikipedia/commons/thumb/d/dd/Gfp-wisconsin-madison-the-nature-boardwalk.jpg/2560px-Gfp-wisconsin-madison-the-nature-boardwalk.jpg"
       	 },
       	 "type": "image_url"
        }
      ]
    }
  ]
}
headers = {
"Authorization": "Bearer  AnyAPI_API_KEY",
"Content-Type": "application/json"
}

response = requests.post(url, json=payload, headers=headers)
print(response.json())
import requestsurl = "https://api.anyapi.ai/v1/chat/completions"payload = { "model": "o1", "messages": [ { "role": "user", "content": [ { "type": "text", "text": "Text prompt" }, { "image_url": { "url": "https://upload.wikimedia.org/wikipedia/commons/thumb/d/dd/Gfp-wisconsin-madison-the-nature-boardwalk.jpg/2560px-Gfp-wisconsin-madison-the-nature-boardwalk.jpg" }, "type": "image_url" } ] } ]}headers = { "Authorization": "Bearer AnyAPI_API_KEY", "Content-Type": "application/json"}response = requests.post(url, json=payload, headers=headers)print(response.json())‍
View docs
Copy
Code is copied
const url = 'https://api.anyapi.ai/v1/chat/completions';
const options = {  
  method: 'POST',  
  headers: {
    Authorization: 'Bearer  AnyAPI_API_KEY', 
    'Content-Type': 'application/json'
  },
  body: '{
    "model":"o1",
    "messages": [
      {
      "role":"user",
      "content":[
        {
          "type":"text",
          "text":"Text prompt"
        },
        {
          "image_url":{
            "url":"https://upload.wikimedia.org/wikipedia/commons/thumb/d/dd/Gfp-wisconsin-madison-the-nature-boardwalk.jpg/2560px-Gfp-wisconsin-madison-the-nature-boardwalk.jpg"
            },
            "type":"image_url"
          }
        ]
      }
    ]
  }'
};
try {  
	const response = await fetch(url, options);  
	const data = await response.json();  
	console.log(data);} 
catch (error) {  
	console.error(error);
}
const url = 'https://api.anyapi.ai/v1/chat/completions'; const options = { method: 'POST', headers: {Authorization: 'Bearer AnyAPI_API_KEY', 'Content-Type': 'application/json'}, body: '{"model":"o1","messages":[{"role":"user","content":[{"type":"text","text":"Text prompt"},{"image_url":{"url":"https://upload.wikimedia.org/wikipedia/commons/thumb/d/dd/Gfp-wisconsin-madison-the-nature-boardwalk.jpg/2560px-Gfp-wisconsin-madison-the-nature-boardwalk.jpg"},"type":"image_url"}]}]}' }; try { const response = await fetch(url, options); const data = await response.json(); console.log(data); } catch (error) { console.error(error); }
View docs
Copy
Code is copied
curl --request POST \  
  --url https://api.anyapi.ai/v1/chat/completions \  
  --header 'Authorization: Bearer  AnyAPI_API_KEY' \  
  --header 'Content-Type: application/json' \  
  --data '{  
    "model": "o1",  
    "messages": [    
      {      
      "role": "user",     
      "content": [      
        {        
          "type": "text",      
          "text": "Text prompt"  
        },      
          {    
          "image_url": {     
            "url": "https://upload.wikimedia.org/wikipedia/commons/thumb/d/dd/Gfp-wisconsin-madison-the-nature-boardwalk.jpg/2560px-Gfp-wisconsin-madison-the-nature-boardwalk.jpg"  
            },      
            "type": "image_url"     
          }      
        ]   
      }  
    ]
  }'
curl --request POST \ --url https://api.anyapi.ai/v1/chat/completions \ --header 'Authorization: Bearer AnyAPI_API_KEY' \ --header 'Content-Type: application/json' \ --data '{ "model": "o1", "messages": [ { "role": "user", "content": [ { "type": "text", "text": "Text prompt" }, { "image_url": { "url": "https://upload.wikimedia.org/wikipedia/commons/thumb/d/dd/Gfp-wisconsin-madison-the-nature-boardwalk.jpg/2560px-Gfp-wisconsin-madison-the-nature-boardwalk.jpg" }, "type": "image_url" } ] } ]}'‍
View docs
Copy
Code is copied
View docs
Code examples coming soon...

Comparison

o1 vs GPT-4o: Reasoning Depth or Speed and Cost?

o1 and GPT-4o are both OpenAI flagship-class models, but they solve different problems. GPT-4o is a fast, general-purpose multimodal model tuned for low latency and high throughput. o1 is a reasoning model that trades speed for deliberate chain-of-thought accuracy. The gap is stark on hard reasoning: OpenAI reports o1 solving around 74% of 2024 AIME problems versus roughly 12% for GPT-4o. The practical decision is whether your workload needs step-by-step correctness on math, science, and complex code, or fast, cost-efficient responses at scale.

Dimension
o1
GPT-4o
Context window *
200000
tokens
128000
tokens
Output speed *
N/A
tok/s
135
tok/s
Intelligence Index *
23.9
9.4
Input pricing
90
AnyToken
15
AnyToken
Output pricing
360
AnyToken
60
AnyToken
Knowledge cutoff *
December 2024
May 2024

Choose o1 when accuracy on multi-step reasoning, competition math, graduate-level science, or algorithmically hard coding justifies higher latency and reasoning-token cost, and when responses can take seconds rather than being instant. Choose GPT-4o when you need low latency, high-volume serving, cheaper output, audio input/output, or general conversational and multimodal tasks where deep reasoning is unnecessary. Many production systems route only hard subtasks to o1 while GPT-4o handles the routine, latency-sensitive majority.

Limitations & Trade-offs

Where o1 falls short

1
High latency by design. o1 produces a long internal chain of thought before responding, so it is slower than non-reasoning models like GPT-4o. This makes it unsuitable for real-time chat, autocomplete, or interactive UIs where responses must feel instant. For those on-the-fly scenarios, a faster model is the better default; reserve o1 for asynchronous or tolerant-latency reasoning steps.
2
Reasoning tokens inflate output cost. o1's 100,000-token output cap includes invisible reasoning tokens that are billed but never shown. A short visible answer can still consume large hidden reasoning, making per-request cost harder to predict and long outputs comparatively expensive. Budget with max_completion_tokens and avoid o1 for high-volume generation where a cheaper model would suffice.
3
Text-only output and no audio. o1 accepts text and image input but returns only text. It does not generate images or audio and does not accept audio input, unlike GPT-4o's realtime and audio capabilities. Applications needing voice, speech, or generated media must pair o1 with other models rather than relying on it alone.
4
Unpredictable on loosely specified tasks. Independent software-engineering case studies found o1 sets new state-of-the-art on well-scoped single-task problems but can underperform non-reasoning models on certain multi-task or format-sensitive prompts. Its reasoning steps drive both successes and failures, so ambiguous or format-heavy tasks may need tighter specification or a different model.

Best-Fit Workloads

Where this model earns its place

01

Competition-Grade Math and Quantitative Reasoning


o1 excels at problems that reward stepwise deduction. OpenAI reports it averaged 74% on the 2024 AIME with a single sample, far above GPT-4o. This makes it well suited to quantitative analysis, algorithmic derivations, and financial or scientific modeling where a wrong intermediate step invalidates the answer. Because each request is slow and reasoning-heavy, run these as asynchronous jobs rather than interactive endpoints.

02

Graduate-Level Scientific Reasoning


o1 exceeds human PhD-level accuracy on the GPQA benchmark across physics, biology, and chemistry, and its image input lets it reason over diagrams and scientific figures. This suits research assistance, technical literature analysis, and complex domain question answering. Note the October 2023 knowledge cutoff: pair o1 with retrieval for current findings, and verify outputs in high-stakes scientific contexts.

03

Complex, Well-Specified Coding Tasks


o1 ranks near the 89th percentile on Codeforces and produces strong results on multi-step implementation tasks such as planning a project structure then generating full files. Function calling and structured outputs let it slot into agentic developer tooling. It performs best when requirements are explicit; ambiguous or heavily format-constrained tasks can produce inconsistent results, so keep specifications tight.

04

Reasoning Steps Inside Agentic Pipelines


With function calling and structured outputs, o1 fits as the deliberate reasoning node in an agent that also uses faster models for routine steps. Developers have used the o1 line for agentic applications in customer support, supply chain, and financial forecasting. Route only hard planning or verification subtasks to o1 to contain latency and cost while preserving accuracy where it matters.

Pricing in anytokens via AnyAPI
Input
90
Output
360
Cache write
Cache read
45

Integration

Access o1 via AnyAPI.ai

Access o1 through AnyAPI.ai using a unified API built for multi-model AI applications. Integrate o1 without maintaining a separate provider-specific connection, and keep the flexibility to test, switch, or combine models as your application requirements evolve.

01

One API integration

Access o1 and other AI models through the same API workflow instead of maintaining separate integrations for every provider.

02

Easy model switching

Test o1 against alternative models or switch models as your performance, capability, or cost requirements change without rebuilding your application around another provider API.

03

Flexible for production

Use o1 from experimentation through production while keeping your AI stack flexible as workloads, traffic, and model requirements evolve.

04

Multi-model applications

Use o1 for the workloads where it performs best and combine it with other models for tasks that require different capabilities, performance, or efficiency.

Frequently Asked Questions

Answers to common questions about integrating and using this AI model via AnyAPI.ai

o1 has a 200,000-token context window and can generate up to 100,000 output tokens. Importantly, that output budget includes invisible reasoning tokens the model uses to think, so the visible answer is smaller than the cap implies. Use max_completion_tokens to reserve enough room and avoid truncated responses.

o1 performs strongly on well-specified coding tasks, ranking near the 89th percentile on Codeforces and handling multi-step implementation and refactoring. It works best when requirements are explicit. Independent studies show it can be less predictable on ambiguous or format-sensitive multi-task prompts, so tight specifications improve results.

Yes. o1 accepts both text and image input, letting it reason over diagrams, figures, and other visual content in science, manufacturing, and coding contexts. However, o1 returns text only and does not generate images or audio, and it does not accept audio input.

o1 is the production successor to o1-preview. The o1-2024-12-17 snapshot is a post-trained version released for developers with production features o1-preview lacked, including function calling, structured outputs, developer messages, and vision input. It targets real-world use cases beyond the earlier preview.

o1 generates a long internal chain of thought before responding, spending inference-time compute to plan its answer. This deliberate reasoning improves accuracy on hard problems but adds latency, making o1 unsuitable for real-time interactions. For fast, high-volume responses, GPT-4o or another non-reasoning model is a better fit.

* Benchmark data source: Artificial Analysis artificialanalysis.ai