DaVinci Resolve AI video plugin: Runway's, and an API route

Runway put a paid plugin in DaVinci Resolve on Sep 23, 2026. Sume has none; its API hands an editor separate clips or one assembled MP4.

4 min readSume
All posts

Runway's changelog lists a DaVinci Resolve plugin on Sep 23, 2026, tagged Paid, with the line "Runway is now available directly inside DaVinci Resolve." Sume's docs describe an HTTP API, a CLI and a hosted MCP endpoint, not an editor plugin, so with Sume you generate outside Resolve and import the MP4 files it returns.

What did Runway ship for Resolve?

One entry on Runway's changelog, read 2026-09-29: "DaVinci Resolve Plugin (Paid)", dated Sep 23, 2026. The entry does not list features, supported Resolve versions or credit rates, so this page states none. Check Runway's own pages before you plan a timeline around it.

Does Sume have a DaVinci Resolve plugin?

Not in the docs read for this page. The MCP overview lists the surfaces that exist: hosted MCP, a developer API and CLI, and the Studio Agent product. None is an editor plugin. The practical route is a file handoff: Sume produces MP4 files, and you import them into whatever editor you use.

Should I send the editor clips or one assembled file?

That depends on how much editing you want left. Separate clips keep every cut decision in the editor. One assembled file saves the editor's first pass but bakes in the transitions and the audio.

Two handoffs from Sume to an editor, from the Sume docs read 2026-09-29.
HandoffHowNotes from the docs
Separate clipsPOST /v1/videos, then GET /v1/videos/{jobId}/content per jobOne file per generation; limits are per model
One assembled MP4POST /v1/timeline-1.0/render1–200 video slots, audio spine of 1–1800 seconds, $0.10 per output minute rounded up

How do I get the frame size and rate right?

A Timeline render defaults to 1080×1920, a vertical frame, so a landscape project needs output.width and output.height (even integers from 256 to 2160). output.fps accepts 24, 25, 30 or 60; leave it out and the render follows the rate the sources already run at. A rate that differs from a source's is met by repeating or dropping frames, which shows as judder on motion, so match your Resolve project's rate to the sources when you can.

Import the generated clips first: Timeline only reads this workspace's media.sume.com files, and Idempotency-Key is required. The /plan route is an unbilled preflight. Details are in the Timeline docs.

How do I pull the files down?

Once a video job is completed, download it from the content endpoint. index defaults to 0.

curl "https://api.sume.com/v1/videos/{jobId}/content?index=0" \
  -H "Authorization: Bearer $SUME_API_KEY" \
  --output shot-01.mp4

What can surprise me when the render comes back?

Timeline reports soft warnings, which are not failures: a short source is padded or looped, a transition is snapped, and a still is held static with its motion ignored. Each video[] slot's fit defaults to cover, which fills the frame and crops the overflow, and a transition may not exceed one second. Coverage may trail the audio spine by at most 0.5 seconds. Read the warnings[] array in the job result before you drop the file on a Resolve timeline.

Sources

Related posts

More in Media tools

All Media tools posts

Written by Sume