OpenAI · none caching
o1 Pro
o1 Pro on Zumik: live pricing, context, and caching, routable by id or alias through one OpenAI-compatible endpoint.
Specifications
At a glance.
| Provider | OpenAI |
| Family | o-series |
| Released | 2025-03 |
| License | Proprietary |
| Context window | 200K tokens |
| Max output | 100K tokens |
| Modalities | text, image |
| Tool calling | Yes |
| Reasoning mode | Yes |
| Caching | none |
| Batch discount | 50% off |
Measured by Zumik
What reuse looks like here.
Pricing, context, and capabilities for o1 Pro are live, but it is outside the flagship set Zumik benchmarks in depth, so measured reuse, capture, and warm TTFT are not shown yet. Run a workload estimate or route it by id to start collecting traces.
What you actually pay once caching works.
At a typical 55% prefix reuse, a million input tokens on o1 Pro effectively costs $150.00 instead of $150.00 - blending to roughly $262.50 with a 25% output share. Background work drops a further 50% on the batch tier.
Estimate it for your workloadRoute it directly by id, or let an alias pick it when it wins under policy.
Call it
Same OpenAI client, this model.
from openai import OpenAI
client = OpenAI(base_url="https://api.zumik.ai/v1", api_key="zk_live_...")
r = client.responses.create(
model="o1-pro",
input="Draft a fix for the failing test.",
)
print(r.usage.input_tokens_cached) # confirm reuseFrequently asked
o1 Pro, answered.
How much does o1 Pro cost?
o1 Pro is $150.00 per million input tokens and $600.00 per million output tokens through Zumik. Cache reads are $150.00 per million, a 0% discount on input.
What is o1 Pro's context window?
o1 Pro supports a 200K-token context window with up to 100K output tokens.
Does o1 Pro support prompt caching?
Yes. OpenAI uses Automatic prefix caching caching. In the Zumik corpus, o1 Pro shows a median cache capture of 78% on agent workloads.
Run o1 Pro with reuse measured.
Point an OpenAI client at Zumik and see exactly how much of this model's input you are reusing.