Frequently asked questions
Who runs Readly API?
Readly API is an independent storefront for a cloud text-to-speech API. We help indie developers integrate high-quality TTS into SaaS notifications and interfaces without enterprise overhead. Our API is simple, predictable, and built for developers who value honesty over hype. We are not affiliated with OpenAI, ElevenLabs, or any other major brand.
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 foundation ensures high-quality synthetic speech while respecting the original creators' rights. You can use these voices in your applications without worrying about complex licensing agreements for the base audio sources.
Is my data private?
Your input text is used only to produce the audio and is not used for training. We keep request metadata, such as time, characters, and status, strictly for billing purposes. This ensures transparency in your usage costs without retaining your actual content for other purposes. Your data remains yours.
Do you store audio?
No. Generated audio is returned in the response and is not stored on our servers. Once the audio file is delivered to your client, we do not retain a copy. This minimizes data retention and ensures that your generated speech files are transient, existing only for your immediate use.
How do I contact support?
Support is available by email only. We do not offer a phone number or live chat. You can reach us via the contact page or the email link provided in your account dashboard. We aim to respond to your inquiries promptly to help you resolve any issues with the API.
Do you accept credit cards?
No, we do not accept credit cards, PayPal, or offer subscriptions. Top-ups are made using USDT on the TRON network (TRC-20) only. The minimum top-up amount is $5, and your balance is credited automatically within minutes after the transfer. This method keeps our overhead low and prices predictable.
Is there a phone number?
No, there is no phone number for Readly API. All support interactions happen via email. This allows us to maintain a lean, indie-focused operation without the overhead of call centers. You can find our email address on the contact page or within your account dashboard for direct assistance.
Do you have an SLA?
No, we do not offer an SLA or an uptime guarantee. As an indie API, we prioritize simplicity and honesty over enterprise contracts. While we strive for reliability, our service is provided as-is. This approach keeps our pricing straightforward and avoids the complexities associated with formal service level agreements.
Are you affiliated with OpenAI?
No, we are not affiliated with OpenAI. Our API endpoint structure mimics the OpenAI speech endpoint for ease of use, but we are an independent service. Our voices are based on LibriVox recordings, not OpenAI models. We are a separate entity offering a different engine with different pricing and features.
What is the watermark?
Every generated audio file carries an inaudible watermark that marks it as synthetic speech. This helps identify the audio as AI-generated without affecting the listening experience. It is a standard feature of our technology to ensure transparency about the origin of the voice, distinguishing it from human-recorded audio.
Can I use voices commercially?
Yes, you can use the generated audio commercially. Since the base recordings are from LibriVox (public domain) and LibriTTS-R (CC BY 4.0), you have broad rights to use the output. There are no additional licensing fees for commercial use, making it ideal for SaaS notifications, interfaces, and other commercial applications.
Is the API open source?
No, the API itself is not open source. We provide a simple REST API that works with standard HTTP requests or the OpenAI SDK. While the underlying voice data sources are open, our infrastructure and specific implementation details remain proprietary. We focus on delivering a reliable, managed service rather than open-source code.
Do you offer refunds?
Failed requests are free, so you are not charged for them. If a synthesis fails, the charge is returned in full. For other cases, we do not have a formal refund policy beyond this.
How do I report a bug?
You can report bugs by contacting us via email. Use the contact page or the email link in your dashboard. Include details like the request ID, voice used, and the issue you encountered. Our team reviews these reports to improve the API. We appreciate your help in making Readly API better.
Who We Are
Readly API is an independent storefront for the same text-to-speech engine, operated by a small editorial team that understands the daily grind of indie development. We built this interface because we needed a reliable, honest TTS solution for our own SaaS notifications and interfaces, one that delivers high-quality audio without the complexity of enterprise-grade platforms.
Independent editorial team
We are a small, focused team of developers and writers who value clarity over marketing fluff. Our decisions are driven by developer feedback and practical usage, ensuring the API remains simple, predictable, and easy to integrate into your projects.
Built for indie developers
Our API is designed for developers who need to integrate TTS into SaaS notifications and interfaces without wrestling with complex configurations. We provide straightforward endpoints and clear documentation, so you can generate audio files quickly and move on to building your product.
No enterprise overhead
We offer no unnecessary seats, subscriptions, or minimum spend requirements. You only pay for what you use, with transparent pricing and no hidden fees. This approach keeps our service accessible and affordable for indie developers and small teams who need reliable speech synthesis.
Voice Licensing
Readly API’s voice models are grounded in transparency. Our eight presets are derived from licensed recordings, ensuring that the synthetic speech you generate has a clear, verifiable lineage. We do not hide behind proprietary black boxes; instead, we rely on open, well-documented sources for our audio data.
Based on LibriTTS-R (CC BY 4.0)
The core of our voice engine is the LibriTTS-R dataset, released under the Creative Commons Attribution 4.0 International license. This dataset provides a robust foundation for natural-sounding speech synthesis, allowing us to deliver high-quality audio without the legal ambiguity of proprietary training data.
- Standardized for consistent quality across all 8 voices
- Clear attribution requirements for downstream uses
Recordings from LibriVox
Our audio samples originate from LibriVox, a massive community-driven project where volunteers record public domain books. By leveraging these existing recordings, we ensure that our voices sound natural and human-like, avoiding the uncanny valley often associated with purely synthetic voice generation.
Public domain audiobook readings
Since the source materials are in the public domain, the underlying performances are free from complex royalty structures. This simplicity translates to predictable pricing for you and clear licensing terms for the voices used in your applications, from narration to interface prompts.
Data Privacy
Readly API was built by indie developers for indie developers, prioritizing transparency and simplicity. We avoid the complexity of enterprise overhead, offering a straightforward TTS solution that fits seamlessly into your SaaS notifications and interfaces without hidden costs or confusing tiers.
Input text not used for training
When you send text to our API, it is used exclusively to generate the requested audio file. We do not use your input data to train or improve our voice models. Your content remains yours, ensuring that your proprietary notifications or interface copy stay private and are not repurposed for our algorithmic development.
Audio not stored after response
Once the synthesis is complete and the audio file is returned in the response, we do not retain the generated audio. The file is returned in the response and not persisted on our servers for later retrieval or analysis. This ensures that your generated speech is transient and not stored long-term.
Metadata kept for billing only
We keep request metadata—such as the timestamp, character count, and status—solely for accurate billing and debugging. This data is not used for marketing or training. It exists only to ensure you are charged correctly for character usage.
Payment Methods
Readly API keeps billing simple and direct. We accept USDT on the TRON network (TRC-20) for all top-ups. Payments are processed automatically within minutes of transfer, ensuring your credit balance is ready for immediate use without waiting for manual verification.
USDT on TRON network only
USDT on TRON network (TRC-20) is the sole payment method. The minimum top-up amount is $5. Credits are added to your account automatically within minutes after the blockchain confirms your transfer.
No credit cards or PayPal
We do not accept credit cards, debit cards, or PayPal. There are no monthly subscriptions or recurring charges. You pay only for what you generate, and your balance never expires.
No invoices with VAT
Since we do not handle traditional payment processors, we do not issue invoices with VAT. Our system records transaction metadata for billing purposes, but you are responsible for your own tax reporting based on your local regulations.

Support Channels
We keep communication simple and direct. All support requests go through a single email channel, ensuring your questions are handled by the same small team that built the API. This approach avoids the complexity of enterprise support structures while maintaining clear, honest communication.
Email support only
Email remains our primary and only support method. It allows us to provide thoughtful, detailed responses to technical questions about integration, rate limits, or voice selection. You can expect a direct answer from the developers without being routed through multiple tiers of general support staff.
- Direct line to the development team
- Clear, written record of all inquiries
- No waiting in queue for basic questions
No phone number
We do not maintain a phone line. This decision reduces overhead and keeps our focus on building a reliable API rather than managing call centers. Most indie developers prefer asynchronous communication that fits into their coding workflow, allowing them to respond at their own pace.
No live chat
Unlike many SaaS platforms, we skip the live chat widget. There is no one-click support bubble to clutter your experience. If you need help, send an email. This ensures every request receives the full attention of a human developer rather than a rushed, automated response.
Limitations
We keep our promise simple: no hype, just clear limits. This transparency helps you decide if Readly API fits your workflow without hidden surprises later.
No streaming
We return complete audio files via standard HTTP responses. There is no real-time partial audio streaming, which keeps the integration straightforward for most indie developer workflows.
No SSML or custom cloning
We offer eight preset voices based on licensed recordings. There is no support for SSML, phoneme dictionaries, or custom voice cloning. You cannot upload your own voice or design new emotions.
If you need specific pronunciation or cloned voices, you will need a different solution. Our focus is on consistent, high-quality preset voices for notifications and interfaces.
No SLA or uptime guarantee
We do not provide an SLA, uptime guarantee, or enterprise contracts. Requests are processed sequentially, so under heavy load, you may experience queue delays.
Support is available via email only. There is no phone number or live chat for urgent issues. We aim for reliability but do not guarantee specific uptime percentages.
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
- curl documentation
- Python documentation
- LibriTTS-R paper (arXiv 2305.18802)
- IETF RFC 7845: Ogg Opus
- openai-python on GitHub
- Creative Commons Attribution 4.0
- LibriVox public-domain audiobooks
- LibriTTS-R corpus (OpenSLR 141)
- TRON developer hub: TRC-20
- OpenAI API reference: create speech
- W3C WAI: making audio and video accessible
