Generate Images
Call /openai/images/generations, submitting model=gpt-image-2.5-flare:reverse and prompt.
gpt-image-2.5-flare:reverse and gpt-image-2.5-flare use the same reverse interface and per-image billing method. It is suitable for applications that need to explicitly mark the billing variant in requests; retain the full model name when calling it.
Submit requests to the public API at api.acedata.cloud using the documented parameters, then use the results in your application.
api.acedata.cloudgpt-image-2.5-flare:reverseInput parameters and result formats vary by service. Use the public API for this model and follow its guide for generation, task retrieval and editing operations.
gpt-image-2.5-flare:reversegpt-image-2.5-flareCall /openai/images/generations, submitting model=gpt-image-2.5-flare:reverse and prompt.
Call /openai/images/edits, use the same model, and provide image and editing instructions. Use JSON for image URLs and multipart for local images.
quality supports auto, low, medium, high, xhigh, and max. size can be auto or WIDTHxHEIGHT that complies with interface limits.
n supports 1–10 images; only 1 image is supported when using the b64_json return format. Editing can provide up to 16 reference images; see the interface documentation for specific size and file limits.
Requests are billed by successful image count. Even if the response contains Token usage statistics, the billing method is still determined by this reverse model. The base price is 0.19 Credits/successful image; account discounts and final charges are subject to Pricing and usage records.
When availability is restored, requests may be completed using a compatible GPT Image 2.5 Flare; the request model and per-image billing method remain unchanged.
First, use one image to verify the prompt, aspect ratio, and output format, then increase the number of generations. Edit instructions should separately describe the elements to keep and modify, for example, keep the product angle and only change the background.
Synchronous requests read images from data; in callback mode, first save task_id, then query or receive the final result. Check the final successful images, usage records, and charges.
This is the platform's explicit reverse-call alias, equivalent to gpt-image-2.5-flare.
If you want to explicitly select the reverse variant, enter gpt-image-2.5-flare:reverse; the full name includes :reverse.
This model is billed by the number of successfully generated images; the Token statistics in the response do not change the billing method.
Yes. The JSON image field in edit requests supports a single URL or an array of URLs; local images use multipart file upload.
n supports 1–10 images; multiple-image responses use URLs, while b64_json supports only a single image.
Save task_id, then query or receive the final result. Receiving a task ID only means the request has been accepted; only the final images and usage records should be used for verification.
Choose a development approach or application suited to this model and follow its setup guide.
Python SDK Integration Guide
SDK installation, authentication and examplesTypeScript SDK Integration Guide
SDK installation, authentication and examples