Visual Style is gone — describe the look in Additional Direction

The Visual Style dropdown is no longer part of video creation. In practice almost every video was generated on the autodetect default, and the fixed list of styles competed with the far more expressive Additional Direction field. Generation now always behaves the way autodetect did, and the agent picks a look from your brand, your objective, and whatever you describe.

What changed in the product

• The Visual Style dropdown is removed from the video creation dialog and the video playground.
• Additional Direction is where you ask for a look now — write it the way you would describe it to an editor: "gritty handheld documentary footage, muted colors", "clean studio product shots on white".
• Videos generated before this change keep the style they recorded, and the editor sidebar still shows it. Adapting or regenerating such a video into a new video drops the stored style — the new video is generated under the current behavior.

Breaking change for the API and MCP

video_style has been removed from:

• the create_video_ad MCP tool, and
• POST /api/v1/videos.

These request schemas are strict, so a request that still sends video_style now fails validation with an unrecognized key error rather than silently ignoring the parameter. That is deliberate — a silently dropped style parameter would be much harder to notice.

To migrate: delete video_style from your payload. If you were sending a value other than autodetect, describe that style in additional_direction instead:

 {
   "brand_id": "...",
-  "video_style": "cinematic",
-  "additional_direction": "Feature the new summer menu."
+  "additional_direction": "Feature the new summer menu. Cinematic look — shallow depth of field, warm golden-hour grading."
 }

No other video parameters changed.