Frequently asked questions
What is the best voice for a male NPC?
Choose from four male presets: felix for energetic promos, milo for conversational tones, atlas for neutral news delivery, or orion for deep documentary styles. Each voice is based on licensed recordings from LibriTTS-R (CC BY 4.0), from LibriVox public-domain audiobook readings.
How do I ensure voice consistency?
Select one of the eight fixed voice presets for your NPC and reuse it across all dialogue requests. Since voices are static presets rather than dynamic clones, the audio characteristics remain identical for every generation, provided you use the same voice parameter in your API calls.
Can I change voices mid-conversation?
Yes, simply send a new request with a different voice parameter in the JSON body. Each request generates an independent audio file, allowing you to switch characters between dialogue lines.
How long does it take to generate dialogue?
Generation is roughly real-time, averaging 25 characters of text per second of audio. Short phrases take a few seconds, while longer texts process sequentially. Under load, requests may wait in a queue, but typical usage remains fast enough for iterative development workflows.
Do I need to split text manually?
Yes, split input text into parts of up to 4096 characters per request. You must join the resulting audio files yourself. The API processes each chunk independently, so handling the concatenation in your client code ensures no data is truncated due to length limits.
What formats work best for game engines?
You can choose mp3, wav, opus, flac, or pcm via the response_format field. MP3 and Opus are efficient for storage, while WAV and FLAC offer lossless quality. PCM provides raw data for immediate processing. Select the format that best fits your engine’s audio pipeline requirements.
How much does NPC dialogue generation cost?
Pricing is $10 per 1 million characters, or $0.01 per 1,000 characters. Spaces and punctuation count toward this total. Failed requests are free, with charges returned in full. This transparent model allows you to budget precisely based on your character dialogue volume without hidden fees.
Can I use this for multiplayer games?
Yes, the API is stateless and scalable for multiplayer environments. Each request is independent, so you can generate dialogue for multiple players simultaneously. Just manage your API key’s rate limit of 60 requests per minute (10 per minute before the first top-up).
Is there a limit on concurrent requests?
Requests are processed one after another, so under heavy load, your requests may wait in a queue. The limit is 60 requests per minute per key. This sequential processing ensures stability, but you should account for potential latency during peak usage periods in your game’s audio system.
How do I handle special characters in text?
Send standard text in the input field of the JSON body. The API handles standard characters naturally. Since there is no SSML support, you cannot use special tags for pronunciation. Ensure your text is within the 4096 character limit to avoid truncation during generation.
Can I use the audio for voiceovers?
Yes, the generated audio files are returned directly in the response and can be used for voiceovers. Each file carries an inaudible watermark marking it as synthetic speech. Input text is used only to produce the audio and is not used for training.
Do you support dynamic voice mixing?
No, the API does not support real-time streaming. Each request generates a separate audio file. You must handle mixing and transitions between different voice presets in your game engine or client-side audio player after receiving each individual audio response.
How do I debug a failed request?
If synthesis fails, the charge is returned in full. Check your HTTP response status code and body for error details. Ensure your Authorization header is correct and your text is within the 4096 character limit. Failed requests do not consume your character balance.
Can I export voices as a list?
Yes, send a GET request to /v1/voices to retrieve a list of available voices, languages, formats, and pricing details. This endpoint provides the exact metadata needed to configure your game’s audio settings, ensuring you select the correct voice IDs for your NPC dialogue generation.
Understanding NPC Audio Requirements
NPC dialogue demands distinct personalities without requiring complex emotion tags. Use different voice presets to signal character personality, such as the warm, clear narration of Aria for guides or the deep, documentary tone of Orion for lore entries. This approach gives your game a consistent audio identity while keeping implementation simple.
Variety in tone
Use different voice presets to signal character personality. Selecting from our eight distinct voices allows you to differentiate between a friendly merchant and a stern guard without needing manual audio editing.
Consistency across character lines
Maintain a single voice ID for each character across all quests. This ensures that players instantly recognize their companions and enemies, building immersion without the overhead of custom voice cloning.
Speed for rapid prototyping
Adjust the speed parameter (0.25–4.0) to match your game's pacing. Whether you need slow, atmospheric narration or fast-paced combat commands, the API handles the generation quickly, supporting rapid iteration during development.
Selecting the Right Voice Preset
Choosing the correct voice preset ensures your NPCs sound distinct and appropriate for their roles. QuestVoice offers eight presets, each designed for specific narrative functions, allowing you to assign a unique identity to every character without additional effort.
Aria for warm narrators and guides
Aria provides a warm, clear narrator voice ideal for guide characters or lore explanations. Her tone invites players in, making complex game mechanics or story backdrops feel accessible and engaging without sounding robotic.
Atlas for neutral news-style dialogue
Atlas delivers a neutral, news-style delivery perfect for quest updates, radio broadcasts, or objective markers. His consistent, unemotional tone ensures clarity and allows the player to focus on information rather than vocal performance.
Orion for deep documentary tones
Orion offers a deep, documentary-style voice suitable for ancient histories or mysterious lore. His rich timbre adds weight to significant narrative moments, helping to distinguish historical records from immediate gameplay dialogue.

Handling Multiple Languages
NPC dialogue often spans multiple regions, requiring your API to handle diverse linguistic inputs seamlessly. QuestVoice supports 23 distinct languages, allowing you to generate authentic voices for international game worlds without managing separate voice models for each region.
Automatic detection for Latin scripts
For text using Latin characters, the API automatically guesses the language as English by default. This simplifies integration for English-first projects, but you can override this behavior when needed to ensure accurate pronunciation for other Latin-based languages.
Manual ISO codes for non-English Latin
If your NPC speaks French, German, or Spanish using Latin script, explicitly set the language field in your request. Without this code, the system defaults to English, which may result in unnatural accents or mispronunciations for non-English dialogue.
Support for 23 distinct languages
QuestVoice supports Arabic, Chinese, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hindi, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Russian, Spanish, Swahili, Swedish, and Turkish. Any voice can speak any of these languages, ensuring consistent audio quality across your entire cast.
Optimizing Request Payloads
Optimizing your request payloads ensures your NPC dialogue sounds natural and integrates smoothly without wasting credits or hitting limits. By carefully structuring your API calls, you can maintain high audio quality while keeping generation times predictable for your game’s runtime.
Understanding the constraints of the TTS engine helps you design better dialogue pipelines. You have control over how text is processed, how fast it is spoken, and the final file format delivered to your engine.
Keep inputs under 4096 characters
Each API request accepts a maximum of 4096 characters for the input field. This limit includes spaces and punctuation. If your NPC has a longer monologue, split the text into smaller chunks, generate audio for each, and join them sequentially in your engine.
This constraint ensures stable processing. Requests are handled one after another, so keeping payloads concise helps maintain a steady flow without unnecessary queuing delays during peak times.
- Count spaces and punctuation toward the 4096-character limit.
- Split long dialogues into logical sentences before sending requests.
- Join the resulting audio files in your game engine.
Use speed adjustments for pacing
Adjust the speed parameter between 0.25 and 4.0 to match your character’s personality or emotional state. Slower speeds create a calm, instructional tone, while faster rates suit energetic or urgent dialogue.
This feature allows you to fine-tune delivery without re-recording or generating new audio files. It is particularly useful for creating distinct pacing between different NPC types, such as a slow-walking elder versus a quick messenger.
- Set
speedfrom 0.25 (slow) to 4.0 (fast). - Use lower speeds for narrative or calming dialogue.
- Increase speed for energetic or urgent character lines.
Choose formats like MP3 or WAV
Select the response_format based on your engine’s needs. MP3 offers small file sizes for efficient storage, while WAV provides uncompressed quality. You can also choose OPUS, FLAC, or PCM depending on your pipeline.
The choice affects both storage and processing. MP3 is ideal for reducing bandwidth and disk usage in large games, whereas uncompressed formats ensure maximum fidelity for close-mic dialogue moments.
- MP3 for smaller file sizes and efficient storage.
- WAV for uncompressed, high-quality audio.
- Support for OPUS, FLAC, and PCM formats.
Integrating with Game Engines
QuestVoice provides a straightforward REST API that integrates directly into your game’s asset pipeline. By sending standard HTTP POST requests, you can trigger speech synthesis for NPC dialogue without needing a proprietary SDK or complex middleware.
Use HTTP requests in your game logic
Send text to https://api.playa555.com/v1/audio/speech with your chosen voice and format. The API returns the audio file directly, allowing you to save it locally or stream it into your engine’s audio mixer.
Cache generated audio for reuse
Since NPC lines are rarely regenerated, cache the resulting MP3 or WAV files in your project directory. This eliminates repeated API calls for static dialogue, reducing costs and ensuring consistent audio quality across playthroughs.
Stream or load asynchronously
For real-time interactions, load audio assets asynchronously to prevent frame drops. The API does not offer WebSocket streaming.
Managing Character Voice Consistency
Maintaining a consistent voice is critical for player immersion. When an NPC speaks across multiple quests or dialogue trees, their voice must remain recognizable. Switching voices randomly can break the illusion of a single character and confuse players.
Stick to one voice preset per character
Assign each character a specific voice preset from the start. For example, use Atlas for news-style dialogue or Orion for deep, documentary tones. Once chosen, never swap the voice for that character, even if the script tone changes.
Use the same voice ID in requests
Ensure your API calls always include the same voice parameter for a given character. This guarantees that every line, whether short or long, is synthesized with identical vocal characteristics. Consistency in the voice ID prevents accidental variations in tone or pitch.
- Map voice IDs to character IDs in your database.
- Use environment variables for voice selection to avoid hardcoding.
Avoid switching voices mid-scene
Even within a single conversation, stick to the assigned voice. Switching mid-scene can make the NPC seem unstable or disjointed. If you need a different emotion, adjust the speed parameter instead of changing the voice preset.

Dealing with Long Quest Dialogues
NPC dialogue often exceeds the 4096-character limit per request, requiring you to split long quests into smaller segments before sending them to the API. This ensures each chunk is processed efficiently without truncation or errors in the synthesis engine.
Split text into chunks under limit
Break your dialogue text into segments no longer than 4096 characters. Each segment is treated as a separate synthesis job, allowing the system to handle long scripts without hitting payload limits. Remember that spaces and punctuation count toward this total.
Generate audio for each chunk
Send each text segment via a separate POST request to the speech endpoint. The API processes requests sequentially, so under heavy load, you may experience slight delays. Each request returns a distinct audio file corresponding to that specific chunk of text.
Join audio files sequentially
Once all chunks are synthesized, concatenate the resulting audio files in the exact order of the original text. This creates a seamless long-form dialogue track. Ensure your game engine can load these files sequentially to maintain immersion without noticeable gaps between segments.
Testing Voice Quality in Game Context
Before integrating NPC dialogue into your build, validate how the synthetic speech behaves within your engine’s audio pipeline. Listen for natural flow and pacing, ensuring the voice preset matches the character’s intended tone without sounding robotic or disjointed during rapid exchanges.
Listen for natural flow and timing
Generate sample lines and play them back in your game’s audio mixer. Check that the speed settings (0.25–4.0) create a comfortable listening rhythm. Since requests are processed sequentially, ensure your logic handles any slight delays gracefully so dialogue doesn’t feel laggy during cutscenes.
- Test voice presets like Atlas for news-style or Orion for documentary tones to ensure they fit the scene's mood.
- Verify that speed adjustments do not distort pronunciation or make dialogue hard to understand.
Check background noise compatibility
NPC lines often compete with environmental sounds. Generate audio in formats like MP3 or WAV and test them against your game’s ambient tracks. Ensure the synthetic voice’s clarity isn’t lost under heavy background noise or music, maintaining intelligibility for the player.
- Compare generated audio quality against your game’s existing sound assets.
- Adjust volume levels in-engine to balance NPC voices with environmental effects.
Validate with player feedback
Share prototypes with a small group of testers to gather reactions. Ask if the voices feel consistent with the character’s personality and if the dialogue feels immersive. Use this feedback to tweak voice selections or language settings before scaling up production.
- Collect notes on voice consistency across different scenes.
- Identify any voices that feel unnatural or mismatched with the character’s role.
Cost Management for Dialogue Batches
Managing audio costs is straightforward because pricing is tied directly to input length. You pay $0.01 per 1,000 characters, so estimating your dialogue volume helps predict budget needs accurately. Failed requests are free, ensuring you only pay for successful audio generation.
The dashboard provides real-time visibility into your spending, character usage, and remaining balance. This transparency allows indie studios to scale NPC dialogue generation without unexpected charges or hidden fees.
Estimate character counts beforehand
Calculate total characters before generating batches. Since spaces and punctuation count, plan your text length carefully to stay within budget limits.
Use the $10 per 1 million characters rate to forecast costs for large dialogue trees or ambient narration projects.
- Count all characters, including spaces and punctuation
- Plan for 4096-character limits per request
Monitor usage via dashboard
Check your balance and character usage regularly through the /get-api-key/ page. The dashboard shows your current balance, trial status, and total characters consumed.
Track request status to ensure you are only charged for successful syntheses.
- View real-time balance updates
- Track character consumption per key
Top up USDT for bulk generation
Fund your account with USDT on the TRON network (TRC-20). Minimum top-up is $5, and credits are added automatically within minutes.
This method supports bulk generation without monthly subscriptions or minimum spend requirements, keeping your workflow flexible.
- Use USDT (TRC-20) for funding
- Minimum top-up: $5
Common Pitfalls in NPC Audio
NPC dialogue generation is straightforward, but small oversights can break immersion or stall production. Recognizing these common pitfalls early helps indie studios maintain audio quality and workflow efficiency without unnecessary delays.
Ignoring language detection errors
The API guesses language from the script, defaulting to English for Latin text. If your NPC speaks French or German but uses Latin characters without specifying the language field, the engine may misinterpret accents or phonemes.
- Always set the
languageISO code for non-English Latin-script dialogue to ensure accurate pronunciation.
Overloading the API with parallel requests
Requests are processed sequentially. Sending too many parallel synthesis jobs causes queuing, increasing latency for short phrases. This can stall your game's asset pipeline during bulk generation.
- Limit parallel requests to avoid queue wait times, especially during rapid prototyping phases.
Not handling rate limits gracefully
You are limited to 60 requests per minute per key. Exceeding this triggers throttling. Implement exponential backoff in your integration to handle retries smoothly without dropping dialogue assets.
- Monitor your dashboard usage and implement retry logic to stay within the 60 RPM limit.

Best Practices for Indie Studios
Indie developers can validate their audio pipeline quickly using the $0.50 free trial credit, which provides approximately 50,000 characters for seven days. This allows you to generate and test NPC dialogue without upfront costs, ensuring the voice presets match your game’s tone before committing to bulk production.
Start with the free trial credit
Use the trial to test multiple voices like Aria or Orion with your actual in-game text. Since the credit expires in seven days, prioritize testing the most complex dialogue trees first to ensure the API meets your pacing and quality needs.
- Trial credit: $0.50 (approx. 50,000 characters)
- Valid for 7 days upon Google sign-in
- Ideal for rapid prototyping and voice selection
Use OpenAI SDK for easy integration
Since our API mirrors the OpenAI speech endpoint, you can reuse existing OpenAI SDKs by simply changing the base_url to https://api.playa555.com/v1. This minimizes code changes and leverages familiar authentication patterns with your tts-... key.
Pass your text, chosen voice, and desired format via JSON. The SDK handles the request structure, allowing you to focus on integrating the returned audio files into your engine’s asset pipeline.
- Compatible with official OpenAI SDKs
- Set
base_urltohttps://api.playa555.com/v1 - Use standard
Authorization: Bearerheader
Document your voice assignments
Keep a clear mapping of which voice preset corresponds to each character or NPC type. Since you can only have one active API key per account, consistent naming helps you manage voice IDs across different scenes and updates.
Record which voices handle specific roles (e.g., Atlas for news-style announcements, Nova for upbeat quests) to maintain consistency during rapid prototyping and later production phases.
- Map voices to character roles
- Track voice IDs for consistency
- Simplify future audio updates
Listen to the 8 voices
Each sample below was generated by this API from the same sentence. Craft immersive game worlds where NPCs feel truly alive and responsive to player choices.
23 languages
Any voice speaks any of these languages.
