gpt-image-2.5-flare-2026-09-08 on Sume: use openai/gpt-image-2.5

Sume does not document gpt-image-2.5-flare-2026-09-08 as an accepted id, and an id outside its catalog returns 404 model_not_found. OpenAI's Flare page lists that dated snapshot; on Sume, send openai/gpt-image-2.5 (Flare) instead.

Snapshot names are from OpenAI's model page; Sume behavior from the Image API docs. Both read 2026-10-01.

Which snapshots does OpenAI list?

The Flare page lists two: gpt-image-2.5-flare and gpt-image-2.5-flare-2026-09-08. The page marks the dated one as the default snapshot. A dated name pins a version on OpenAI's side.

Which ids does Sume accept?

How do I call Flare?

Use the catalog slug. Bare legacy ids are accepted as aliases, but the org/slug form is what GET /v1/images/models returns.

curl -X POST https://api.sume.com/v1/images \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "openai/gpt-image-2.5",
    "prompt": "Isometric illustration of a tiny greenhouse"
  }'

Can I pin a version?

Sume's docs describe no snapshot pin. If a visual change would break your product, store the model and job id with each result and compare outputs when you update your integration.