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. 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 elevenlabs --help
runapi elevenlabs text-to-speech --help

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

runapi elevenlabs text-to-speech --input-file request.json

Submit asynchronously and poll separately:

runapi elevenlabs text-to-speech --async --input-file request.json
runapi wait <task-id> --service elevenlabs --action text-to-speech

Available actions: 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:

• JavaScript / TypeScript: @runapi.ai/elevenlabs
• Ruby: runapi-elevenlabs
• Go: github.com/runapi-ai/elevenlabs-sdk/go

References

• Model overview, pricing, and rate limits: https://runapi.ai/models/elevenlabs.md
• Provider comparison: https://runapi.ai/providers/elevenlabs.md
• Full model catalog: https://runapi.ai/models.md

Variants

• Turbo v2.5 text to speech
• Multilingual v2 text to speech
• Dialogue v3
• Sound effects v2
• Speech to text
• Audio isolation