TTS API Guide for Teachers: Voices, Pricing, and Languages

By Lectura editorial team · Updated 2026-11-18

This guide helps teachers and school staff use the Lectura text-to-speech API to convert lesson plans, reading materials, and announcements into audio files. You will learn how to select from eight voice presets, choose from 23 languages, and manage costs without writing code. The endpoint is compatible with standard SDKs, making integration straightforward for non-technical users.

We cover pricing structures, technical ease, and data privacy policies specific to educational workflows. You will find concrete examples for generating audio files, understanding character limits, and managing API keys. This resource is designed for educators who need a reliable, no-code solution for audio content creation without enterprise complexity.

TTS API Guide for Teachers: Voices, Pricing, and Languages

Frequently asked questions

Which TTS API is best for schools?

Lectura is designed for schools and teachers, offering a straightforward REST endpoint compatible with standard SDKs. It handles character limits and language selection automatically. The API processes requests sequentially, ensuring consistent output for lesson texts and announcements without requiring coding expertise.

Is OpenAI TTS good for education?

Lectura uses the same engine as OpenAI TTS (tts-1 and tts-1-hd) but offers a simpler integration for non-technical users. You can use the OpenAI SDK by changing the base_url to api.playnn77.com. This provides access to identical voice quality and models without OpenAI’s complex billing structure.

How does pricing compare?

Lectura charges $10 per 1 million characters, or $0.01 per 1,000 characters. Failed requests are free. Unlike competitors, we do not offer monthly plans or subscriptions. You pay only for what you use, topped up via USDT on the TRON network.

Which voice is best for reading?

For reading materials, Luna offers a soft, storytelling tone, while Sage provides a calm, instructional style. Aria is a warm, clear narrator suitable for general texts. Felix works well for energetic announcements. All voices support 23 languages and can be selected via the API.

Can I use TTS for exams?

Yes, you can generate audio for exam texts using the API. The system supports 23 languages, including English, Spanish, and German. You can specify the language code to ensure accuracy. Audio files are returned directly in the response and are not stored on our servers.

Is ElevenLabs better?

Lectura uses the same engine as ElevenLabs’ TTS-1 models but offers a simpler, no-code workflow for educators. We do not claim to be better, but we provide transparent pricing at $0.01 per 1,000 characters with no monthly fees or minimum spend requirements.

What about Google TTS?

Lectura provides comparable audio quality using the same engine technology. Unlike Google’s ecosystem, we offer a dedicated API key, simple REST integration, and direct USDT top-ups. We do not bundle with other services, making it easier to track costs for school departments.

Is there a free option?

Yes, signing in with Google gives you $0.50 of credit, valid for 7 days. This covers about 50,000 characters. Accounts created with email and password start without trial credit. You can top up with a minimum of $5 via USDT on TRON.

How many languages do I need?

We support 23 languages, including Arabic, Chinese, English, French, German, Hindi, Japanese, Spanish, and more. Any voice can speak any of these languages. If you do not set the language, it is guessed from the script, defaulting to English for Latin text.

Is audio quality important?

Lectura uses licensed recordings from LibriTTS-R and LibriVox, ensuring high-quality synthetic speech. Each file includes an inaudible watermark. The engine produces clear, natural-sounding audio suitable for educational content, announcements, and reading materials without requiring human voice actors.

Can I use TTS for podcasts?

Yes, you can generate audio for podcasts using the API. You can choose from eight distinct voices and multiple formats like MP3, WAV, and OPUS. The API handles character limits up to 4,096 per request, splitting longer texts automatically if needed.

What is the character limit?

Each API request accepts up to 4,096 characters of input text. For longer texts, split them into parts and join the resulting audio files. Spaces and punctuation count toward the character limit. Failed requests do not consume your credit.

Is streaming available?

No, streaming is not available. The API returns complete audio files after processing. Requests are processed sequentially, so under load, a request may wait in a queue. Typical speed is roughly real-time, with short phrases taking a few seconds.

Do I need an account?

Yes, you need an account to generate an API key. Sign up at /get-api-key/ using Google or email. Each account has one active key. You can issue a new key at any time, which stops the old one immediately. Balance does not expire.

Criteria for Selection

Sound wave illustration for: Criteria for Selection

Selecting the right text-to-speech API requires evaluating voice clarity, language coverage, and cost efficiency. Lectura offers eight distinct presets suitable for educational content, ensuring clear narration for lesson texts and announcements.

Voice Quality

Lectura provides eight voices based on licensed recordings, ranging from warm narrators to energetic announcers. These presets ensure consistent audio quality for student materials without requiring technical expertise.

  • Eight distinct voice presets for varied tones
  • Licensed recordings for clear, natural narration
  • Consistent quality across all formats

Language Support

The API supports 23 languages, including English, Spanish, German, and French. It handles character limits automatically, making it easy to convert reading materials into audio without complex setup.

  • Support for 23 languages
  • Automatic language detection or manual selection
  • No need for external translation tools

Pricing Model

Lectura charges $0.01 per 1,000 characters, with no monthly subscriptions or hidden fees. Failed requests are free, and a $0.50 trial credit is available for new Google accounts.

  • $0.01 per 1,000 characters
  • No monthly subscriptions or seats
  • Free failed requests

Voice Options

Sound wave illustration for: Voice Options

Lectura offers eight voice presets derived from licensed recordings, ensuring consistent audio quality for educational materials. Each voice is designed to maintain clarity and engagement, suitable for converting lesson texts and reading materials into accessible audio formats without requiring technical expertise.

8 Presets Available

The API provides eight distinct voice options, including female presets like Aria and Nova, and male presets such as Felix and Milo. These voices are based on licensed recordings from LibriTTS-R (CC BY 4.0) and LibriVox public-domain audiobook readings.

  • Aria: Warm, clear narrator
  • Nova: Bright, upbeat
  • Luna: Soft, storytelling
  • Sage: Calm, instructional
  • Felix: Energetic, promo
  • Milo: Friendly, conversational
  • Atlas: Neutral, news
  • Orion: Deep, documentary

Clear Narration

Voices like Aria and Luna are optimized for clear narration, making them ideal for reading lessons aloud. The synthetic speech includes an inaudible watermark to identify generated audio, helping teachers track usage accurately.

Diverse Tones

From the deep tones of Orion to the energetic delivery of Felix, the diverse range of voices allows teachers to match the audio to the content type. This variety supports different teaching styles and student engagement strategies.

Language Coverage

Sound wave illustration for: Language Coverage

Lectura supports 23 languages, allowing you to generate audio for diverse classroom materials. Any voice can speak any of these languages, providing flexibility for multilingual lessons or international reading assignments without needing multiple voice models.

23 Languages

The API handles Arabic, Chinese, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hindi, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Russian, Spanish, Swahili, Swedish, and Turkish. You can set the language field to an ISO code to ensure correct pronunciation, especially for non-English Latin script text.

  • Arabic, Chinese, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hindi, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Russian, Spanish, Swahili, Swedish, Turkish

No Vietnamese

Vietnamese is not among the supported languages.

No Thai

Thai is not supported.

Pricing Structures

Sound wave illustration for: Pricing Structures

Lectura charges $0.01 per 1,000 characters, including spaces and punctuation. Failed requests are free, with charges returned in full if synthesis fails. The standard rate is $10 per million characters processed.

For larger needs, top-ups use USDT (TRC-20) on the TRON network. Transfers are credited automatically within minutes. There are no monthly plans, seats, or minimum spending requirements, allowing you to pay only for what you generate.

Per Character

Billing is strictly usage-based at $10 per 1 million characters. This cost covers all models, including the high-definition option. Spaces, punctuation, and special characters count toward the total. If a request fails, you are not charged.

  • Rate: $0.01 per 1,000 characters.
  • All characters count, including spaces.

Subscription Models

The API does not use traditional subscriptions. There are no monthly plans, no per-seat fees, and no minimum spend requirements. Your balance does not expire, so you can top up when needed without losing credit.

Free Tiers

Signing in with Google provides a $0.50 trial credit, valid for 7 days. This covers approximately 50,000 characters of text-to-speech conversion. Accounts created with an email and password do not receive this trial credit.

  • Google sign-in: $0.50 credit.
  • Email sign-up: No trial credit.

Technical Ease

Sound wave illustration for: Technical Ease

Lectura uses a standard REST API compatible with common HTTP libraries. Teachers can send text and receive audio files directly without complex infrastructure. The endpoint mirrors OpenAI’s structure, allowing simple integration into existing educational tools.

SDK support enables quick implementation using the official OpenAI SDKs by changing the base URL. This reduces the learning curve for staff who may not have deep technical expertise, ensuring smooth adoption across various classroom management systems.

REST API

The API accepts POST requests with JSON bodies. You specify the model, input text, voice, and desired audio format. Responses return the generated audio file directly, simplifying the retrieval process for lesson materials.

  • Endpoint: POST https://api.playnn77.com/v1/audio/speech
  • Supports MP3, WAV, OPUS, FLAC, and PCM formats
  • Handles text up to 4096 characters per request

SDK Support

Since the request shape matches the OpenAI Speech endpoint, official OpenAI SDKs work by changing the base URL. This allows teachers to use existing code snippets or libraries without rewriting logic for custom protocols.

Documentation

Comprehensive guides detail request parameters and response formats. Clear examples help educators configure their first API call quickly, ensuring accurate audio generation for reading materials and announcements.

Data Usage

Sound wave illustration for: Data Usage

Lectura prioritizes data simplicity for educational workflows. Input text is processed solely to generate the requested audio file and is not retained for model training. This ensures that student readings or lesson materials remain distinct from your training datasets.

Training Policy

Your input text is used exclusively for immediate synthesis. We do not store or reuse your content to train or improve the underlying TTS engine, keeping your educational materials distinct from our model development.

Storage Policy

Generated audio is returned directly in the API response and is not stored on our servers. Only request metadata—such as timestamp, character count, and status—is kept for accurate billing and usage tracking.

Privacy

We maintain a minimal data footprint. Since audio files are not stored and input text is not used for training, your classroom data remains private and under your control.

Limitations

Sound wave illustration for: Limitations

Lectura’s API delivers complete audio files via standard HTTP requests. It does not support real-time streaming, WebSocket connections, or partial audio chunks, which means you receive the final file only after synthesis completes.

No Streaming

Requests are processed sequentially, so longer texts may experience queue delays. You must wait for the full response before playing the audio, making this model suitable for pre-generated lesson files rather than live interactive read-alouds.

No SSML

The API does not support Speech Synthesis Markup Language (SSML). You cannot control pause durations, emphasis, or pronunciation via XML tags within the input text field.

  • Input is plain text only.

No Cloning

We do not offer custom voice cloning or uploading of your own voice recordings. The eight presets are fixed and based on licensed recordings from LibriVox. You cannot design new voices or create celebrity impersonations.

  • No custom voice upload.
Limitations

Integration Complexity

Sound wave illustration for: Integration Complexity

Integrating Lectura into your classroom workflow requires minimal technical overhead. The API follows a standard REST structure, allowing you to send text and receive audio files without building complex infrastructure. This simplicity supports both manual setup and automated tools.

You can connect the API using no-code platforms or direct code. The process is straightforward: authenticate with your key, format the JSON request, and handle the returned audio file. This approach keeps integration manageable for teachers without dedicated IT staff.

No-Code Tools

You can connect the API using no-code platforms or direct code. The process is straightforward: authenticate with your key, format the JSON request, and handle the returned audio file. This approach keeps integration manageable for teachers without dedicated IT staff.

Many automation tools support HTTP requests. You can trigger audio generation from lesson plans or announcement boards without writing custom scripts, though no specific platform integrations are provided. This reduces the barrier to entry for non-technical educators.

  • Automate audio creation from text fields in learning management systems
  • No custom server required for basic workflows

Manual Integration

For more control, you can use the standard REST endpoint. Send a POST request with your text, voice selection, and desired format. The API returns the audio file directly, ready for download or playback in your classroom materials.

The request shape matches the OpenAI SDK standard. If you already use Python or JavaScript, you can adapt existing code snippets by changing the base URL to https://api.playnn77.com/v1.

  • POST to /v1/audio/speech with JSON body
  • Supports mp3, wav, opus, flac, and pcm formats
  • Compatible with standard OpenAI SDKs via base_url change

API Keys

Authentication relies on a single active Bearer token. You generate this key on your dashboard and include it in the Authorization header. One key per account ensures clear tracking of usage and costs.

You can rotate your key at any time. When you issue a new key, the old one stops immediately. This is useful for security or if you need to reset access without losing your balance.

  • Generate keys via /get-api-key/ dashboard
  • One active key per account
  • Instant invalidation of old keys upon rotation

Support Quality

Sound wave illustration for: Support Quality

Lectura provides support exclusively via email, ensuring that queries are documented and resolved without the pressure of immediate live interaction. This channel is the single point of contact for all technical and billing inquiries, keeping communication clear and traceable for school IT staff and teachers alike.

There is no phone number, live chat, or on-call engineering team for urgent outages. Users rely on written responses which are typically prompt, though response time can vary based on queue volume. For most standard questions about voices or pricing, you can expect a reply within one business day.

Email Only

All support requests are handled through a dedicated email address. This approach avoids the noise of multiple channels and ensures that every ticket has a clear history, which is useful when troubleshooting API key issues or billing discrepancies in the school’s account.

Since there is no live chat, you do not need to wait on hold. Simply describe your issue with your API key and the request details, and the support team will address it directly via email.

  • Single email contact channel
  • No phone or live chat
  • Written record of all interactions

Response Time

Response times are not guaranteed by an SLA, so there is no fixed uptime or support level agreement. However, the small team structure allows for direct attention to each ticket. Most inquiries regarding character counts, voice selection, or basic integration questions are resolved quickly.

For complex technical issues, such as debugging a custom Python script using the OpenAI SDK, you may need to provide more context. The team reviews these carefully to ensure accurate solutions rather than generic replies.

  • No SLA guarantee
  • Typical replies within 24 hours
  • Direct team attention

Documentation

The primary resource for self-service support is the /docs/ page. It contains clear examples for Python, cURL, and JavaScript, showing exactly how to send text and receive audio files. This reduces the need for email support for common tasks.

The documentation also covers rate limits (60 requests per minute) and character limits (4096 per request), helping you avoid errors before they happen. If the docs do not cover your specific use case, email support is the next step.

  • Complete API reference
  • Code examples in Python and cURL
  • Rate limit details included

Use Case Fit

Sound wave illustration for: Use Case Fit

Lectura’s TTS API allows educators to convert static text into clear audio files without coding. This workflow supports diverse classroom needs, from reading assignments to daily announcements, by generating standardized audio formats compatible with any device.

Read-Aloud

Teachers can paste lesson texts directly into the API to generate audio for students. With support for 23 languages and eight distinct voice presets, educators can ensure the audio matches the intended tone, whether it is a calm narration for literature or an energetic read for younger grades.

  • Convert up to 4,096 characters per request
  • Select from 8 voice presets
  • Support for 23 languages

Announcements

Daily school announcements can be converted into audio files for broadcast systems or learning management platforms. The API processes requests sequentially, ensuring consistent output quality. Generated files are returned after processing, allowing for quick integration into morning assembly audio streams or digital notice boards.

  • Instant audio file generation
  • No manual recording required
  • Compatible with standard audio players

Audio Books

Educators can transform reading materials into audio books for accessibility or independent listening. Since the API does not store generated audio, files must be saved by the user. Long texts are split into 4,096-character segments and joined to create complete listening experiences.

  • Split long texts automatically
  • Join audio segments
  • No storage limits on user side

Security

Sound wave illustration for: Security

Lectura secures data transmission using standard HTTPS encryption for all API requests and responses. Your lesson texts and generated audio files are protected in transit without requiring custom certificate management. This ensures that sensitive classroom materials remain confidential between your device and our servers.

Account security relies on a single active API key per account. You control access directly through the dashboard, ensuring only authorized tools can consume your character credits. The system does not store the input text for training, preserving student privacy by design.

HTTPS

All API endpoints use HTTPS to encrypt data in transit. This standard protection ensures that your lesson texts and audio outputs are secure during transmission without requiring complex infrastructure changes for school networks.

Key Rotation

Each account holds one active API key. If you suspect a leak, you can issue a new key from the dashboard at any time. The previous key stops working immediately, preventing unauthorized usage without manual intervention.

  • Issue new key instantly
  • Old key invalidates immediately
  • No downtime during rotation

Rate Limits

The API enforces a limit of 60 requests per minute per key. This prevents a single script from consuming your entire balance unexpectedly during a busy class. New accounts start with a lower 10 requests-per-minute limit until the first top-up is processed.

Requests are processed sequentially, so heavy usage may queue slightly. This ensures fair resource distribution and prevents server overload during peak school hours.

Final Recommendation

Sound wave illustration for: Final Recommendation

Lectura is purpose-built for educators who need reliable audio generation without managing complex infrastructure. The API’s straightforward REST endpoint allows seamless integration with existing school communication platforms, ensuring that lesson texts and announcements are converted to audio files efficiently.

No-Code Integration

For teachers and staff without coding experience, Lectura offers a simple path to audio conversion. The API endpoint mirrors standard structures, allowing easy use with common no-code tools. This ensures that school newsletters and reading materials can be audio-enabled quickly.

  • Standard REST endpoint compatible with no-code platforms
  • No custom SDK required
  • Simple JSON request body

Scaling Usage

Schools can generate audio for large reading lists without immediate cost surprises. With a per-character pricing model, you only pay for what you use. The 60 requests per minute limit supports steady batch processing for entire classes or departments.

Budget Management

The flat rate of $10 per million characters makes costs predictable. Failed requests are refunded, ensuring you do not pay for errors. The $0.50 free trial allows testing before committing to a top-up via USTRC-20.

Listen to the 8 voices

Each sample below was generated by this API from the same sentence. Teachers can easily design engaging lessons without needing technical skills to manage their classrooms efficiently.

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. OpenAI API reference: create speech
  3. Python documentation
  4. Creative Commons Attribution 4.0
  5. IETF RFC 7845: Ogg Opus
  6. MDN: Web Speech API
  7. Tether (USDT)
  8. LibriTTS-R paper (arXiv 2305.18802)
  9. Node.js documentation
  10. ISO 639 language codes
  11. curl documentation
  12. FFmpeg documentation

More on this site