o1

Use the model ID o1 through the compatible chat completions endpoint. Note that o1 spends more time thinking before responding, which affects latency and cost.

For o1, set the max_tokens or max_completion_tokens parameter to control spending per call. Start with a budget aligned to your typical response length and increase only when longer outputs are genuinely needed. Monitor token usage in the API response headers to tune your budget over time.

Test your most demanding STEM and reasoning tasks. Account for the longer thinking time in your latency budget. Confirm the accuracy improvement justifies the cost for your specific use cases.

o1 is billed per use and the record publishes no free-tier allowance. The current published rates are input $15.0000 per 1M tokens and output $60.0000 per 1M tokens. Trial credit or promotional quota is tied to your account rather than to the model, so check the console before planning around a free tier.

o1 supports prompt caching, which can significantly reduce costs for repeated prompts with shared prefixes. The cache read price is substantially lower than the standard input price. Check the current pricing page for the exact cache hit discount ratio for o1.

To get a cache hit on o1, send requests with identical prompt prefixes. The cache is keyed by the beginning of your prompt; as long as the prefix matches a previous request, subsequent calls benefit from the lower cached rate. Keep system messages and initial context consistent across calls for best results.