Runway Brand Kits in MCP, and how Sume handles references

Runway's changelog says that on Sep 22, 2026 agents using Runway MCP can reference Brand Kits, while creating and editing a kit stays in Runway's main product. Sume's video docs describe no saved brand kit; you keep your brand look by sending reference images, and for some models video or audio references, with each request.

What did Runway change?

According to Runway's changelog, read 2026-09-29, the Sep 22, 2026 entry "Brand Kits in Runway MCP" lets agents reference Brand Kits, and creation and editing stay in the main product. The entry does not list what a kit contains or which models honor it, so this page does not either.

Does Sume have a brand kit?

The Sume video docs read for this page describe references as fields on each request: frame_images for first and last frames, and input_references for style or content reference images that the model uses as visual guidance. They do not describe a saved kit object. Anything you want repeated across clips, such as a logo lockup, product photo or palette board, goes into every request, or into your own template that builds the request.

If both fields arrive together, frame_images takes precedence and the request is treated as image-to-video. Use input_references alone when you want guidance rather than exact frames.

Which models accept which references?

Only models whose supported_input_references lists a type accept it, so read the catalog before you build a template.

How does this work when an agent calls Sume?

Through hosted MCP, generate_video is a paid tool. Under OAuth it needs the opt-in Write scope, and every paid submit needs an idempotency_key. The agent has to be handed the reference URLs, or fetch them from your own store, on every call; nothing in the docs carries a kit from one call to the next.

Practical setup: keep one folder of brand references, note the URL of each, and put the same list in the prompt or the template your agent uses. For a model whose supported_input_references omits a type, drop that type rather than expecting the model to ignore it. The video docs and the Video Router page list the fields.

When would a saved kit be the better fit?

A kit you edit once in a product UI suits a team that wants non-technical people to control the look. Per-request references suit code that already assembles requests, because the brand inputs live beside the prompt in version control. Those are two workflows, and this page does not rank them.