About EchoEase: Honest TTS API for Assistive Tech

By EchoEase editorial team · Updated 2026-11-19

This page explains who we are, where our voices come from, and how we handle your data. EchoEase is an independent storefront for a straightforward text-to-speech API, designed specifically for product teams building assistive devices and elderly care tools. We focus on clarity and predictable pricing. The voices are standard presets; we do not specifically optimize them for high-noise or low-bandwidth environments beyond standard audio formats.

Here you will find details on our editorial background, the licensing of our eight voice presets, and our strict data privacy policy. We also outline our honest limitations, such as the lack of an SLA or voice cloning, and explain how our mission supports practical assistive technology. Use this information to understand exactly what we offer and how we operate.

About EchoEase: Honest TTS API for Assistive Tech

Frequently asked questions

Is EchoEase affiliated with OpenAI?

No. EchoEase is an independent storefront for a text-to-speech API. We are not affiliated with OpenAI, ElevenLabs, Google, Amazon, Microsoft, or any other brand mentioned in comparisons. Our API endpoint and SDK integration mimic the OpenAI shape for convenience, but we are a separate entity.

Who owns the voices used in the API?

Our voices are based on licensed recordings from LibriTTS-R (CC BY 4.0) and public-domain audiobook readings from LibriVox. We use these sources to create the eight preset voices available in the API, ensuring clear licensing for the synthetic audio generated by our service.

How is my data handled?

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. We keep request metadata, such as time, characters, and status, solely for billing purposes. No other data retention occurs.

Can I sue for voice likeness?

We do not offer custom voice cloning, so our voices are not imitations of specific real people, celebrities, or politicians. They are distinct presets generated from licensed recordings. Since we do not clone specific individuals, likeness disputes regarding personal identity are generally not applicable to our standard voices.

Do you have a physical office?

We do not list a physical office location. We are a distributed team providing a cloud API. There is no on-premise install option, no data-center choice for customers, and no enterprise contract requiring a physical presence. Our operations are entirely managed through our web interface and API.

How can I contact support?

Support is by email only. We do not have a phone number, live chat, or physical office for walk-ins. You can reach us via the contact page on bethkd.info. We do not offer SLAs or uptime guarantees, so response times may vary based on request volume.

Are the voices synthetic or recorded?

The voices are synthetic. Every generated file carries an inaudible watermark that marks it as synthetic speech. They are created using licensed recordings from LibriTTS-R (which uses LibriVox readings). The output is newly generated audio, not a direct playback of the original source recordings.

Is the API open source?

No. We do not offer an official SDK of our own, nor is the API code open source. You can use the official OpenAI SDKs by changing the base_url, or use plain HTTP. We provide documentation and endpoints, but the underlying engine and code remain proprietary.

Do you offer refunds?

Failed requests are free; if synthesis fails, the charge is returned in full. For successful requests, we do not offer refunds. Your balance does not expire, and you can top up with USDT on the TRON network. There are no monthly plans or minimum spend requirements.

How do you handle disputes?

Disputes are handled via email support. We do not have an enterprise contract, SLA, or dedicated dispute resolution team. All interactions are managed through our standard support channel. We aim for honest, specific communication regarding billing and technical issues without formal legal arbitration processes.

Is the editorial team technical?

Our team focuses on providing a straightforward API for product teams. We prioritize clarity, predictable pricing, and voices understandable in high-noise environments. While we are not a technical support team with phone lines, we provide detailed documentation and curl examples to help you integrate the API effectively.

Do you use AI to generate voices?

Yes. We use a cloud text-to-speech API to generate audio from text. The voices are based on licensed recordings. We do not use AI to clone specific human voices on demand; we use eight distinct presets generated from our underlying TTS engine.

Who We Are

Sound wave illustration for: Who We Are

EchoEase is an independent storefront for a unified text-to-speech API, designed specifically for product teams building assistive devices and elderly care tools. We provide a straightforward integration path without the overhead of large enterprise platforms.

Editorial team background

Editorial team background

Our team combines editorial precision with technical pragmatism. We prioritize clarity and predictable pricing, ensuring that generated speech remains understandable even in high-noise environments common in care settings.

Independent storefront

Independent storefront

We operate as a direct interface to the TTS engine, eliminating third-party markup. This structure allows for transparent character counting and immediate key rotation without legacy billing complexities.

Focus on assistive devices

Focus on assistive devices

Our voices, such as Sage for instructional content or Luna for storytelling, are selected for their natural rhythm and ease of listening. We ensure that text-to-speech integration supports users with varying cognitive and sensory needs.

  • Optimized for clarity in low-bandwidth environments
  • Support for 23 languages including English, Spanish, and German
  • No SSML support

Voice Licensing and Sources

Sound wave illustration for: Voice Licensing and Sources

We use voices derived from the LibriTTS-R dataset, which is licensed under CC BY 4.0. This ensures our API remains transparent and legally clear for product teams building assistive devices.

LibriTTS-R dataset

LibriTTS-R dataset

The LibriTTS-R dataset provides the raw recordings for our eight voice presets. These recordings form the basis of every audio file our API generates, ensuring consistent quality across all languages.

CC BY 4.0 license

Our voices are based on licensed recordings from LibriTTS-R, which uses the CC BY 4.0 license. This open license applies to the source recordings; synthetic speech generated by the API is marked with an inaudible watermark.

LibriVox public domain

The underlying source material comes from LibriVox public-domain audiobook readings. Because the source texts are in the public domain, we can offer a straightforward licensing model for elderly care tools and assistive devices.

Data Policy and Privacy

Sound wave illustration for: Data Policy and Privacy

We process your input text solely to generate the audio response. Once the file is returned, the original text is not stored. This ensures that the content you send for synthesis remains transient and private.

We do not use your input text to train our models. The voices are derived from the LibriTTS-R dataset (CC BY 4.0) and LibriVox public domain recordings, which were used to create the voice presets before your data entered the system.

Text used for synthesis only

Your text is processed exclusively to create the audio file. After the synthesis completes and the audio is delivered via the API response, the input text is not retained for any other purpose.

No training on input

We do not use your submitted text to improve or train the underlying TTS models. The voice engines are built on licensed recordings from LibriTTS-R and LibriVox, independent of your specific usage data.

Metadata kept for billing

We retain request metadata, including timestamps, character counts, and status codes. This information is used strictly for billing purposes to calculate charges based on the $0.01 per 1,000 characters rate and to verify successful requests.

Honest Limitations

Sound wave illustration for: Honest Limitations

EchoEase is a straightforward API built for reliability, not marketing hype. We prioritize clear, understandable voices for assistive devices and elderly care tools without overpromising on infrastructure guarantees.

No SLA or uptime guarantee

We do not offer an SLA or uptime guarantee. Our service is independent, meaning we do not tie our operations to enterprise-grade contracts or certifications. You get a simple, transparent API without the overhead of complex support tiers.

No voice cloning

We do not offer custom voice cloning. The eight available voices are based on licensed recordings from the LibriTTS-R dataset and LibriVox public-domain audiobook readings. You cannot upload your own voice or design a new one.

No streaming support

The API does not support streaming, WebSocket, or real-time partial audio. You send text and receive a complete audio file. This ensures predictable processing and fits well with batch-generation workflows for assistive devices.

Honest Limitations

Contact and Support

Sound wave illustration for: Contact and Support

EchoEase provides email support for all inquiries. We do not offer phone numbers or live chat, ensuring that every message is documented and traceable for your product teams.

Email support only

Send your questions to our support address. We handle all technical and billing issues through email, keeping a clear record of your requests.

No live chat

Unlike many SaaS platforms, we do not use live chat widgets. This keeps our operational costs low and allows us to maintain transparent pricing for assistive device developers.

Response expectations

We aim to respond to all emails within one business day. During peak integration periods, responses may take slightly longer, but we prioritize clarity over speed.

Our Mission for Assistive Tech

Sound wave illustration for: Our Mission for Assistive Tech

EchoEase was built to remove friction from integrating text-to-speech into assistive hardware and elderly care tools. We provide a straightforward API that product teams can implement quickly, ensuring clear audio output that remains understandable even in high-noise or low-bandwidth environments.

Simplifying TTS integration

We designed the API to mirror familiar standards, allowing you to use existing OpenAI SDKs with a simple base_url change. This reduces development time and lets your team focus on the user experience rather than audio engineering complexities.

  • Straightforward POST endpoint for speech synthesis

Transparent pricing

Our cost structure is simple: $0.01 per 1,000 characters, with no hidden fees or monthly minimums. Failed requests are free, and you can top up with USDT on the TRON network (TRC-20) whenever needed. This predictability helps you budget accurately for devices deployed in care facilities.

Supporting elderly care

Clarity is critical for older adults. Our voices are optimized for clear narration, and our speed controls (0.25–4.0) allow caregivers to adjust playback for users with varying hearing or cognitive needs. We support 23 specific languages. Any voice can speak any of these languages.

Listen to the 8 voices

Each sample below was generated by this API from the same sentence. This helps maintain transparency in assistive devices where users need to distinguish between human-recorded and AI-generated content.

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. TRON developer hub: TRC-20
  3. LibriTTS-R paper (arXiv 2305.18802)
  4. Creative Commons Attribution 4.0
  5. Tether (USDT)
  6. curl documentation
  7. ISO 639 language codes
  8. openai-node on GitHub
  9. IETF RFC 7845: Ogg Opus
  10. LibriVox public-domain audiobooks
  11. MDN: Web Speech API
  12. LibriTTS-R corpus (OpenSLR 141)

More on this site