Skip to content
Discussion options

You must be logged in to vote

No, there isn't one today.

The TTS surface is write-only: /v1/audio/speech, /tts, and the ElevenLabs-compatible POST /v1/text-to-speech/:voice-id (core/http/routes/elevenlabs.go:21). Note that last one takes a voice id but has no GET /v1/voices counterpart, unlike the real ElevenLabs API it mirrors — so there's nothing to enumerate against.

It also can't be added at the HTTP layer alone. backend/backend.proto has TTS, TTSStream and SoundGeneration, but no ListVoices-style RPC, so LocalAI has no channel to ask a loaded backend what it supports. Implementing this means a new proto method plus an implementation in every TTS backend (piper, kokoro, sherpa-onnx, vibevoice, fish-speech, qwen-tt…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@pinage404
Comment options

Answer selected by pinage404
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants