Luma Modify Video: adhere, flex and reimagine modes vs a Sume prompt
Luma's Modify Video has nine modes: adhere 1-3, flex 1-3 and reimagine 1-3. Sume's video edit has no mode field, so strictness comes from the prompt.

Luma's Modify Video endpoint has a required mode with nine values in three families: adhere 1 to 3, flex 1 to 3 and reimagine 1 to 3. They set how closely the output follows the source. Sume's video edit has no mode field: the request is a video_url plus a prompt, and how much changes is decided by what the prompt says.
What the three families mean
Luma describes adhere modes as keeping the output very close to the source, for subtle changes and light stylization. Flex modes adhere somewhat to shapes, characters and details and allow larger style shifts while keeping recognizable elements. Reimagine modes adhere much more loosely, for fundamental transformations and new aesthetics.
| Family | Levels | Intent |
|---|---|---|
| Adhere | 1, 2, 3 | Very close to the source; subtle changes and light stylization |
| Flex | 1, 2, 3 | Somewhat flexible; larger style shifts, recognizable elements kept |
| Reimagine | 1, 2, 3 | Loose; fundamental transformations |
How to get the same range on Sume
The Sume edit example in the Video Router docs shows the pattern: Replace the bottle with an apple. Keep everything else the same. The first sentence is the change, and the second sentence is the strictness. There is no numbered dial, so write the constraint into the prompt.
A translation habit
A rough translation, as a starting point and not a rule that Sume documents:
- For an adhere-style edit, name one change and say to keep everything else the same.
- For a flex-style edit, name the style or look and list what must stay, such as the character and the framing.
- For a reimagine-style edit, describe the new look and say what you do not care about keeping.
- Run a short test and compare before you spend on a long source.
Keep each edit small
Sume's edit mode takes resolution as an optional field and refuses aspect_ratio and duration, so the output length follows the source. If you need a precise change, make one edit per request and chain the results, rather than packing several changes into one prompt.
Sources
Related posts
More in Developers
- MAI-Image-2.6 allows 6 requests a minute at tier 1; Sume queues
Foundry rates MAI-Image-2.6 at 6 RPM on tier 1 and 429s past it. Sume accepts valid image jobs as queued until a plan slot opens. Compare the two behaviours.
- MAI-Image-2.6 returns base64 PNG; Sume returns a hosted image URL
Foundry returns MAI-Image-2.6 as b64_json PNG only. Sume returns a signed media URL in data[].url, in png, jpeg or webp per model. How to handle each in code.
- Make an AI avatar video from the terminal with the Sume CLI
sume avatars create and sume avatar-videos create submit Avatar 1.0 jobs from a shell. Flags, the --confirm-paid guard, and how to recover the job.
- Mastra 1.69 Inngest retries option: durable agents and Sume jobs
Mastra core 1.69.0 adds a retries option for Inngest workflows and durable agents. Pair it with a Sume Idempotency-Key so a retried step never pays twice.
Written by Sume