Transparent Pricing & Licensed Voices for Your TTS Needs

By VoxLocale editorial team · Updated 2026-11-18

Welcome to the VoxLocale about page, where we explain how our independent storefront supports localization agencies scaling their dubbing pipelines. You will find the exact licensing sources for our eight voice presets, the transparent character-based pricing, and the specific technical limits of our API. This information is designed to help you evaluate whether our 23-language, 8-voice system fits your localization workflow.

As an independent entity, we provide access to the TTS API without the overhead of enterprise contracts or SLAs. We focus on clear data policies, straightforward billing via USDT, and honest technical details so you can integrate our voices into your automation tools with confidence. Read on to understand our editorial approach, our voice origins, and how to contact our support team.

Transparent Pricing & Licensed Voices for Your TTS Needs

Frequently asked questions

Who runs this site?

VoxLocale is an independent storefront for the TTS API. We operate as a standalone entity, distinct from major tech brands. Our team manages the infrastructure, pricing, and support for the text-to-speech service available at playyy9.com, ensuring a direct and transparent relationship with localization agencies and developers.

Are the voices licensed?

Yes. Our eight voice presets are based on licensed recordings from LibriTTS-R (CC BY 4.0) and public-domain audiobook readings from LibriVox. This ensures that the synthetic speech generated by our API is built upon properly sourced audio data, providing a reliable foundation for your commercial and non-commercial dubbing projects.

Is my text used for training?

No. Input text is used exclusively to produce the audio file for your request. We do not use your submitted text for training our models or improving future generations. Only request metadata, such as time, character count, and status, is retained for billing and usage tracking purposes.

Do you have an SLA?

We do not offer a Service Level Agreement (SLA) or an uptime guarantee. Our service is provided on a best-effort basis. While we strive for reliability, we do not contractually promise specific availability percentages or compensation for downtime. You can check our current status and documentation for more technical details.

How do I contact support?

Support is available via email only. We do not have a phone number, live chat, or physical office for walk-ins. Please send your inquiries to our support email address. We aim to respond to all messages promptly, but please allow for standard processing times depending on query volume.

Are you affiliated with OpenAI?

No. We are not affiliated with OpenAI, despite our API endpoint structure being compatible with the OpenAI speech endpoint. You can use the official OpenAI SDKs by changing the base_url to our API domain. We are an independent provider of text-to-speech services, separate from any other major brand.

Do you offer refunds?

Failed requests are refunded automatically. If synthesis fails, the charge is returned in full. For other cases, refunds are handled via email support. We do not have a self-service refund portal. Your balance does not expire, so you can use your credit for future successful requests at any time.

Is the API GDPR compliant?

We do not provide a specific GDPR certification or certificate. While we process data in a manner consistent with standard privacy practices, we do not make explicit legal claims about GDPR compliance status. For specific data processing agreements or detailed legal interpretations, please contact our support team via email.

Who owns the audio?

You own the audio files generated by your requests. Since we do not store the audio files after delivery, you retain full control over your generated content. The voices are based on licensed data, but the resulting synthetic speech files are yours to use according to our terms of service.

Do you store audio files?

No. Generated audio is returned in the response and is not stored on our servers. Input text is also not stored long-term, only metadata like time and character count is kept for billing. This ensures that your specific audio outputs are transient and remain under your control immediately after generation.

Can I use the API commercially?

Yes. Our API is designed for commercial use, including by localization and dubbing agencies. There are no restrictions on using the generated audio for commercial projects. You simply need a valid API key and sufficient balance. We charge based on characters processed, making it scalable for high-volume commercial workflows.

Do you have a physical address?

We do not list a physical office address for customer visits. Our support is handled entirely via email. As an independent digital storefront, we operate remotely. If you require specific legal address details for invoicing or contracts, please reach out to our support team via email for assistance.

How do I verify the license?

Our voices are based on LibriTTS-R (CC BY 4.0) and LibriVox public-domain recordings. You can verify this by reviewing our documentation or contacting support. The inaudible watermark in generated files marks them as synthetic speech.

Is the editorial team human?

Our team is human. We manage the API, pricing, and support directly. Our editorial and support staff handle inquiries, verify facts, and ensure the accuracy of our documentation and pricing information for our localization agency customers.

Who We Are

Sound wave illustration for: Who We Are

VoxLocale is an independent storefront for a cloud text-to-speech API. We are an editorial team dedicated to providing reliable voice-over infrastructure for localization agencies. Our goal is to help you scale your dubbing pipeline without the overhead of hiring extra talent.

Editorial Team

Editorial Team

We curate and maintain the API infrastructure, ensuring consistent quality across all 23 supported languages and 8 distinct voices. We focus on transparency, offering clear pricing and straightforward technical documentation.

Focus on Agencies

Focus on Agencies

Our platform is built for agencies that need to automate voice-over production. With support for character-based billing and multiple format outputs, we integrate seamlessly into your existing localization pipeline, allowing you to handle high-volume dubbing projects efficiently.

Independent Storefront

Independent Storefront

We operate independently and are not affiliated with OpenAI, ElevenLabs, or other major brands. This means you get direct access to our specific engine and pricing structure without intermediary markups or conflicting brand promises.

Our Voices

Sound wave illustration for: Our Voices

We generate audio using the LibriTTS-R dataset, a collection of spoken text recordings. This data forms the basis of our eight distinct voice presets. Each preset, from the warm narrator Aria to the energetic promo voice Felix, is derived directly from these source recordings.

LibriTTS-R Source

LibriTTS-R Source

Our eight voice presets—Aria, Nova, Luna, Sage, Felix, Milo, Atlas, and Orion—are built entirely from the LibriTTS-R dataset. This ensures that every generated file originates from real human speech patterns rather than synthetic interpolation.

CC BY 4.0 License

The underlying dataset is licensed under Creative Commons Attribution 4.0 International. This means you can use the generated audio commercially without worrying about complex royalty structures, provided you attribute the original data source as required by the license terms.

Public Domain Recordings

Many of the source recordings come from LibriVox public-domain audiobook readings. This historical foundation gives our voices a natural, established quality that works well for localization and dubbing agencies needing consistent, clear narration across 23 languages.

Data Policy

Sound wave illustration for: Data Policy

Your input text is processed exclusively to generate the requested audio file. We do not use your scripts for model training, ensuring your creative content remains distinct from our engine’s development data.

Request metadata, including timestamp, character count, and status, is retained solely for billing accuracy and usage tracking. Generated audio is returned in the response and not stored on our servers.

Input Not Trained

We treat your text as a transient input. Unlike some providers, we do not ingest your voice-over scripts into our training datasets. This ensures your unique localization content remains proprietary and is not used to influence future voice models.

Metadata Kept for Billing

To support our character-based pricing model, we store minimal request metadata. This includes the time of request, the number of characters processed, and the final status of the synthesis. This data is strictly used to calculate your invoice and verify usage limits.

No Long-Term Storage

Once the audio file is delivered to your client, we do not retain a copy of the generated audio file. Your input text is also not kept for long-term archival purposes. This reduces data exposure and simplifies compliance for your agency’s client deliverables.

Technical Limits

Sound wave illustration for: Technical Limits

We deliver audio via standard REST endpoints, meaning you receive the complete file only after synthesis finishes. There is no WebSocket or streaming support for real-time partial audio delivery.

No Streaming

Our API returns the full audio file upon completion. This design is reliable for batch processing but does not support real-time streaming of audio chunks.

No SSML

We do not support Speech Synthesis Markup Language (SSML). You cannot use tags to control pauses, pronunciation, or emphasis within the input text.

No Custom Cloning

We offer eight distinct voice presets but do not provide custom voice cloning for your clients. You cannot upload a reference sample to create a new voice model.

Technical Limits

Contact Us

Sound wave illustration for: Contact Us

We prefer asynchronous communication to ensure every question receives a thorough, documented response from our team. You can reach us at [email protected] for any inquiries regarding your account, billing, or technical implementation.

Email Support

Our email support is the primary and only channel for customer service. We aim to provide clear, specific answers without the noise of live sessions. This approach allows us to maintain detailed records of your requests, ensuring continuity if you follow up later.

  • Primary support channel
  • Detailed response history
  • Asynchronous workflow

No Live Chat

We do not offer live chat widgets on this site. There is no real-time agent waiting to answer immediate questions. This decision helps us keep operational costs low and avoids the pressure of instant responses for complex technical queries.

No Phone

There is no phone number to call for support. You will not receive outbound calls, nor can you call in for urgent issues. All communication remains text-based via email, ensuring a clear audit trail for your records.

Disclaimer

Sound wave illustration for: Disclaimer

VoxLocale operates as an independent storefront for the text-to-speech API described here. We are not affiliated with OpenAI, ElevenLabs, Google, Amazon, Microsoft, or any other brand mentioned in comparisons. Our API endpoint and SDK compatibility mimic OpenAI’s structure, but we are a separate entity.

Not Affiliated with OpenAI

While our API endpoint structure mirrors OpenAI’s speech endpoint, VoxLocale is an independent provider. We do not use OpenAI’s models, infrastructure, or branding. Our 8 voices are based on LibriTTS-R recordings, distinct from any commercial voice cloning services offered by major tech platforms.

No SLA Guarantee

We do not offer a Service Level Agreement (SLA) or uptime guarantee. Requests are processed sequentially, so under load, synthesis may wait in a queue. We strive for reliability, but there is no contractual commitment to specific response times or availability windows.

No Certifications

We do not hold SOC 2, HIPAA, or GDPR certifications. Our data policy states that input text is not used for training and generated audio is not stored long-term. Request metadata is kept solely for billing purposes. We are not enterprise-contracted.

Listen to the 8 voices

Each sample below was generated by this API from the same sentence. Unlike many consumer-grade platforms, we do not use your input text to train our models.

Avatar of the voice aria
ariafemale
Avatar of the voice nova
novafemale
Avatar of the voice luna
lunafemale
Avatar of the voice sage
sagefemale
Avatar of the voice felix
felixmale
Avatar of the voice milo
milomale
Avatar of the voice atlas
atlasmale
Avatar of the voice orion
orionmale

23 languages

Any voice speaks any of these languages.

Sources and further reading

  1. Wikipedia
  2. LibriTTS-R corpus (OpenSLR 141)
  3. openai-node on GitHub
  4. ISO 639 language codes
  5. curl documentation
  6. W3C WAI: making audio and video accessible
  7. OpenAI API reference: create speech
  8. openai-python on GitHub
  9. Python documentation
  10. TRON developer hub: TRC-20
  11. Tether (USDT)
  12. MDN: Web Speech API

More on this site