happyhorselisted

# HappyHorse on RunAPI Generate text, image, or edit-video clips with HappyHorse through RunAPI. Text-to-video can also use ordered reference images through the character model. The default path for one-off agent tasks is the `runapi` CLI; SDKs are for application integration. ## Routing decision - One-off text, image, or edit-video generation 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 happyhorse --help runapi happyhorse text-to-video --help runapi happyhorse image-to-video --help runapi happyhorse edit-video --help ``` Run a one-off task: ```shell runapi happyhorse text-to-video --input-file request.json runapi happyhorse image-to-video --input-file request.json runapi happyhorse edit-video --input-file request.json ``` Submit asynchronously and poll separately: ```shell runapi happyhorse text-to-video --async --input-file request.json runapi wait <task-id> --service happyhorse --action text-to-video ``` For image-to-video and edit-video, use