Krea 2 creativity parameter vs Sume's unsupported_parameter

Krea 2 treats creativity as an actual request parameter: at high values the model adds aesthetic depth, interpretation and visual richness to what you give it. Sume has no creativity field. A request that sets one is rejected with a 400, so steer with the prompt and references instead.

Krea facts are from its Krea 2 API overview; Sume facts are from Image models, read 2026-10-01.

What does creativity do on Krea 2?

The overview lists tunable creativity among Krea 2's strengths. The page text I read does not give a range or default for it, so check Krea's parameter reference before you pick a value.

What happens if I send creativity to Sume?

The docs say a request that sets a parameter the selected model does not list is rejected with 400 unsupported_parameter rather than silently dropped, and a model accepts only the values its catalog descriptors list. The Image API parameter table has no creativity row, so expect a 400, but the docs do not name the exact error code for a field outside the schema.

curl https://api.sume.com/v1/images \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"sume/auto","prompt":"a quiet harbor","creativity":0.8}'
# expect: a 400 (creativity is not in the request schema)

What can I tune on Sume instead?

None of these is a creativity dial. Use n to compare several takes of the same prompt.

How do I know what a model accepts?

Read the descriptors from GET /v1/images/models/{model_id}/endpoints before you add a parameter, and drop any the model does not list. The same check applies to `seed`, which is also not served in v1.