•

Proprietary model

•

Released April 2025

o3 API Provider Benchmarking & Analysis

Model Comparison

This analysis is intended to support you in choosing the best API provider of o3 for your use-case.

Lowest Time per Task

Time per Intelligence Index task (minutes)

Total 2 providers

Lowest Cost per Task

Cost per Intelligence Index task

Total 2 providers

o3 is available through 2 API providers, each offering different performance characteristics and pricing. Below is a comparison of the key metrics across providers.

Time per Task

Inference time (minutes) per Intelligence Index task · Lower is better

No data available

Cost per Task

Weighted average cost (USD) per Intelligence Index task · Lower is better

No data available

Pricing

Cost per Intelligence Index Task: o3

Weighted average cost (USD) per Intelligence Index task · Segmented by token type · Lower is better

No data available

Weighted average cost per Intelligence Index task. Each evaluation’s cost is calculated from input, cache hit, cache write, reasoning, and answer token prices, divided by task count, and weighted by its Intelligence Index weight.

Pricing: Cache Hit, Input, and Output: o3

Price (USD per M Tokens) · Lower is better

Price per token for cached prompts (previously processed), typically offering a significant discount compared to regular input price, represented as USD per million tokens. The values shown here are the cache hit price; cache write and cache storage are billed separately and vary by provider — see "Cache pricing by provider" for detail.

Output Speed vs. Cost per Task: o3

Output speed: output tokens divided by total request time, including time to first token · Weighted average cost (USD) per Intelligence Index task

Most attractive quadrant

No data available

Output tokens, including reasoning tokens, received per second over a request's full duration, from sending the request to receiving the final token. The headline value averages each Performance v3 workload over the past 5 days, then averages the workloads.

Speed

Average of the single-request and multi-turn agentic workloads measured

Output Speed: o3

Output tokens divided by total request time · Includes time to first token · Average of the single-request and multi-turn agentic workloads measured · Higher is better

Speed and latency metrics average each endpoint's runs over the past 5 days, and the error rate pools them. We run the benchmark every 6 hours, and endpoints of deprecated models every 18 hours.

Latency

Average of the single-request and multi-turn agentic workloads measured

Time to First Answer Token: o3

Seconds until the first answer token after any reasoning · Average of the single-request and multi-turn agentic workloads measured · Lower is better

Time to first answer token received, in seconds, after API request sent. For reasoning models, this includes the 'thinking' time of the model before providing an answer. For models which do not support streaming, this represents time to receive the completion.

Speed and latency metrics average each endpoint's runs over the past 5 days, and the error rate pools them. We run the benchmark every 6 hours, and endpoints of deprecated models every 18 hours.

Reliability

Share of requests the endpoint failed, across all the single-request and multi-turn agentic workloads measured

Endpoint Error Rate: o3

Share of requests the endpoint failed with an error, a rate limit or a timeout · Across all the single-request and multi-turn agentic workloads measured · Lower is better

Share of requests over the past 5 days that the endpoint failed with an error, a rate limit or a timeout. Failures on our side are left out of both counts. Across several workloads, the failures and requests are pooled before dividing.

Speed and latency metrics average each endpoint's runs over the past 5 days, and the error rate pools them. We run the benchmark every 6 hours, and endpoints of deprecated models every 18 hours.

Caching

Cache Hit Rate: o3

Median across multi-turn agentic session runs in the last four weeks, updated Oct 26, 2026 · Higher is better

The share of cacheable input tokens served from the provider's prompt cache, measured during multi-turn agentic sessions. We regularly measure each endpoint and report a representative rate based on recent measurements. Higher values mean more of the input is billed at the cheaper cache-hit price, where the provider offers one, which lowers the effective cost of agentic workloads. For further details, see our methodology page.

Cost per Task vs. Cache Hit Rate: o3

Weighted average cost (USD) per Intelligence Index task · Cache hit rate: median of the last four weeks, updated Oct 26, 2026

Most attractive quadrant

No data available

Key Comparison Metrics & API Features



Microsoft Azure	--	--	20.75	0.0%	200k	Proprietary
OpenAI	--	--	8.95	0.0%	200k	Proprietary

Frequently Asked Questions

Common questions about o3 providers

o3 is available through 2 API providers: Azure and OpenAI. Each provider offers different performance characteristics and pricing.

o3 is currently available through 2 API providers that we benchmark and track.

The providers with the lowest time to first answer token for o3 are OpenAI (7.80s) and Azure (19.61s). Lower latency means faster initial response time.

The most affordable providers for o3 by blended price are Azure ($1.55 per 1M tokens) and OpenAI ($1.55 per 1M tokens). Blended price uses a 7:2:1 cache hit/input/output token ratio.

The providers with the lowest input token pricing for o3 are Azure ($2.00 per 1M input tokens) and OpenAI ($2.00 per 1M input tokens).

The providers with the lowest output token pricing for o3 are Azure ($8.00 per 1M output tokens) and OpenAI ($8.00 per 1M output tokens).

All 2 providers of o3 support JSON mode for structured output.

All 2 providers of o3 support function calling (tool use).

When choosing a provider for o3, consider: time per task (how quickly the provider completes an Intelligence Index task), latency (for interactive applications requiring quick first responses), pricing (for cost-sensitive workloads), and API features like JSON mode or function calling.

Yes, provider performance can vary over time due to infrastructure changes, load balancing, and updates. We continuously benchmark all providers and display historical performance trends in the "Over Time" charts.

For information about o3's intelligence, capabilities, modalities, and how it compares to other models, see the model overview page. View model overview

o3 API Provider Benchmarking & Analysis

Lowest Time per Task

Lowest Cost per Task

Time per Task

Cost per Task

Pricing

Cost per Intelligence Index Task: o3

Cost per Intelligence Index Task

Pricing: Cache Hit, Input, and Output: o3

Cache Hit

Output Speed vs. Cost per Task: o3

End-to-End Output Speed

Speed

Output Speed: o3

End-to-End Output Speed

Time Period

Latency

Time to First Answer Token: o3

Time to First Answer Token

Time Period

Reliability

Endpoint Error Rate: o3

Endpoint Error Rate

Time Period

Caching

Cache Hit Rate: o3

What Cache Hit Rate Shows

Cost per Task vs. Cache Hit Rate: o3

Cost per Intelligence Index Task

What Cache Hit Rate Shows

Key Comparison Metrics & API Features

Frequently Asked Questions

Where can I access o3?

How many API providers offer o3?

Which provider has the lowest latency for o3?

Which provider is cheapest for o3?

Which provider has the lowest input price for o3?

Which provider has the lowest output price for o3?

Which o3 providers support JSON mode?

Which o3 providers support function calling?

How do I choose a provider for o3?

Does provider performance for o3 change over time?

What are the overall capabilities of o3?