Image 1.0 is retiring and its URLs point at Auto: what to change
Sume says Image 1.0 retires soon and its public URLs are compatibility aliases for the Auto pipe. The three edits for a client that still calls /v1/image-1.0.
Sume has announced that Image 1.0 will retire soon, and the docs say its public URLs stay as compatibility aliases for the Auto pipe, meaning model sume/auto. If your code still calls /v1/image-1.0/generate, move it to POST /v1/images and pick either sume/auto or a pinned catalog id.
What the docs say
The Image API docs state that the legacy POST /v1/image-router/generate and GET /v1/image-router/models routes still work, are deprecated, and will not get new parameters. The Image 1.0 page is the legacy reference.
Three edits
Old calls carry through with small changes.
| Old | New | Note |
|---|---|---|
| /v1/image-1.0/generate | POST /v1/images | Same Auto pipe if you send model sume/auto |
| /v1/image-router/models | GET /v1/images/models | sume/auto is not listed there |
| Image URLs in the response | data[].url | Sume-hosted signed URLs, not base64 |
One honest gap
For transparent stills the docs currently still point to Image 1.0 with transparency true, while the ChatGPT Image 2.5 rows list a background field that accepts transparent. Both statements are in the docs today. Test the 2.5 route with your assets before you drop Image 1.0, and watch the docs for the retirement date, which the page does not give.
- Pin a model when you need repeatable looks.
- Keep sume/auto for work where the family does not matter.
- Log job.model, because it will say sume/auto.
Sources
Related posts
More in Developers
- Image API 200 or 202: branch on the status code, not the body
POST /v1/images returns images with 200 or a job envelope with 202. A small Python handler that branches on the code and prints the URLs to poll.
- Image API n: 10 per call in the schema, lower for each model
The Sume Image API schema allows n from 1 to 10, but each model lists its own n range. How to read the ceiling and what you pay for n images.
- Image burst after a model launch: 429 queue_full vs 503 retry plan
Launch week means batches. On Sume, 429 rate_limited, 429 queue_full and 503 provider_capacity_exceeded each need a different retry, plus idempotency keys.
- Sume /v1/images returns 200 or 202: branch on the status code
A slow 4K or xhigh image request on Sume returns 202 with a job envelope, not the image body. A Python client that handles 200, 202 and 502 correctly.
Written by Sume