klinglisted

# Kling on RunAPI Generate and edit video with Kling 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 kling --help runapi kling text-to-video --help ``` Run a one-off task (synchronous — polls until the task completes): ```shell runapi kling text-to-video --input-file request.json ``` Submit asynchronously and poll separately: ```shell runapi kling text-to-video --async --input-file request.json runapi wait <task-id> --service kling --action text-to-video ``` Available commands: `text-to-video`, `avatar`, `image-to-video`, `motion-control`. For Kling 3.0 text-to-video requests, keep `model: "kling-3.0"` and choose `output_resolution: "720p"`, `"1080p"`, or `"4k"` as needed. ## SDK integration path When integrating Kling into an app, backend, worker, or library