CometAPI’s Flare edit label still needs an actual edit-request contract

CometAPI’s GPT Image 2.5 Flare page gives an edit integrator a route label, but not yet an edit request to implement. Treat POST /v1/images/edits as a documented reference—not as a complete input contract for gpt-image-2.5-flare.

The distinction matters if the job is to change an existing product photograph rather than generate a new composition. Before deciding how an upload form should send the photograph, the integration needs evidence about the edit body itself.

What the Flare page actually demonstrates

In the CometAPI GPT Image 2.5 Flare catalog page, captured on September 9, 2026, the API section labels both /v1/images/edits and /v1/images/generations. The visible cURL example, however, posts to https://api.cometapi.com/v1/images/generations, supplying model: "gpt-image-2.5-flare" and a text prompt. The Python and JavaScript examples likewise call images.generate.

Those are generation examples. Changing the route string to /images/edits would not establish how to supply an existing image, what additional fields are required, or how to read an edit response. The captured page does not provide an edit payload or response schema. This is a documentation boundary, not a finding that CometAPI edits fail or are unavailable.

An edit-contract worksheet, with the blanks left visible

Here is a proposed implementation worksheet for this exact CometAPI listing. “Documented” means visible in the catalog, not verified by a runtime request. All runtime checks below are unexecuted.

Contract item Evidence available now What would close the gap
Edit route The page labels POST /v1/images/edits. An edit-specific CometAPI request example and a successful response for this model.
Model identifier The page and generation examples name gpt-image-2.5-flare; edit acceptance is untested. An edit-specific example naming that exact ID, followed by an authorized check.
Body encoding Unknown for edits; the JSON generation body does not settle it. A documented edit content type and body schema. Do not assume multipart.
Image input Field name and representation are unknown. Documentation specifying whether and how image data is supplied, followed by a check using a permitted test asset.
Mask field Presence, omission rules and meaning are unknown. An explicit edit schema defining any mask field and its rules; do not invent one.
Required parameters Unknown for edits. A minimal edit request with required versus optional fields identified. The generation sample’s two fields are not that proof.
Input limits File count, size and format limits are unknown. Model-and-route-specific limits, then bounded acceptance checks.
Response representation Unknown for edits. A documented response schema and an actual response whose image output can be retrieved or decoded as specified.

The implementation decision

Keep the edit adapter provisional until the request and response blanks are filled. In particular, do not commit an image-upload representation or promise mask controls from this catalog sample alone. For a proposed test such as changing a product photo’s background while retaining its silhouette, accepting the request would be only the first checkpoint; inspecting the returned image would be a separate, still-unexecuted check.

This worksheet is tied to CometAPI’s GPT Image 2.5 Flare listing and its exact model ID. It does not establish an alias relationship with another GPT Image 2.5 identifier or transfer an edit contract from another model. The reusable lesson is to separate a route label from a demonstrated request; the concrete missing contract here belongs to this Flare integration.

What edit-specific CometAPI documentation would fill the input and response cells without borrowing assumptions from the generation example?