Frequently asked questions
Who owns the voices used in the API?
The voices are based on licensed recordings from LibriTTS-R (CC BY 4.0), derived from LibriVox public-domain audiobook readings. We provide these as eight distinct presets for use in your generated audio files without requiring additional attribution beyond standard license terms.
Is my text data sold to third parties?
No. Input text is used solely to produce the audio and is not used for training models. We do not sell your data to third parties. Generated audio is returned in the response and is not stored on our servers.
Do you store the generated audio files?
No. Generated audio is returned directly in the API response and is not stored by us. We retain request metadata, such as time, character count, and status, strictly for billing and usage tracking purposes.
How long are request logs kept?
Request metadata, including timestamp, character count, and status, is kept for billing purposes. We do not specify an exact retention duration for these logs, but they are retained long enough to verify charges and resolve billing inquiries.
Is there a phone number for support?
No. We do not offer a phone number for support. All customer support is conducted via email only. You can reach our support team through the contact page or by emailing us directly for assistance.
Do you have a physical office?
No. We do not list a physical office address. As an independent API provider, we operate remotely. Our infrastructure is cloud-based, and our team is accessible via email for all operational and support inquiries.
Can I request a new voice?
No. We offer a curated catalog of eight preset voices. We do not offer custom voice cloning or the ability to upload your own voice. You cannot request new voices; you must choose from the existing eight options.
Are the voices customizable?
No. The voices are fixed presets with specific tonal characteristics. We do not offer emotion tags, SSML support, or phoneme dictionary adjustments. You can only adjust the overall speed (0.25–4.0) and select the language for the output.
Is the API GDPR compliant?
We do not provide a specific GDPR certificate or claim explicit GDPR compliance. We do not offer enterprise contracts or SLAs. We process data as described, but you should verify compliance needs independently based on our data handling practices.
Do you offer enterprise contracts?
No. We do not offer enterprise contracts, SLAs, or uptime guarantees. We provide a straightforward API with transparent pricing and no minimum spend. All accounts are equal, with no special tiers or negotiated terms for large volume users.
How do I contact the editorial team?
Support is handled via email only. You can contact us through the /contact/ page on playr77.com. There is no phone number or live chat available for any team inquiries.
Is there a privacy policy link?
We do not list a physical office or phone number. For data handling details, refer to the Data section or contact us via email for clarification.
Who We Are
Playr77 operates as an independent storefront for the Lumivoice network, managing the storefront and API key issuance while the underlying service is provided by the network. We maintain a strict, transparent infrastructure designed specifically for developers who require consistent, scalable audio generation without the complexity of enterprise-grade systems.
Independent Editorial Team
Our team manages the storefront and API key issuance, while the underlying service is provided by the network. We focus on delivering a reliable, straightforward API experience without unnecessary layers of corporate bureaucracy or third-party dependencies.
- Direct API access
- Transparent key management
Focus on Indie Developers
We build tools for indie developers who need consistent, scalable audio generation without complex infrastructure. Our API integrates seamlessly with existing workflows, allowing you to send text and receive audio files quickly and predictably.
No Corporate Overhead
We operate without the overhead of large corporations, allowing us to offer transparent pricing and straightforward integration. Our structure ensures that you pay only for what you use, with no hidden fees or complex tiered plans.
Voice Licensing
Lumivoice delivers eight distinct voice presets derived from the LibriTTS-R dataset. This foundation ensures consistent audio quality while maintaining clear legal provenance for every synthetic voice used in your API responses.
LibriTTS-R Source
Our voices are synthesized from high-quality recordings within the LibriTTS-R dataset. This provides a reliable, standardized base for all eight presets, from warm narrators to neutral news anchors, without relying on proprietary, opaque source material.
CC BY 4.0 License
The underlying dataset operates under the Creative Commons Attribution 4.0 International license. This allows us to legally process and repurpose these audio samples for commercial API usage. You receive a functional TTS service backed by a transparent, standard public license.
Public Domain Readings
Many source recordings originate from LibriVox, featuring public domain audiobook readings. This ensures that the core vocal performances are free from restrictive copyright claims. We handle the technical synthesis, leaving you with a straightforward, legally sound audio product.
Data Policy
Our text-to-speech API processes input text solely for the purpose of generating the requested audio file. We do not use your submitted text to train our underlying models or improve voice synthesis algorithms. Once the audio is delivered, the original text payload is not retained in our long-term storage systems.
Input Text Usage
The input string is processed immediately to synthesize audio and is not archived for future training purposes. This ensures that your proprietary content remains distinct from our model development data.
Audio Storage Policy
Generated audio files are returned directly in the API response and are not stored on our servers after delivery. There is no persistent storage of your synthesized speech unless you download and save it locally.
Metadata Retention
We retain request metadata, including timestamp, character count, and status, specifically for billing accuracy and usage tracking. This data allows us to process charges correctly and maintain account integrity.
- Request timestamp
- Character count
- Request status (success/failure)
- Voice model used
Technical Limits
Lumivoice delivers a straightforward, batch-oriented text-to-speech API without real-time streaming capabilities. Audio files are generated sequentially and returned once synthesis completes, ensuring consistent processing order but requiring clients to handle wait times for longer texts.
No Streaming Support
The API returns complete audio files rather than streaming partial chunks. Clients must wait for the full synthesis job to finish before receiving data, which simplifies integration but does not support low-latency live audio delivery.
No SSML or Lexicons
Support is limited to basic text input without SSML tags or custom pronunciation lexicons. The system guesses language from script if unspecified, but users must explicitly set the language for non-English Latin text to ensure accuracy.
- Standard text input only
- No SSML tag support
- Explicit language code recommended for non-English text
Single Key per Account
Each account maintains one active API key at a time. Issuing a new key immediately invalidates the previous one, ensuring simple access management without complex key rotation logic.
- One active key per account
- Immediate invalidation on rotation

Contact and Support
Support for Lumivoice is managed exclusively through email. We do not maintain a live chat widget or a dedicated phone line for user inquiries. All technical questions, billing issues, and feedback are handled via a single support email address.
Email Only Support
We rely on asynchronous communication to ensure every query receives a thorough, documented response. This approach allows our small team to address complex technical details without the pressure of real-time availability.
- Single email address for all inquiries
No Live Chat
There is no real-time chat support available on any page of our site. You will not find a floating chat widget or a "talk to an agent" button. This eliminates the expectation of instant answers during off-hours.
Response Times
Typical response times vary based on current volume, but we aim to reply within 24 hours on business days. During high traffic periods, responses may take longer. We do not guarantee a specific response window.
Transparency
Lumivoice provides a straightforward text-to-speech API without marketing fluff. We focus on delivering consistent audio generation for indie developers who value transparency over complex infrastructure.
Honest Product Limits
We do not offer streaming, SSML, or custom voice cloning. Our API returns static audio files via standard HTTP requests, ensuring predictable behavior for all integrations.
No Hidden Features
The service includes exactly eight licensed voices and 23 supported languages. There are no hidden tiers or surprise capabilities; the feature set matches the documentation precisely.
Clear Pricing
Pricing is simple: $10 per million characters, with spaces and punctuation counting toward the total. Failed requests are free, and there are no monthly subscriptions or minimum spend requirements.
- USDT (TRC-20) top-ups only
- No VAT or invoice fees
- Balance does not expire
Listen to the 8 voices
Each sample below was generated by this API from the same sentence.
23 languages
Any voice speaks any of these languages.
Sources and further reading
- Wikipedia
- Creative Commons Attribution 4.0
- OpenAI API reference: create speech
- curl documentation
- ISO 639 language codes
- MDN: Web Speech API
- IETF RFC 7845: Ogg Opus
- LibriTTS-R paper (arXiv 2305.18802)
- openai-python on GitHub
- LibriTTS-R corpus (OpenSLR 141)
- LibriVox public-domain audiobooks
- W3C WAI: making audio and video accessible
