Meet the Team Behind Our Text-to-Speech Engine

By LingoCast editorial team · Updated 2026-11-19

This page explains the technical and legal foundations of the LingoCast text-to-speech API, built specifically for game developers and content creators who need reliable, programmable voice lines for NPC dialogue and in-game audio pipelines. We provide a standard-compliant API that integrates directly into your existing audio generation workflows without requiring custom middleware or proprietary SDKs.

You will find details on our voice licensing sources, data handling policies, infrastructure setup, and support channels. Since we are an independent storefront, we maintain full transparency regarding our engineering choices, limitations, and the specific constraints of our cloud-based TTS service. Read on to understand exactly how our API fits into your development stack.

Meet the Team Behind Our Text-to-Speech Engine

Frequently asked questions

Who runs this site?

LingoCast is an independent storefront for a cloud text-to-speech API. We operate this specific instance at vip0.info. Each site in our network is an independent storefront for the same underlying TTS API, providing a standard-compliant interface optimized for game developers and content creators who need reliable, programmable voice lines.

Are you affiliated with OpenAI?

No. We are not affiliated with OpenAI, ElevenLabs, Google, Amazon, Microsoft, or any other brand mentioned in comparisons. Our API endpoint shape matches the OpenAI speech endpoint, allowing you to use official OpenAI SDKs by simply changing the base_url. We are a distinct, independent provider.

Where do the voices come from?

Our eight voice presets are based on licensed recordings from LibriTTS-R (CC BY 4.0) and public-domain audiobook readings from LibriVox. These recordings form the basis for our voice presets. Every generated file also carries an inaudible watermark that marks it as synthetic speech for identification purposes.

Is the data used for training?

No. Your input text is used only to produce the audio and is not used for training our models. We retain request metadata, such as time, character count, and status, strictly for billing purposes. Your raw text data is not repurposed for model improvement or other uses.

How do I contact support?

Support is available via email only. We do not offer phone support or live chat. You can reach our team through the contact page or the email address provided in your account dashboard. We aim to respond to inquiries efficiently, but response times may vary based on volume.

Do you have a phone number?

No. We do not offer a phone number for customer support. All communication is handled via email. This allows us to maintain a lean, engineering-focused operation without the overhead of voice support lines, ensuring our resources remain dedicated to API reliability and infrastructure maintenance.

Is there a live chat?

No. There is no live chat widget on our site. Support is conducted exclusively through email. This approach ensures that every support ticket is documented and can be referenced later if needed, providing a clear audit trail for any issues you encounter with your API usage.

Do you offer voice cloning?

No. We do not offer custom voice cloning for customers, nor do you upload your own voice. We provide eight fixed presets (Aria, Nova, Luna, Sage, Felix, Milo, Atlas, Orion). If you need a specific voice, you must use one of our available presets.

What is the data policy?

Input text is used only to produce the audio and is not used for training. Generated audio is returned in the response and not stored on our servers. Request metadata (time, characters, status) is kept for billing purposes only. We do not share your data with third parties.

Are the voices public domain?

The underlying recordings are from LibriVox public-domain audiobook readings, licensed under CC BY 4.0 via LibriTTS-R. However, the generated synthetic audio files are distinct products. Each file carries an inaudible watermark marking it as synthetic speech.

Do you store audio files?

No. Generated audio is returned in the API response and is not stored on our servers. We retain request metadata, such as timestamp, character count, and status, for billing and troubleshooting purposes. You are responsible for downloading and storing the audio files you generate via the API.

Is the API open source?

No. We do not provide an official SDK of our own. You can use the official OpenAI SDK by changing the base_url, or use plain HTTP requests.

Editorial Team

Sound wave illustration for: Editorial Team

LingoCast is an independent storefront for a single text-to-speech API. We operate separately from the underlying infrastructure providers and do not function as an official agent for any major tech brand. Our role is limited to distribution, billing, and key management for the API endpoint at api.vip0.info.

Team Role

Team Role

Our team manages the storefront, handles USDT top-ups on the TRON network, and issues API keys. We do not develop the synthesis engine or maintain the servers. The engine and voice models are provided by a third-party infrastructure provider; we simply route requests and manage account balances.

Editorial Focus

Editorial Focus

We focus on providing accurate, factual documentation for game developers and content creators. All pricing, rate limits, and voice descriptions are verified directly against the API specification. We avoid marketing hype, ensuring that features like the 8 voice presets and 23 supported languages are described exactly as they function.

Independence

Independence

LingoCast is not affiliated with OpenAI, ElevenLabs, Google, or Amazon. We do not use their branding or SDKs exclusively; we support standard HTTP requests compatible with the OpenAI speech endpoint structure. Our independence allows us to offer direct USDT payments without the overhead of traditional enterprise billing contracts.

  • Independent storefront entity
  • No affiliation with major cloud providers
  • Direct billing via USDT (TRC-20)

Voice Licensing

Sound wave illustration for: Voice Licensing

LingoCast’s voice synthesis engine relies on eight presets derived from licensed recordings in the LibriTTS-R dataset. These voices are built from public-domain audiobook readings, ensuring a clean, legally sound foundation for commercial game audio pipelines without hidden royalty burdens.

LibriTTS-R Source

LibriTTS-R Source

The audio models are sourced directly from the LibriTTS-R dataset, which provides high-quality speech data originally recorded for machine learning research. This dataset forms the core training material for our eight voice presets, including Aria, Nova, and Atlas.

CC BY 4.0 License

LibriTTS-R is released under the Creative Commons Attribution 4.0 International (CC BY 4.0) license. This allows us to use the recordings for commercial purposes, including in-game NPC dialogue, provided proper attribution is maintained in our documentation.

  • Commercial use permitted
  • Attribution required
  • No additional licensing fees

LibriVox Origin

The underlying recordings originate from LibriVox, a platform of public-domain audiobooks read by volunteers. These readings provide the natural prosody and clarity we synthesize into our API responses, ensuring consistent audio quality across all 23 supported languages.

Data Policy

Sound wave illustration for: Data Policy

LingoCast processes input text strictly to generate the requested audio file. Once synthesis completes, the generated audio is returned in the response and is not stored on our servers. Your raw text data is used solely for the immediate production of the voice output.

We do not use your input text or generated audio to train our models or improve the voice engines. The voices are derived from licensed recordings, and your specific content remains isolated to your API usage.

Input Usage

Text sent via the API is processed in real-time to produce the audio response. We do not retain the audio files after delivery, ensuring your game dialogue or narration remains ephemeral unless you save it.

The input text is not archived for long-term analysis. It serves only as the source material for the TTS engine to generate the specific audio format you requested (mp3, wav, opus, flac, or pcm).

No Training

Your text inputs and resulting audio files are not used to train the underlying TTS models. The voice presets (e.g., Aria, Nova, Felix) are based on fixed licensed recordings from LibriVox and do not evolve based on your specific content.

This ensures that your unique game narratives or content creator scripts remain distinct from the general training data of other users, maintaining the integrity of your specific audio assets.

Metadata Storage

We retain request metadata—including timestamp, character count, status, and model used—strictly for billing and usage verification. This data allows us to accurately calculate charges based on the $0.01 per 1,000 characters rate.

This metadata is kept only as long as necessary for billing cycles and dispute resolution. It does not include the actual text content or audio files, preserving your creative data while ensuring accurate billing.

  • Timestamp of request
  • Character count processed
  • Request status (success/fail)
  • Model used (tts-1 or tts-1-hd)

API Infrastructure

Sound wave illustration for: API Infrastructure

LingoCast operates as a cloud-native text-to-speech API designed for low-latency game audio pipelines. We handle the infrastructure so you can focus on integrating voice lines into your engine without managing servers.

Our architecture supports standard HTTP requests, ensuring compatibility with existing game audio middleware. This allows seamless integration into NPC dialogue systems without requiring custom drivers or heavy SDKs.

Cloud Hosting

Our API runs on scalable cloud infrastructure, ensuring consistent availability for production builds. Requests are processed sequentially, with typical generation speeds matching real-time audio output for long texts.

Standard Endpoint

We use a standard-compliant endpoint: POST https://api.vip0.info/v1/audio/speech. This matches the OpenAI speech endpoint shape, allowing you to use official OpenAI SDKs by simply changing the base_url to https://api.vip0.info/v1.

  • Supports tts-1 and tts-1-hd models
  • Accepts JSON bodies with standard fields
  • Returns audio files in mp3, wav, opus, flac, or pcm

No Custom SDK

We do not provide a proprietary SDK. Use any HTTP client or the OpenAI SDK. This avoids vendor lock-in and lets you integrate TTS directly into your game’s audio pipeline with minimal code.

API Infrastructure

Support Channel

Sound wave illustration for: Support Channel

LingoCast operates with a lean, engineering-focused structure. Our support infrastructure is designed to handle technical queries and billing details without the overhead of large call centers, ensuring that every interaction is documented and traceable.

Email Only

We handle all inquiries via email at [email protected]. This channel allows us to maintain detailed records of your account issues and billing questions, ensuring nothing gets lost in a queue. We aim to respond within one business day.

No Phone

There is no phone number for LingoCast support. This eliminates voice ticket latency and allows you to reference exact error codes or request payloads directly in your message.

No Live Chat

We do not offer live chat widgets. This ensures that support staff can focus on resolving complex API integration issues without context-switching between concurrent chat windows.

Product Limits

Sound wave illustration for: Product Limits

LingoCast provides a deterministic TTS API optimized for game pipelines. Our eight voice presets are fixed, derived from licensed LibriTTS-R recordings. We do not offer custom voice cloning, upload-your-own-voice features, or emotion tags. The voices are static, ensuring consistent character audio without the variability of AI-generated clones or the need for training data.

Our API returns standard audio files via HTTP. We do not support streaming, WebSocket connections, or real-time partial audio delivery. SSML markup is not parsed; language and speed are controlled via simple request parameters. These limits keep the endpoint lightweight and reliable for integrating NPC dialogue into Unity, Unreal, or custom engines.

No Streaming

We deliver complete audio files upon synthesis completion. There is no WebSocket endpoint for partial audio chunks or real-time streaming.

This design suits turn-based dialogue or pre-generated voice lines where immediate millisecond-level latency is less critical than reliability.

  • No WebSocket support
  • No partial audio chunks
  • Standard HTTP response

No SSML

The API does not parse SSML tags for pronunciation or prosody control. Language detection is automatic or set via the language field.

For precise control, adjust the speed parameter (0.25–4.0) or choose the appropriate voice preset.

No Voice Cloning

We do not offer custom voice cloning or upload-your-own-voice features. The eight available presets are fixed. These voices are derived from licensed LibriTTS-R recordings, ensuring legal clarity without the variability of AI-generated clones.

Users select from Aria, Nova, Luna, Sage, Felix, Milo, Atlas, or Orion. No training data or custom model generation is available.

Listen to the 8 voices

Each sample below was generated by this API from the same sentence. Avoid these three frequent errors to ensure consistent voice generation and accurate billing.

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. MDN: Web Speech API
  3. Python documentation
  4. W3C WAI: making audio and video accessible
  5. OpenAI API reference: create speech
  6. openai-python on GitHub
  7. TRON developer hub: TRC-20
  8. LibriTTS-R corpus (OpenSLR 141)
  9. curl documentation
  10. FFmpeg documentation
  11. LibriVox public-domain audiobooks
  12. Tether (USDT)

More on this site