output_format jpg or jpeg? What Sume's image routes accept

Image 1.0 accepts jpg as well as jpeg in output_format. POST /v1/images lists png, jpeg, webp and svg and does not list jpg, so send jpeg there.

From Sume's Image 1.0 and Image API docs, read 2026-09-30.

What does each route list?

The two tables differ by one alias and by svg.

What comes back?

POST /v1/images returns data[].url with a media_type such as image/png or image/webp. Image 1.0 jobs return artifacts under result.artifacts[] with content_type such as image/png. Check the returned type rather than trusting the extension in the URL.

How do I ask for JPEG on the Image API?

Use the listed spelling:

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": "Magazine cover photo of a coffee cup",
    "output_format": "jpeg"
  }'

What about compression?

output_compression (0 to 100 for webp and jpeg) is in the schema but no model advertises it in v1, so sending it returns 400 unsupported_parameter.

How do I check this myself?

If a client library sends jpg by habit, normalize it to jpeg when the target is /v1/images. Add a test that checks the format string you send. The linked docs pages and the catalog endpoint show the current values, and this post reflects them as of 2026-09-30.