Skip to main content
Lokutor answers OpenAI’s two audio endpoints, so tools that support an OpenAI-compatible speech provider work with Lokutor by pointing them at https://api.lokutor.com/v1 with your Lokutor API key. Billing, limits and errors are those of the underlying endpoints, at the published rates.

Text to speech

  • model is accepted and ignored: every request uses Versa 2.0.
  • voice takes OpenAI’s names, mapped to Lokutor voices (alloy→F1, nova→F2, shimmer→F3, coral→F4, sage→F5, echo→M1, onyx→M2, fable→M3, ash→M4, ballad→M5), or any Lokutor voice directly (F1, es_f3, a cloned voice id).
  • language is a Lokutor extra field (en, es, ca, gl, eu, pt, fr, it, de); without it the text decides.
  • The audio is always WAV, whatever response_format asks for. Clients that play the file or hand it to an audio element work; a client that insists on MP3 bytes does not.

Speech to text

response_format can be json (default, {"text": ...}), text, or verbose_json (adds language, duration and per-word times). srt and vtt are not supported. WAV audio only, as in the speech-to-text API.

OpenAI SDK

Open WebUI, LiteLLM and others

In Open WebUI’s Admin → Settings → Audio, choose the OpenAI engine for both text to speech and speech to text, set the base URL to https://api.lokutor.com/v1, paste your key, and give the voice (alloy or a Lokutor voice). In LiteLLM, use the openai/ prefix with api_base="https://api.lokutor.com/v1".