Model-Grounded Text-to-Video Workflow

Overview

Treat model choice as an API-schema decision, not a marketing label. Runway request bodies are discriminated by model; valid ratios, durations, prompt limits, optional controls, price, and even required fields can differ between models.

Prerequisites

• A product requirement covering quality, latency, duration, ratio, and budget
• Current Runway models, API reference, and pricing pages
• Durable task tracking and owned output storage

Instructions

Step 1: Define the output contract

Record modality, intended use, dimensions, duration, audio need, quality threshold, deadline, moderation policy, and maximum credits. Separate hard constraints from preferences.

Step 2: Choose direct model or router