runway

Generate and edit video with Runway through RunAPI. Use when the user asks an agent to create, edit, or transform video with Runway. Default to the RunAPI CLI for one-off generation; use SDKs only when the user is integrating RunAPI into an app or backend.

Runway on RunAPI

Generate and edit video with Runway through RunAPI. The default path for one-off agent tasks is the runapi CLI; SDKs are for application integration.

Routing decision

• One-off generation, editing, or transformation for the user → use the CLI path with the runapi binary.
• Building an app, backend, worker, library, or production codebase → use the SDK integration path.

CLI path

The runapi binary is the runtime dependency. Authenticate with runapi login (browser) or set RUNAPI_API_KEY; a saved CLI config also works — no required environment variable.

Inspect the available actions and request fields with CLI help:

shell

runapi runway --help
runapi runway text-to-video --help

Run a one-off task (synchronous — polls until the task completes):

shell

runapi runway text-to-video --input-file request.json

Submit asynchronously and poll separately:

shell

runapi runway text-to-video --async --input-file request.json
runapi wait <task-id> --service runway --action text-to-video

Available actions: text-to-video, extend-video.

SDK integration path

When integrating Runway into an app, backend, worker, or library — not for one-off tasks — use a RunAPI SDK package:

• JavaScript / TypeScript: @runapi.ai/runway
• Ruby: runapi-runway
• Go: github.com/runapi-ai/runway-sdk/go

References

• Model overview, pricing, and rate limits: https://runapi.ai/models/runway.md
• Provider comparison: https://runapi.ai/providers/runway.md
• Full model catalog: https://runapi.ai/models.md