SpyBara
Go Premium

Documentation 2026-08-28 18:00 UTC to 2026-08-31 23:00 UTC

10 files changed +46 −19. View all changes and history on the product overview
2026
Mon 31 23:00 Fri 28 18:00 Thu 27 22:01 Wed 26 22:57 Tue 25 18:59 Mon 24 22:00 Fri 21 19:59 Thu 20 23:59 Wed 19 18:02 Tue 18 04:58 Mon 17 22:57 Sat 15 01:01 Fri 14 20:01 Thu 13 22:00 Wed 12 02:57 Tue 11 19:59 Mon 10 19:00 Fri 7 00:58 Thu 6 21:58 Wed 5 18:01 Tue 4 22:59 Mon 3 18:01

deprecations.md +14 −1

Details

34 34 

35Upcoming deprecations are listed below, with the most recent announcements at the top.35Upcoming deprecations are listed below, with the most recent announcements at the top.

36 36 

37### 2026-08-26: Transcription models

38 

39On August 26, 2026, we notified developers using `whisper-1`, `gpt-4o-transcribe`, `gpt-4o-mini-transcribe`, and `gpt-4o-transcribe-diarize` of their deprecation and removal from the API on February 26, 2027.

40 

41For information about the recommended replacements, see the [transcription guide](https://developers.openai.com/api/docs/guides/transcription).

42 

43| Shutdown date | Model / system | Recommended replacement |

44| ------------- | --------------------------- | ----------------------------------------- |

45| Feb 26, 2027 | `whisper-1` | `gpt-live-transcribe` or `gpt-transcribe` |

46| Feb 26, 2027 | `gpt-4o-transcribe` | `gpt-live-transcribe` or `gpt-transcribe` |

47| Feb 26, 2027 | `gpt-4o-mini-transcribe` | `gpt-live-transcribe` or `gpt-transcribe` |

48| Feb 26, 2027 | `gpt-4o-transcribe-diarize` | `gpt-live-transcribe` or `gpt-transcribe` |

49 

37### 2026-07-20: Legacy audio, realtime, and transcription models50### 2026-07-20: Legacy audio, realtime, and transcription models

38 51 

39On July 20, 2026, we notified developers using legacy audio, realtime, and transcription model families and snapshots of their deprecation and removal from the API on January 20, 2027.52On July 20, 2026, we notified developers using legacy audio, realtime, and transcription model families and snapshots of their deprecation and removal from the API on January 20, 2027.


270 283 

271### 2025-08-20: Assistants API284### 2025-08-20: Assistants API

272 285 

273The Assistants API was officially sunset on August 26, 2026, following its deprecation announcement on August 26, 2025.286On August 26th, 2025, we notified developers using the Assistants API of its deprecation and removal from the API one year later, on August 26, 2026.

274 287 

275When we released the [Responses API](https://developers.openai.com/api/reference/resources/responses/methods/create) in [March 2025](https://developers.openai.com/api/docs/changelog), we announced plans to bring all Assistants API features to the easier to use Responses API, with a sunset date in 2026.288When we released the [Responses API](https://developers.openai.com/api/reference/resources/responses/methods/create) in [March 2025](https://developers.openai.com/api/docs/changelog), we announced plans to bring all Assistants API features to the easier to use Responses API, with a sunset date in 2026.

276 289 

Details

1463## Set image detail intentionally1463## Set image detail intentionally

1464 1464 

1465On GPT-5.6 models, omitted image `detail` and `detail: "auto"` use the same1465On GPT-5.6 models, omitted image `detail` and `detail: "auto"` use the same

1466sizing behavior as `original`. The service preserves the input dimensions1466sizing behavior as `original`. The service preserves the input dimensions,

1467instead of resizing the image to a patch budget or pixel-dimension limit. Large1467except that images larger than 65,535 pixels on either side are scaled down to

1468images can use more input tokens and add latency as a result.1468fit that limit. The API rejects images that still exceed the

1469[30,000-patch limit](https://developers.openai.com/api/docs/guides/images-vision#image-input-requirements),

1470rather than resizing them to fit it. Large images can use more input tokens and

1471add latency as a result.

1469 1472 

1470Choose [`detail`](https://developers.openai.com/api/docs/guides/images-vision#choose-an-image-detail-level)1473Choose [`detail`](https://developers.openai.com/api/docs/guides/images-vision#choose-an-image-detail-level)

1471for the task. Resize the image, use `low` when fine visual detail is not1474for the task. Resize the image, use `low` when fine visual detail is not

Details

111. Select the vision model you plan to use.111. Select the vision model you plan to use.

122. Enter the original image width and height in pixels. The calculator applies the model's resizing rules.122. Enter the original image width and height in pixels. The calculator applies the model's resizing rules.

133. Select an image detail level supported by the model.133. Select an image detail level supported by the model.

144. Read the image input tokens and estimated cost. Expand **Calculation details** to see the resized dimensions and token calculation.144. Read the image input tokens and estimated cost. If the processed image exceeds the [30,000-patch limit](https://developers.openai.com/api/docs/guides/images-vision#image-input-requirements), the calculator shows a rejection message instead of an estimate. Expand **Calculation details** to see the resized dimensions and token calculation.

15 

16For example, a 6000 × 6000 image on GPT-5.6 exceeds the limit with `original` detail (35,344 patches), but fits after resizing with `high` detail (2,500 patches). Choose `high` only when your task does not require original resolution or precise image coordinates.

15 17 

16## Understand the estimate18## Understand the estimate

17 19 

Details

969| Request size | Up to 512 MB total payload per request |969| Request size | Up to 512 MB total payload per request |

970| Image count | Up to 1,500 images per request |970| Image count | Up to 1,500 images per request |

971 971 

972For [patch-based image inputs](#patch-based-image-tokenization), the API supports up to 30,000 patches per image after applying the resizing rules for the selected model and `detail` level. This limit applies across supported detail levels and to each image separately, not to the combined patch count of the request.

973 

974Lower model- and detail-specific resizing budgets still apply. Images that exceed the 30,000-patch limit after processing are rejected, not automatically resized to meet it. Reduce the image's dimensions and try again.

975 

972Image tokens and the rest of your prompt must also fit the model's input and context limits. A token estimate does not guarantee that a request meets every input limit. Image use must comply with our [usage policies](https://openai.com/policies/usage-policies/).976Image tokens and the rest of your prompt must also fit the model's input and context limits. A token estimate does not guarantee that a request meets every input limit. Image use must comply with our [usage policies](https://openai.com/policies/usage-policies/).

973 977 

974### Choose an image detail level978### Choose an image detail level


997| `original` | Large, dense, spatially sensitive, or computer-use images, when supported by the model. |1001| `original` | Large, dense, spatially sensitive, or computer-use images, when supported by the model. |

998| `auto` | Use the model's default sizing behavior, shown in the model sizing table. |1002| `auto` | Use the model's default sizing behavior, shown in the model sizing table. |

999 1003 

1000For tasks that require fine visual detail or precise coordinates, such as optical character recognition (OCR), small-object detection, or computer use, use `"detail": "original"` when supported. Original detail can still resize images that exceed the model's limits. For coordinate-sensitive tasks, resize images to fit those limits before sending them and map returned coordinates back to the original image. See the [Computer use guide](https://developers.openai.com/api/docs/guides/tools-computer-use) for coordinate handling.1004For tasks that require fine visual detail or precise coordinates, such as optical character recognition (OCR), small-object detection, or computer use, use `"detail": "original"` when supported. Original detail can still resize images to meet the model's pixel-dimension limit or resizing patch budget, but not to meet the separate 30,000-patch rejection limit. For coordinate-sensitive tasks, resize images to fit those limits before sending them and map returned coordinates back to the original image. See the [Computer use guide](https://developers.openai.com/api/docs/guides/tools-computer-use) for coordinate handling.

1001 1005 

1002### Model sizing behavior1006### Model sizing behavior

1003 1007 


1020 </td>1024 </td>

1021 <td>1025 <td>

1022 `low` fits within 512 × 512 pixels. `high` fits1026 `low` fits within 512 × 512 pixels. `high` fits

1023 within 2048 × 2048 pixels and 2,500 patches. `original` fits1027 within 2048 × 2048 pixels and 2,500 patches. `original`

1024 within 65,535 × 65,535 pixels, with no patch-budget limit. 1028 preserves the image's dimensions, except that images larger than 65,535

1029 pixels on either side are scaled down to fit that limit. If the resulting

1030 image requires more than

1031 [30,000 patches](#image-input-requirements), the API rejects

1032 the request; the image is not resized to fit the patch limit.

1025 `auto` uses the same sizing behavior as `original`.1033 `auto` uses the same sizing behavior as `original`.

1026 </td>1034 </td>

1027 </tr>1035 </tr>


1099 1107 

1100### Patch-based image tokenization1108### Patch-based image tokenization

1101 1109 

1102Some models tokenize images by covering them with 32px x 32px patches. Many model and detail-level combinations define a maximum patch budget. First, the API fits the image within the selected detail level's pixel-dimension limit, preserving aspect ratio and rounding to integer pixels without enlarging smaller images. The token cost is then determined as follows:1110Some models tokenize images by covering them with 32px x 32px patches. Many model and detail-level combinations define a resizing patch budget. First, the API fits the image within the selected detail level's pixel-dimension limit, preserving aspect ratio and rounding to integer pixels without enlarging smaller images. The token cost is then determined as follows:

1103 1111 

1104A. Compute how many 32px x 32px patches are needed to cover the image after applying the pixel-dimension limit. A patch may extend beyond the image boundary.1112A. Compute how many 32px x 32px patches are needed to cover the image after applying the pixel-dimension limit. A patch may extend beyond the image boundary.

1105 1113 


1107patch_count = ceil(width/32)×ceil(height/32)1115patch_count = ceil(width/32)×ceil(height/32)

1108```1116```

1109 1117 

1110GPT-5.6 Sol, Terra, and Luna have no patch-budget limit for `original` or `auto`. After applying their pixel-dimension limit, skip the patch-budget resizing step. Large images can therefore use more tokens than with earlier models; resize them before sending or select `low` or `high` to control token use.1118B. When the selected model and detail level specify a resizing patch budget, scale the image down proportionally if it exceeds that budget. Otherwise, skip this step. Adjust the scale to stay within budget after converting to integer pixel dimensions and computing patch coverage. Keep full precision until calculating the final dimensions.

1111 

1112B. When a patch budget applies and the image exceeds it, scale the image down proportionally. Adjust the scale to stay within budget after converting to integer pixel dimensions and computing patch coverage. Keep full precision until calculating the final dimensions.

1113 1119 

1114```1120```

1115shrink_factor = sqrt((32^2 * patch_budget) / (width * height))1121shrink_factor = sqrt((32^2 * patch_budget) / (width * height))


1125resized_patch_count = ceil(resized_width/32)×ceil(resized_height/32)1131resized_patch_count = ceil(resized_width/32)×ceil(resized_height/32)

1126```1132```

1127 1133 

1134If this count exceeds 30,000 patches, the API rejects the request. Check this limit before applying the token multiplier.

1135 

1128D. Multiply the patch count by the model's multiplier and round up to get the billable image input tokens. Apply the model's input price to those tokens once; the multiplier does not apply to other prompt tokens or to the price again.1136D. Multiply the patch count by the model's multiplier and round up to get the billable image input tokens. Apply the model's input price to those tokens once; the multiplier does not apply to other prompt tokens or to the price again.

1129 1137 

1130| Model | Multiplier |1138| Model | Multiplier |

Details

28- **Token efficiency:** GPT-5.6 reaches flagship-level performance with fewer output tokens.28- **Token efficiency:** GPT-5.6 reaches flagship-level performance with fewer output tokens.

29- **Frontend design:** GPT-5.6 creates more polished and usable websites and applications, with stronger layout, visual hierarchy, and design judgment.29- **Frontend design:** GPT-5.6 creates more polished and usable websites and applications, with stronger layout, visual hierarchy, and design judgment.

30- **Intent understanding:** GPT-5.6 can better infer the user's underlying goal and intended level of work from context, so you often do not need to prescribe every step. Continue to provide domain context, hard constraints, approval boundaries, and success criteria. Tell the model when an important ambiguity should trigger a question.30- **Intent understanding:** GPT-5.6 can better infer the user's underlying goal and intended level of work from context, so you often do not need to prescribe every step. Continue to provide domain context, hard constraints, approval boundaries, and success criteria. Tell the model when an important ambiguity should trigger a question.

31- **Original image detail:** GPT-5.6 preserves the original dimensions of images sent with `original` or `auto` detail instead of resizing them to a patch budget or pixel-dimension limit. Large images can use more input tokens and increase latency. Learn how to [choose an image detail level](https://developers.openai.com/api/docs/guides/images-vision#choose-an-image-detail-level).31- **Original image detail:** GPT-5.6 preserves image dimensions with `original` or `auto` detail, except that images larger than 65,535 pixels on either side are scaled down to fit that limit. The API rejects images that still exceed the [30,000-patch limit](https://developers.openai.com/api/docs/guides/images-vision#image-input-requirements), rather than resizing them to fit it. Large images can use more input tokens and increase latency. Learn how to [choose an image detail level](https://developers.openai.com/api/docs/guides/images-vision#choose-an-image-detail-level).

32 32 

33## Safeguards33## Safeguards

34 34 

Details

28- **Token efficiency:** GPT-5.6 reaches flagship-level performance with fewer output tokens.28- **Token efficiency:** GPT-5.6 reaches flagship-level performance with fewer output tokens.

29- **Frontend design:** GPT-5.6 creates more polished and usable websites and applications, with stronger layout, visual hierarchy, and design judgment.29- **Frontend design:** GPT-5.6 creates more polished and usable websites and applications, with stronger layout, visual hierarchy, and design judgment.

30- **Intent understanding:** GPT-5.6 can better infer the user's underlying goal and intended level of work from context, so you often do not need to prescribe every step. Continue to provide domain context, hard constraints, approval boundaries, and success criteria. Tell the model when an important ambiguity should trigger a question.30- **Intent understanding:** GPT-5.6 can better infer the user's underlying goal and intended level of work from context, so you often do not need to prescribe every step. Continue to provide domain context, hard constraints, approval boundaries, and success criteria. Tell the model when an important ambiguity should trigger a question.

31- **Original image detail:** GPT-5.6 preserves the original dimensions of images sent with `original` or `auto` detail instead of resizing them to a patch budget or pixel-dimension limit. Large images can use more input tokens and increase latency. Learn how to [choose an image detail level](https://developers.openai.com/api/docs/guides/images-vision#choose-an-image-detail-level).31- **Original image detail:** GPT-5.6 preserves image dimensions with `original` or `auto` detail, except that images larger than 65,535 pixels on either side are scaled down to fit that limit. The API rejects images that still exceed the [30,000-patch limit](https://developers.openai.com/api/docs/guides/images-vision#image-input-requirements), rather than resizing them to fit it. Large images can use more input tokens and increase latency. Learn how to [choose an image detail level](https://developers.openai.com/api/docs/guides/images-vision#choose-an-image-detail-level).

32 32 

33## Safeguards33## Safeguards

34 34 

Details

3351. The user speaks or sends text, and a response is created, either by your client or automatically by the session configuration.3351. The user speaks or sends text, and a response is created, either by your client or automatically by the session configuration.

3361. If the model chooses an MCP tool, you will see `response.mcp_call_arguments.delta` and `response.mcp_call_arguments.done`.3361. If the model chooses an MCP tool, you will see `response.mcp_call_arguments.delta` and `response.mcp_call_arguments.done`.

3371. **If approval is required**, the server adds a conversation item whose `item.type` is `mcp_approval_request`. Your client must answer it with an `mcp_approval_response` item.3371. **If approval is required**, the server adds a conversation item whose `item.type` is `mcp_approval_request`. Your client must answer it with an `mcp_approval_response` item.

3381. Once the tool runs, you will see `response.mcp_call.in_progress`. On success, you will later receive a [`response.output_item.done`](https://developers.openai.com/api/reference/resources/realtime) event whose `item.type` is `mcp_call`; on failure, you will receive [`response.mcp_call.failed`](https://developers.openai.com/api/reference/resources/realtime). The assistant message item and `response.done` complete the turn.3381. Once the tool runs, you will see `response.mcp_call.in_progress`. On success, you will later receive a [`response.output_item.done`](https://developers.openai.com/api/reference/resources/realtime) event whose `item.type` is `mcp_call`; on failure, you will receive [`response.mcp_call.failed`](https://developers.openai.com/api/reference/resources/realtime).

3391. `response.done` for a response can arrive before its MCP calls finish. After the response is done and all of its MCP calls have finished, send another [`response.create`](https://developers.openai.com/api/reference/resources/realtime) event to let the model use the results and proceed with the conversation. Repeat this step if the model makes additional MCP calls. The Realtime API doesn't create these follow-up responses automatically.

339 340 

340This event handler covers the main checkpoints:341This event handler logs the main MCP lifecycle events; it doesn't manage follow-up responses:

341 342 

342Listen for MCP events during a Realtime session343Listen for MCP events during a Realtime session

343 344 

Details

1670 1670 

1671Send that screenshot back as a `computer_call_output` item:1671Send that screenshot back as a `computer_call_output` item:

1672 1672 

1673For Computer use, prefer `detail: "original"` on screenshot inputs to preserve resolution and improve click accuracy. GPT-5.6 models do not resize `original` image inputs to a pixel-dimension or patch-budget limit, so large screenshots can use more input tokens. If `detail: "original"` uses too many tokens, you can downscale the image before sending it to the API, and make sure you remap model-generated coordinates from the downscaled coordinate space to the original image's coordinate space. Avoid using `high` or `low` image detail for computer use tasks. When downscaling, we observe strong performance with 1440x900 and 1600x900 desktop resolutions. See the [Images and Vision guide](https://developers.openai.com/api/docs/guides/images-vision) for more details on image input detail levels.1673For Computer use, prefer `detail: "original"` on screenshot inputs to preserve resolution and improve click accuracy. GPT-5.6 preserves screenshot dimensions, except that images larger than 65,535 pixels on either side are scaled down to fit that limit. The API rejects screenshots that still exceed the [30,000-patch limit](https://developers.openai.com/api/docs/guides/images-vision#image-input-requirements), rather than resizing them to fit it. If `detail: "original"` uses too many tokens or exceeds the limit, downscale the image before sending it to the API, and make sure you remap model-generated coordinates from the downscaled coordinate space to the original image's coordinate space. Avoid using `high` or `low` image detail for computer use tasks. When downscaling, we observe strong performance with 1440x900 and 1600x900 desktop resolutions. See the [Images and Vision guide](https://developers.openai.com/api/docs/guides/images-vision) for more details on image input detail levels.

1674 1674 

1675Send the updated screenshot1675Send the updated screenshot

1676 1676 

libraries.md +1 −1

Details

173<dependency>173<dependency>

174 <groupId>com.openai</groupId>174 <groupId>com.openai</groupId>

175 <artifactId>openai-java</artifactId>175 <artifactId>openai-java</artifactId>

176 <version>4.54.0</version>176 <version>4.55.0</version>

177</dependency>177</dependency>

178```178```

179 179 

quickstart.md +1 −1

Details

190<dependency>190<dependency>

191 <groupId>com.openai</groupId>191 <groupId>com.openai</groupId>

192 <artifactId>openai-java</artifactId>192 <artifactId>openai-java</artifactId>

193 <version>4.54.0</version>193 <version>4.55.0</version>

194</dependency>194</dependency>

195```195```

196 196