Runway Dev Platform

Workflow for integrating Runway Dev products into an application. Use MCP for live account state and management, the SDK for application code, and current docs for API contracts.

When to use: Building, modifying, debugging, or verifying a Runway integration, including work started from Dev Portal.

Do not use for: one-off media generation from the agent or direct REST CLI actions.

Start with the work

Make useful progress before explaining setup. Inspect the workspace and existing configuration without narrating each check. Ask a question only when missing information blocks the next change.

• Existing project: find its server boundary and user-facing integration point. Add a server route or function before integrating a frontend-only project.
• Empty workspace: ask what the user wants to build. You may recommend a small web app with visible inputs and output as a Runway starting point, but do not claim the user requested one.
• Before giving credential setup instructions, test whether RUNWAYML_API_SECRET is present without printing its value, for example with test -n "${RUNWAYML_API_SECRET:-}". If it is present, skip dotenv instructions.
• Use the official SDK. Install @runwayml/sdk for Node or runwayml for Python only if the project needs it and does not already have it.
• Keep updates short. Do not narrate a long setup sequence or checklist.

Current contracts