Image 1.0 input_urls, n and format: deprecated names to replace

Image 1.0 still accepts three deprecated field names: input_urls, n and format. Replace them with image_urls, num_images and output_format, which are the names the Image 1.0 docs tell you to prefer.

Read from Sume's Image 1.0 docs on 2026-09-30. Image 1.0 is retiring soon; it is a compatibility alias for Image Router Auto.

What do the old names map to?

The docs list the deprecated aliases and their replacements side by side.

Do the old names still work?

Yes. The docs say the deprecated aliases are still accepted. They do not give a removal date, so migrate before Image 1.0 itself retires rather than waiting.

What does a clean request look like?

The same edit written with the preferred names:

curl -X POST https://api.sume.com/v1/image-1.0/generate \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: image-names-001" \
  -d '{
    "prompt": "Soft daylight studio background, product unchanged",
    "image_urls": ["https://media.sume.com/artifacts/artf_demo/product.png"],
    "num_images": 2,
    "output_format": "webp"
  }'

What about moving to POST /v1/images?

That route uses n (1 to 10, lower per model) and input_references instead, so the names do not carry over one to one. Check the Image API docs and the model's catalog descriptors when you move.

How do I check this myself?

A quick search of your codebase for input_urls, "n" and format in image calls finds every place to change. Update them together with tests, and confirm the artifacts still come back under result.artifacts[]. The linked docs pages and the catalog endpoint show the current values, and this post reflects them as of 2026-09-30.