Images Edits
The web Images Edits operation under the openai_images_edits internal call entry.
A web operation under an internal call entry, not a public Images API
openai_images_edits is an internal call entry in 8788 and is currently used only by the signed-in online image generation page. It does not expose a public POST /v1/images/edits; the OpenAI SDK-compatible multipart image editing entry is still out of scope.
Paths
| Purpose | Method and path | Authentication |
|---|---|---|
| Image-to-image | POST /api/img/edits | Web login session |
The request also supports POST /api/img/edits/ with a trailing slash.
Request body
{
"model": "Public model id available for Images Edits",
"prompt": "Generate a poster from the reference image",
"size": "1024x1024",
"n": 1,
"images": [
{ "image_url": "data:image/png;base64,..." }
]
}Prop
Type
Backend behavior
The gateway uses the openai_images_edits internal call entry to select the model product and upstream capability, then forwards the request to the upstream's /v1/images/edits. This is the outbound path; the only inbound path remains /api/img/edits.
Configuration and billing
The administrator must configure both:
- The model product under the
openai_images_editsinternal call entry. - An
openai_images_editscapability pointing to the real upstream.
Settlement reuses the image billing rules: on successful settlement, the gateway reads the actual number of images returned in the response's data array and charges by image. The current implementation does not separately persist user uploads, reference images, or generated images; images are used only in the generation call and browser display flow.
Last updated on