ClawHub

runway-aleph

Other

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

Install

openclaw skills install runapi-runway-aleph

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. 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:

runapi runway-aleph --help
runapi runway-aleph video-to-video --help

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

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

Submit asynchronously and poll separately:

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

Available actions: video-to-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: github.com/runapi-ai/runway-aleph-sdk/go

References