Documentation Index
Fetch the complete documentation index at: https://docs.mavera.io/llms.txt
Use this file to discover all available pages before exploring further.
Scenario
Take Mavera-generated content — blog posts, ad scripts, podcast intros, email copy — and convert them to high-quality audio using OpenAI’s TTS models. Build an audio content library from your text assets. Choose from six voices (alloy, echo, fable, onyx, nova, shimmer) and two quality tiers to match your brand tone. Flow: MaveraPOST /generations → text content → OpenAI POST /audio/speech (TTS) → audio files (.mp3)
Code
Example Output
Error Handling
Input text too long
Input text too long
TTS accepts up to 4,096 characters per request. For longer content, split at sentence boundaries and concatenate audio files with
ffmpeg -f concat -i list.txt -c copy output.mp3.Voice selection guidance
Voice selection guidance
Each voice has a distinct character:
alloy (neutral), echo (warm male), fable (expressive British), onyx (deep authoritative), nova (friendly female), shimmer (soft gentle). Test 2-3 voices per content type before standardizing.Audio quality tiers
Audio quality tiers
tts-1 is faster and cheaper but lower quality. tts-1-hd produces broadcast-quality audio with less distortion. Use tts-1 for internal drafts and tts-1-hd for published content.