Skip to main content
gpt-image-2.5-flare-vip and gpt-image-2.5-sunburst-vip are both available again. If you paused requests during the outage, you can resume using a Default-group per-call token. Switching back from an alternative route is optional.
  • Published: September 22, 2026
  • Last checked: September 22, 2026
  • Status: Restored, as confirmed by LaoZhang API operations

Which models are restored?

This update covers the two VIP models affected by the September 16 upstream capacity shortage. Users who paused these models or moved to another route can now resume VIP requests. Users of other model IDs do not need to change their configuration because of this recovery.

Resume requests or switch back

  1. Check your token. In token management, select a Default-group per-call token and confirm that its model permissions include the VIP model you want to use.
  2. Set the full model ID. For an existing VIP integration, use your original gpt-image-2.5-flare-vip or gpt-image-2.5-sunburst-vip ID. If you are switching from official forwarding, change both the token and the model ID: the target ID must end in -vip. Check the current model price before sending requests.
  3. Use the VIP examples. The GPT Image 2.5 integration guide includes image generation with /v1/images/generations and image editing with /v1/images/edits. Follow the per-call examples for your operation and parameters.
  4. Check one request before restarting batches. Open the returned image and confirm that it meets your request. Then review the model, token group, and charge in call logs.

Frequently asked questions

Do I have to switch back to VIP?

No. You can keep your current route if it meets your needs. This notice confirms that the two VIP models are available again; it does not require a migration.

Can I keep my official-forward token when switching back?

Use a Default-group per-call token for these VIP models. Changing only the model field is not enough if your current token is configured for official forwarding. Confirm the token group, model permissions, and current price in the console.

What should I check if a VIP request still fails?

Check the exact model ID, token group, and model permissions, then follow the returned error message. If the problem continues, contact support with the request time, a redacted error, and the relevant call-log details. Do not include your full API key. The recovery status is based on the LaoZhang API operations confirmation dated September 22, 2026. It describes availability of the two LaoZhang API VIP routes.