Skip to content

OpenAI Developers Detail Background API Pricing and Queue Priority for Completion Window Settings

2 reports 1 reporting sources first reported Updated 19 hours ago

Understand the event

AI overview

OpenAI Developers introduced completion_window settings for their Background API, allowing users to reduce costs by scheduling response times. Users can set the completion_window parameter to "2h" for 30% less per token than Standard pricing, or "8h" to save 40% per token. These settings provide the API an extended window to process inputs, such as generating a morning brief from meeting notes submitted the previous evening. Additionally, OpenAI Developers advises users to include a "continuation ID" when submitting initial notes and to reuse that same identifier on subsequent follow-up requests to receive higher queue priority.

Generated by AI from reports · Updated 18 hours ago

Read next

More changes in today’s briefingGoogle DeepMind Introduces Gemini 4 Neon for Coding, Analysis, and Science

Report timeline

Follow the reports to explore different sides of the event.

11/19
  1. OpenAI Shares Background API Settings for Lower Per-Token Prices

    OpenAI Developers says setting `completion_window` to `2h` costs 30% less per token than Standard, while `8h` costs 40% less. It also advises setting a continuation ID when sending notes and reusing it in follow-up requests to get higher queue priority. The post links to the Background API guide.

  2. Here’s one example: send your meeting notes before you log off and ask for a morning brief. Set "completion_window" to "8h" to give the API an eight-hour window for the first response.

    Here’s one example: send your meeting notes before you log off and ask for a morning brief. Set "completion_window" to "8h" to give the API an eight-hour window for the first response.

Keep up with AI, one email a day

Model releases, price changes and compute developments, with original sources. Free, confirmed by email, and easy to unsubscribe. Read a past issue

Event heat trend

Current within comparable coverage
6
Peak within comparable coverage
1011/19 08:00 (UTC+8)
24-hour change
–

Trends compare the same continuously observed participants, which may cover fewer sources than current heat. Point or click to inspect hourly heat, or use left and right arrow keys.