runway-alephlisted

# Runway Aleph on RunAPI Generate and edit video with Runway Aleph 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. Run `runapi auth status` first. For agents and headless runs, prefer `RUNAPI_API_KEY` or import it into saved config with `printf '%s' "$RUNAPI_API_KEY" | runapi auth import-token --token -`. Use `runapi login` only when the user explicitly wants interactive browser auth. Inspect the available commands and request fields with CLI help: ```shell runapi runway-aleph --help runapi runway-aleph edit-video --help ``` Run a one-off task (synchronous — polls until the task completes): ```shell runapi runway-aleph edit-video --input-file request.json ``` Submit asynchronously and poll separately: ```shell runapi runway-aleph edit-video --async --input-file request.json runapi wait <task-id> --service runway-aleph --action edit-video ``` Available commands: `edit-video`. ## SDK integration path When integrating Runway Aleph into an app, backend, worker, or library — not for one-off tasks — use a RunAPI SDK package: - JavaScript / TypeScript: `@runapi.ai/runway-aleph` - Ruby: `runapi-runway_aleph` - Go: