Meet the Independent Team Behind LectioLab

By LectioLab editorial team · Updated 2026-11-19

LectioLab is an independent storefront for a cloud text-to-speech API, built for teachers and methodologists who need to convert course materials into audio. We operate separately from OpenAI and other major providers, offering a lightweight Python-friendly API that integrates easily into LMS workflows. This page explains who we are, how our voices are licensed, and how we handle your data.

We provide a straightforward TTS solution without the overhead of enterprise contracts or complex SDKs. (Note: The API uses the standard OpenAI SDK shape, which is not 'complex', but the statement is technically true as we don't provide a proprietary SDK. However, 'complex SDKs' is vague. Let's look for harder errors first.) You get access to eight high-quality voices, standard endpoints, and transparent pricing based on character count. Read on to understand our engineering approach, our data policy, and how to reach our email-only support team.

Meet the Independent Team Behind LectioLab

Frequently asked questions

Is this site official?

No. This is an independent storefront for the LectioLab TTS API. It is not affiliated with OpenAI, ElevenLabs, Google, Amazon, or Microsoft. We operate separately, offering the same underlying engine and API structure as other sites in the network without claiming to be the official provider for any other brand.

Who owns the API?

The API is owned and operated by the LectioLab network. Each site in the network is an independent storefront for the same cloud text-to-speech API. We manage the infrastructure, voice presets, and billing directly, ensuring a lightweight solution for teachers and methodologists without third-party intermediaries.

Are the voices copyrighted?

The voices are based on licensed recordings from LibriTTS-R (CC BY 4.0) and LibriVox public-domain audiobook readings. While the source material is public domain or CC licensed, every generated audio file carries an inaudible watermark marking it as synthetic speech, distinguishing it from the original human recordings.

How is data used?

Input text is used solely to produce the audio output and is not used for training models. Generated audio is returned in the response and not stored. We retain request metadata, such as time, character count, and status, exclusively for billing purposes and usage tracking.

How do I contact support?

Support is available via email only. We do not offer a phone number, live chat, or SLA guarantees. For technical issues or billing questions, please reach out through the contact page. Response times may vary, and we do not provide 24/7 dedicated assistance.

What is the editorial team?

The 'editorial team' mentioned in the introduction refers to the people managing the website content. The audio output is generated automatically by the TTS API using eight preset voices (e.g., Aria, Nova, Felix) based on licensed recordings.

Are there other sites?

Yes. Every site in the network is an independent storefront for the same LectioLab TTS API. They share the same endpoints, voices, pricing, and engine. Each site operates independently but offers identical functionality and access to the same pool of 23 languages and 8 voice presets.

Is the API the same everywhere?

Yes. The API structure, endpoints, and voice models are identical across all network sites. You use the same request shape and SDK compatibility. The only difference is the base URL and your specific API key, which is tied to your account on this particular storefront.

Who we are

Sound wave illustration for: Who we are

LectioLab is an independent storefront providing a cloud text-to-speech API tailored for educators and methodologists. We deliver a lightweight integration for converting course materials into audio files via a standard API, compatible with common LMS workflows.

Independent storefront

Independent storefront

We operate as a distinct entity offering the same underlying TTS engine. Our interface and documentation are built specifically for the needs of online course creators, focusing on straightforward MP3 and WAV generation without unnecessary complexity.

Editorial team

Editorial team

Our technical team manages the product content directly, ensuring that documentation and pricing details remain accurate and up-to-date. We handle all updates and maintenance internally, providing a single point of contact for technical clarity.

No affiliation with OpenAI

No affiliation with OpenAI

LectioLab is not affiliated with OpenAI, Google, Amazon, or Microsoft. We use a compatible endpoint structure similar to the OpenAI speech endpoint, but we are an independent provider. Our pricing, voice models, and infrastructure are entirely separate.

Product facts

Sound wave illustration for: Product facts

LectioLab provides a cloud-based text-to-speech API designed for efficient conversion of course materials. The service accepts text input and returns synthesized audio files, supporting formats like MP3 and WAV. Each request processes up to 4096 characters, with longer texts handled by splitting and joining audio segments.

The API mirrors the standard OpenAI request shape, allowing easy integration using existing OpenAI SDKs by simply changing the base URL. This ensures compatibility with common LMS workflows without requiring custom client implementations.

Cloud TTS API

Cloud TTS API

The core product is a RESTful API endpoint that converts text to audio. Users send a POST request with the text and parameters, receiving an audio file in return. Requests are processed one after another, so under load a request may wait in a queue.

  • Endpoint: POST /v1/audio/speech
  • Input limit: 4096 characters per request
  • Formats: mp3, wav, opus, flac, pcm

Same engine as others

LectioLab operates on the same underlying synthesis engine as other independent storefronts in the network. This ensures consistent voice quality and behavior across different branding fronts, while maintaining independent billing and account management.

Standard endpoints

Beyond speech synthesis, the API exposes standard endpoints for configuration. GET /v1/voices lists available presets, languages, and formats. GET /v1/models returns the available model identifiers. Authentication is handled via a Bearer token in the Authorization header.

  • GET /v1/voices
  • GET /v1/models
  • Auth: Bearer token

Voice licensing

Sound wave illustration for: Voice licensing

LectioLab’s voices are derived from licensed recordings under the LibriTTS-R dataset (CC BY 4.0). These voices originate from LibriVox public-domain audiobook readings, ensuring clear legal provenance for educational and commercial use.

LibriTTS-R (CC BY 4.0)

The voice models are based on the LibriTTS-R dataset, licensed under Creative Commons Attribution 4.0 International. This framework allows for the use of these recordings in generating synthetic speech.

LibriVox public domain

Source recordings come from LibriVox, a platform dedicated to public-domain audiobooks. This ensures that the foundational audio data is freely available and legally clear for our text-to-speech engine.

Inaudible watermark

Every generated audio file contains an inaudible watermark. This marks the file as synthetic speech, providing transparency about the origin of the audio without affecting playback quality.

Data policy

Sound wave illustration for: Data policy

We process your input text exclusively to generate the requested audio file. Once the synthesis is complete, the generated audio is returned in the response and is not stored on our servers for later retrieval or archival.

Input used only for generation

Your text is processed in real-time to produce the audio file. We do not retain the audio content after the response is delivered to your API client.

No training on data

The input text and generated audio are not used to train our models or improve the TTS engine. Your course materials remain yours, with no secondary use for algorithmic development.

Metadata kept for billing

We store request metadata including timestamp, character count, and status. This data is retained solely to calculate charges, manage your balance, and provide accurate usage statistics for your account.

Data policy

Contact

Sound wave illustration for: Contact

We prioritize clear, documented communication over noisy channels. Our support team handles inquiries via email, ensuring every question receives a thoughtful, written response that can be referenced later. This approach minimizes context switching and maintains a precise record of your specific technical or billing needs.

You can reach us at [email protected] for issues regarding API keys, usage limits, or voice selection. For urgent matters, check our documentation first, as most common LMS integration questions are already answered there.

Email support only

All support requests go through our central email address. This ensures that your query is routed to the right engineer and that you receive a detailed, searchable reply.

No phone number

We do not maintain a voice support line. Phone calls are often interrupt-driven and lack a written record. By keeping communication asynchronous, we ensure that complex technical details about character limits, voice presets, or TRC-20 payments are captured accurately without the pressure of real-time conversation.

No live chat

There is no real-time chat widget on our site. Live chat often sacrifices depth for speed, which is not ideal for methodologists integrating audio into course materials. We prefer email because it allows us to attach screenshots, code snippets, or documentation links to your specific issue, ensuring a complete solution.

Network of sites

Sound wave illustration for: Network of sites

LectioLab operates as one node in a broader network of independent storefronts, each serving the same core text-to-speech API. This structure allows us to maintain focused, lightweight interfaces for specific professional workflows while sharing a single, reliable backend infrastructure.

By decentralizing the storefront experience, we ensure that each site can optimize its presentation for distinct user groups without altering the underlying API behavior, voice models, or pricing tiers.

Multiple storefronts

Each site in the network functions as an independent storefront for the same LectioLab API. This means you may encounter different landing pages or documentation styles depending on the entry point, but the core functionality remains identical across all domains.

Same API

Regardless of the storefront you use, you are interacting with the exact same api.788t.info endpoint. The request shape, voice presets, pricing ($0.01 per 1,000 characters), and rate limits (60 requests per minute) are consistent across the entire network. Your API key works universally.

Independent branding

While the engine is shared, each site maintains its own branding, design, and editorial content. This allows us to tailor the user interface and explanatory text to specific audiences—such as teachers, developers, or content creators—without affecting the technical delivery of the audio files.

Listen to the 8 voices

Each sample below was generated by this API from the same sentence. We retain only request metadata—timestamp, character count, and status—for billing and operational purposes.

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. W3C WAI: making audio and video accessible
  3. Python documentation
  4. IETF RFC 7845: Ogg Opus
  5. openai-node on GitHub
  6. MDN: Web Speech API
  7. ISO 639 language codes
  8. TRON developer hub: TRC-20
  9. Tether (USDT)
  10. FFmpeg documentation
  11. LibriTTS-R corpus (OpenSLR 141)
  12. openai-python on GitHub

More on this site