Frequently asked questions
Who runs this site?
Lectia is an independent storefront for a text-to-speech API. We help product teams build accessible, long-form audiobooks and narrated courses without human voice actors. Our API turns your text content into natural-sounding audio at scale, operating as a standalone service distinct from major tech brands.
Are voices cloned?
No. We do not offer custom voice cloning, voice design, or the ability to upload your own voice. Our eight voices are based on licensed recordings from LibriTTS-R and LibriVox public-domain audiobook readings. Each generated file carries an inaudible watermark marking it as synthetic speech.
Is data used for training?
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. Request metadata, such as time, characters, and status, is kept solely for billing purposes.
Do you have an SLA?
No. We do not offer an SLA, uptime guarantee, or enterprise contract. Requests are processed one after another, so under load a request may wait in a queue. Typical speed is roughly real time on long texts, but short phrases take a few seconds.
How to contact support?
Support is by email only. We do not have a phone number, live chat, or on-premise install option. You can reach us via the contact page on this site for any questions regarding your account, usage, or technical details.
Are voices public domain?
Voices are based on licensed recordings: LibriTTS-R (CC BY 4.0) and from LibriVox public-domain audiobook readings. While the source material has specific licenses, the generated audio files carry an inaudible watermark that marks them as synthetic speech created by our API.
Is this 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, so their official SDKs work by changing the base_url to our API domain.
Do you store audio?
Generated audio is returned in the response and not stored. Input text is used only to produce the audio and is not used for training. We keep request metadata (time, characters, status) for billing, but the audio files themselves are transient.
What is the license?
Voices are based on licensed recordings: LibriTTS-R (CC BY 4.0) and from LibriVox public-domain audiobook readings. Generated files carry an inaudible watermark marking them as synthetic speech. We do not offer custom voice cloning or voice design features.
Is there a phone number?
No. There is no phone number, live chat, or direct line for support. All support is handled via email. We focus on providing a reliable API for product teams to build accessible content without the overhead of traditional support channels.
Do you offer enterprise?
No. We do not offer an enterprise contract, SLA, or dedicated support tiers. There are no monthly plans, seats, or minimum spend requirements. You pay per character used, with failed requests being free.
How is 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. Request metadata (time, characters, status) is kept for billing. We do not store your audio files long-term.
Is there a GDPR certificate?
No. We do not provide a GDPR certificate, SOC 2, or HIPAA certification. We are an independent storefront without enterprise contracts or on-premise install options. Data handling is straightforward: input is used for generation, and metadata is kept for billing.
Where are servers located?
We do not offer data-center choice or specify server locations. We are a cloud API service without on-premise install options. Requests are processed in our cloud infrastructure.
Who We Are
We are an independent team building a text-to-speech API for product teams creating long-form audiobooks and narrated courses. We focus on helping you scale audio production without hiring human voice actors, letting your team use our API to turn text content into natural-sounding audio at scale.
Independent Team
Our team operates independently, designing a simple API that integrates directly into your existing workflows. We are not a subsidiary of a larger tech giant, which keeps our priorities aligned with developers and product managers who need reliable, straightforward audio generation.
API Focus
We built Lectia as a cloud API first. You send text via JSON and receive audio files. This approach lets you integrate TTS into your LMS or content platform using standard HTTP requests or the OpenAI SDK, without managing complex infrastructure or waiting for custom builds.
No Fluff
We skip the enterprise jargon and unnecessary features. Our product is a straightforward text-to-speech engine with clear pricing and transparent limits. We do not promise features we do not have, such as custom voice cloning or real-time streaming, ensuring you know exactly what you are getting.
Voices License
Lectia’s eight voice presets are built from licensed recordings sourced from the LibriTTS-R dataset. These voices are based on licensed recordings: LibriTTS-R (CC BY 4.0), from LibriVox public-domain audiobook readings. This foundation allows us to provide natural-sounding speech without relying on proprietary synthetic models or celebrity voice clones.
LibriTTS-R
The LibriTTS-R dataset contains high-quality English speech data collected from public-domain audiobooks. We use these recordings as the base for our eight presets—aria, nova, luna, sage, felix, milo, atlas, and orion. Each voice retains the natural cadence and tone of the original human reader, ensuring clarity and warmth in your generated audio.
- Derived from LibriVox public-domain readings
- Eight distinct presets for diverse use cases
- Natural human cadence without robotic artifacts
CC BY 4.0
The underlying voice data is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). Every generated file carries an inaudible watermark that marks it as synthetic speech.
Public Domain
The original audiobook recordings used in LibriTTS-R are in the public domain. Combined with the CC BY 4.0 license for the dataset, this ensures a clear, low-risk foundation for your long-form content and narrated courses.
Data Policy
We built Lectia to serve product teams who value their data. When you send text for synthesis, we process it strictly to generate the audio file you need. That input text is never used to train our models or improve the engine, ensuring your course content remains yours.
No Training
Your input text is used only to produce the audio and is not used for training. We do not ingest your content to refine our voices or algorithms, keeping your proprietary course material separate from our model development.
No Storage
Generated audio is returned in the response and not stored. Once you receive the file, we do not keep a copy of the audio on our servers, giving you full control over your deliverables.
Metadata Only
Request metadata (time, characters, status) is kept for billing. We retain only the essential data needed to verify usage, calculate your charges, and ensure accurate billing for your API key.
Limits
Lectia is built for product teams who need scale without enterprise overhead. We offer a straightforward API without the complexity of service-level agreements or long-term contracts. Our focus is on delivering reliable text-to-speech generation at a predictable price, allowing you to integrate audio into your LMS or course platform easily.
No SLA
We do not offer a formal Service Level Agreement. This means there are no contractual penalties if response times fluctuate or if a request takes longer than usual during high load.
No Uptime Guarantee
While we strive for consistent availability, we do not guarantee a specific percentage of uptime. Occasional maintenance or unexpected delays may occur, and we do not compensate for them.
No Enterprise
We are not an enterprise provider. We do not offer dedicated infrastructure, custom SLAs, or volume discounts based on long-term contracts. Our pricing is flat: $10 per million characters. Failed requests are free.

Contact
We keep things simple. For any question about your account, billing, or technical integration, our team is available via email. We prioritize clear, written communication so you always have a record of the conversation and our responses.
Email Only
Send your message to [email protected] or use the contact page. We aim to reply within one business day, though response times may vary during high volume periods.
No Phone
We do not offer a phone number. Email allows us to attach relevant documentation, code snippets, or API references directly to your ticket, ensuring you get precise answers without the back-and-forth of voice calls.
No Chat
There is no live chat widget on this site. This reduces interruptions for our engineering team, allowing them to focus on building and maintaining the API infrastructure that powers your audiobooks and courses.
History
Lectia launched as an independent API to solve the high cost and slow turnaround of human narration for online courses and long-form content.
Our mission is simple: provide product teams with a reliable, scalable way to turn text into natural audio without the overhead of voice actors.
Launched
We started by focusing on the technical gaps in existing TTS solutions, ensuring our API handles long texts and multiple languages out of the box.
Mission
We help educators and product teams create accessible audiobooks and narrated courses at scale, using licensed voices that sound human but cost a fraction.
Growth
We grew by prioritizing honest pricing and straightforward documentation, allowing teams to integrate speech synthesis directly into their LMS workflows without complex contracts.
Listen to the 8 voices
Each sample below was generated by this API from the same sentence. Her pacing works well for quick tips, feature introductions, or engaging marketing-style course segments where energy is key.
23 languages
Any voice speaks any of these languages.
