Decart Lucy 2.5 has no clip limit; what Sume's video edit does

Decart's Lucy 2.5 is a video-to-video edit model with no clip-length cap, at $0.04 per second on Decart's own page. Sume's closest route is the Gemini Omni Flash 1.1 edit mode on the Video Router: you send one video_url and a prompt, resolution is optional and defaults to 720p, and there is no duration or aspect_ratio to set. The two are not the same product, and the table below keeps them apart.

The Decart numbers come from Decart's Video Editing page and its non-realtime overview, read on 2026-10-02. The Sume side comes from Video Router and Video generation. Nothing here is a quality ranking: neither page offers a benchmark, and this post does not make one up.

What does Decart's Lucy 2.5 accept?

Decart's page lists MP4 (H.264 or VP8) input, 16:9 or 9:16, a 200 MB file ceiling, and output at 720x1280 or 1280x720. Lucy 2.5 and Lucy 2.1 have unlimited duration at $0.04 per second; the legacy Lucy Clip is capped at 5 seconds and costs $0.15 per second. You can drive an edit with text, a reference image, or both, and Decart recommends prompts of 20 to 40 words.

What does Sume's video edit accept?

Sume's edit is one mode of gemini-omni-flash-1.1, which Sume routes by the shape of the request. Send video_url and a prompt that describes the edit; the docs say resolution is optional with a default of 720p, and that aspect_ratio and duration do not apply. video_url is the edit source, so it cannot be combined with image_url, end_image_url, or reference_*_urls. Native audio is always on.

Billing is provider list times 1.25 per output second by resolution. The repo catalog records the provider list as $0.10 per second at 720p (list dated 2026-08-28, subject to change), and the live number is whatever GET /v1/video-router/models returns when you call it.

curl -X POST https://api.sume.com/v1/video-router/generate \
  -H "Authorization: Bearer $SUME_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: omni-edit-001" \
  -d '{
    "model": "gemini-omni-flash-1.1",
    "prompt": "Make it dusk. Keep the people and motion the same.",
    "video_url": "https://example.com/clip.mp4",
    "resolution": "720p",
    "mode": "async"
  }'

Is $0.04 per second comparable to Sume's rate?

Not directly. Decart prices the whole edit per second of video on its own endpoint. Sume prices a different model, per output second by resolution, with a house margin on top. Divide neither number into the other and call it a verdict. If you are choosing on cost, run one representative clip through each and compare the actual invoice lines.

The Sume docs do not state a source-length ceiling for the edit mode, and this post will not guess one. What they do say is that generation limits are per model, so read capabilities from the catalog rather than assuming one envelope.

What if my source is long?

Sume's media tools work on clips you host with Sume: video inspect probes a clip, and video trim cuts ranges. For a long source, the safe pattern is to inspect it, trim it into short ranges, edit each range, and join the results afterwards. That is more calls than Decart's single long edit, and it is the honest trade: Sume does not advertise an unlimited-length restyle in these docs.

Decart's page does not state how a long source is processed internally, so this post does not either.

• Pick Decart when you need one long clip edited in one call at a published per-second price.
• Pick Sume's edit when the clip is short and you want it in the same job, billing, and webhook flow as your other Sume generations.
• Pick neither blindly: test both on the same ten seconds.

Which should you start with?

If your input is minutes long, start with Decart's published limits and run a short test. If your input is a short ad clip and you already generate with Sume, the edit mode saves a second integration. Either way, check the vendor page again before you commit: both sets of numbers are dated, and Sume's own docs say the provider list is subject to change.

A short test plan keeps the comparison fair: take one ten-second clip, write one prompt that names the change and says what to keep, run it on both, and compare the output and the billed amount side by side. Decart recommends prompts of 20 to 40 words, and a short, specific prompt is a good habit on either.