elevenlabslisted

# ElevenLabs on RunAPI Generate speech, dialogue, and sound with ElevenLabs 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 elevenlabs --help runapi elevenlabs text-to-speech --help ``` Run a one-off task (synchronous — polls until the task completes): ```shell runapi elevenlabs text-to-speech --input-file request.json ``` Submit asynchronously and poll separately: ```shell runapi elevenlabs text-to-speech --async --input-file request.json runapi wait <task-id> --service elevenlabs --action text-to-speech ``` Available commands: `text-to-speech`, `text-to-dialogue`, `text-to-sound`, `speech-to-text`, `isolate-audio`. ## SDK integration path When integrating ElevenLabs into an app, backend, worker, or library — not for one-off tasks — use a RunAPI SDK package: