veo-3.1listed

# Veo 3 on RunAPI Generate and edit video with Veo 3 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 veo-3-1 --help runapi veo-3-1 text-to-video --help ``` Run a one-off task (synchronous — polls until the task completes): ```shell runapi veo-3-1 text-to-video --input-file request.json ``` Submit asynchronously and poll separately: ```shell runapi veo-3-1 text-to-video --async --input-file request.json runapi wait <task-id> --service veo-3-1 --action text-to-video ``` Available commands: `text-to-video`, `extend-video`, `upscale-video`. For `text-to-video`, request JSON may include `duration_seconds` with `4`, `6`, or `8` seconds. Omit it to use the default. ## SDK integration path When integrating Veo 3 into an app, backend, worker, or library — not for one-