Frequently asked questions
Who runs the EchoCast website?
EchoCast is an independent storefront for the TTS API, not affiliated with major brands. Accounts are specific to playmm33.com. We operate remotely without a physical office or live chat; support is provided via email only.
Are the voices based on real people?
Yes. Our eight voice presets are based on licensed recordings from the LibriTTS-R dataset, sourced from LibriVox public-domain audiobook readings. While the voices originate from real people, each generated audio file contains an inaudible watermark to clearly mark it as synthetic speech, ensuring transparency about the audio's origin.
Is my text data used to train the AI?
No. Your input text is used exclusively to produce the requested audio file. We do not use your text for training purposes. Once the audio is generated and returned in the response, the text itself is not stored. We only retain request metadata, such as time, character count, and status, for billing purposes.
Do you store the generated audio?
No. Generated audio is returned in the API response and is not stored on our servers. We retain request metadata (time, characters, status) for billing purposes only. The audio files themselves are transient, ensuring your content remains yours immediately upon generation without long-term storage of the actual audio data on our infrastructure.
How can I contact support?
Support is available via email only. We do not offer a phone number, live chat, or physical address. For issues regarding your API key, billing, or technical questions, please send an email to our support address. We aim to respond to inquiries promptly, but all communication is handled asynchronously through email.
Is there a physical address?
No. We are a cloud-based API service with no physical office or public address. Our operations are fully remote. This structure allows us to focus resources on maintaining our API endpoints and voice engine rather than managing physical locations. You can reach our team solely through the contact email provided on our site.
Are you affiliated with OpenAI?
No. We are not affiliated with OpenAI, despite our API endpoint shape matching their speech model. Our voices, pricing, and infrastructure are entirely independent. We use the OpenAI SDK compatibility for convenience, but we are a separate entity. We do not use OpenAI’s models or branding, and our service operates independently.
Do you offer refunds?
Failed requests are free, with charges returned in full if synthesis fails. For successful requests, we do not offer traditional refunds. You can issue a new API key at any time, which instantly invalidates the old one. Top-ups via USDT on the TRON network (TRC-20) are non-expiring, allowing you to use your balance whenever needed without pressure.
Who We Are
EchoCast is an independent storefront providing a cloud text-to-speech API. We operate as a single entity for podcasters who prefer code over drag-and-drop tools, focusing on reliable, broadcast-ready audio generation for episodic content pipelines.
Independent Editorial Team
We are not a content creation business. We are an independent storefront for the same TTS API. Our role is to provide the API key and infrastructure for your audio generation, without the overhead of a larger media company.
Engineering Focus
Our priority is a straightforward, reliable API. We provide standard HTTP endpoints and OpenAI SDK compatibility, allowing you to integrate speech synthesis directly into your podcast production scripts without managing complex infrastructure.
No Corporate Affiliation
EchoCast is not affiliated with OpenAI, ElevenLabs, Google, Amazon, Microsoft, or any other brand mentioned in comparisons. We are an independent storefront, ensuring your integration remains flexible and free from vendor lock-in to a specific tech giant.
Voice Licensing
EchoCast voices are built from licensed recordings sourced from LibriTTS-R. These voices are generated from public-domain audiobook readings, ensuring that the synthetic speech retains a natural, human-like quality without requiring complex proprietary model training layers.
The audio source material is licensed under CC BY 4.0. This license covers the specific recordings used to construct the eight voice presets, providing clear legal grounding for the synthetic outputs delivered to podcasters and developers.
LibriTTS-R Source
Our eight voice presets—Aria, Nova, Luna, Sage, Felix, Milo, Atlas, and Orion—are derived directly from the LibriTTS-R dataset. This dataset consists of high-quality English audiobook readings, providing the foundational audio data for our engine's voice characteristics.
By utilizing established public-domain readings, we ensure consistent voice quality across all generations. The resulting audio files carry an inaudible watermark, marking them as synthetic speech derived from these licensed sources.
- Voices derived from LibriTTS-R dataset
- Based on public-domain audiobook readings
- Consistent synthetic voice characteristics
CC BY 4.0 License
The audio recordings used to build our voices are licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). This license allows for broad usage, including commercial applications, provided appropriate attribution is given where required.
This licensing structure supports our model of delivering reliable, broadcast-ready audio without the legal complexities often associated with celebrity voice cloning or proprietary voice models. You can use the generated audio in your podcast episodes with confidence.
Public Domain Recordings
The source material originates from LibriVox, a volunteer project providing public-domain audiobooks. These recordings are freely available and have been processed to create the distinct voice presets available in the EchoCast API.
Using public-domain recordings ensures that the core voice data is free from restrictive copyright claims. This allows for straightforward integration into your episodic content pipelines without ongoing royalty obligations.

Data Privacy
Input text is used exclusively to generate the requested audio file and is not used for model training. Once the synthesis is complete and the audio is returned in the response, the input text is not retained for any other purpose. Generated audio files are delivered directly to your client and are not stored in our long-term archives.
No Training on Input
The text you send is used exclusively for the immediate synthesis task. After the audio file is generated and returned, the input text is discarded and never used to train or improve our engine.
No Audio Storage
Generated audio is returned in the response and not stored. We do not keep your synthesized files in long-term archives for your reference or analysis, ensuring that your episodic content remains under your control from generation to distribution.
Billing Metadata Retention
Request metadata, including timestamp, character count, and status, is kept for billing purposes. This data allows us to accurately process your usage charges and manage your account balance without retaining the actual content of your scripts or the resulting audio files.
Technical Infrastructure
EchoCast operates as a cloud-based API service, delivering synthetic audio via standard HTTP requests. We do not offer on-premise installations or data-center choices, ensuring you interact with a consistent remote endpoint regardless of your infrastructure.
The system relies on standard HTTP protocols, accepting JSON bodies and returning audio files directly. This design allows you to integrate our engine into your existing pipelines using plain HTTP libraries or the official OpenAI SDK by simply adjusting the base URL.
Cloud-Based API
Our infrastructure is entirely cloud-hosted, meaning all synthesis occurs on our remote servers. You send text via POST requests to https://api.playmm33.com/v1/audio/speech, and receive audio files without managing local compute resources.
No On-Premise Option
We do not provide on-premise deployments, making it impossible to install the engine directly in your own data center. All processing happens in our cloud environment, so you rely on our availability rather than maintaining your own hardware.
Standard HTTP Protocol
The API uses standard HTTP/HTTPS for all communication. We do not maintain a proprietary SDK; you can use the OpenAI SDK or plain HTTP libraries by simply adjusting the base URL. This ensures broad compatibility with any language or framework that supports RESTful requests.

Support and Contact
We provide email support for all EchoCast users. This is our only channel for assistance; we do not maintain a live chat widget or offer a phone number for direct calls.
Email Support Only
Send your inquiries to the contact address provided on our contact page. Our team handles all questions via email, from technical integration issues to billing disputes.
No Live Chat
We do not offer real-time chat or instant messaging support. There is no live agent queue waiting for your message. All communication is asynchronous via email.
Response Times
We review incoming emails and respond as capacity allows. Response speed depends on the current volume of support requests and does not follow a fixed schedule or business-day rule.

Limitations
EchoCast is a utility API, not a managed service with contractual guarantees. We do not offer an SLA or uptime guarantee. Because requests are processed sequentially, long texts may experience queue waits during high load. Latency varies by request volume; typical generation is roughly real-time, but short phrases may take a few seconds.
No SLA Guarantee
We provide a reliable cloud API, but we do not promise specific uptime percentages or compensation for latency or queue wait times. Requests are processed one after another, so under load, your synthesis job may wait in a queue before beginning. This is standard for our architecture and does not indicate a failure of service.
No Custom Cloning
Our eight voices are based on licensed recordings from LibriTTS-R and LibriVox. We do not offer custom voice cloning, voice design, or the ability to upload your own voice. Every generated file carries an inaudible watermark marking it as synthetic speech. This ensures consistency across episodic content pipelines without the variability of cloned models.
No Mobile SDK
We provide a standard HTTP REST API compatible with the OpenAI SDK format. There is no official mobile SDK for iOS or Android, nor a WordPress plugin or browser extension. You can integrate directly via HTTP requests or use the official OpenAI SDKs by adjusting the base URL to our API endpoint.
Listen to the 8 voices
Each sample below was generated by this API from the same sentence. Stop coding and start creating your dream app with just your voice and a few simple taps.
23 languages
Any voice speaks any of these languages.
