Text laut vorlesen: Reliable TTS for E-Learning Teams

By CourseSpeak editorial team · Updated 2026-11-19

This page provides the technical specifications for CourseSpeak, a reliable text-to-speech API designed for LMS integrations and large-scale audiobook generation. We handle character limits, language detection, and high-volume billing via USDT for engineering teams who need predictable costs and clear technical specs.

Readers will find concrete integration details, including OpenAI-compatible endpoints, rate limits, and supported audio formats. This resource is intended for technical leads and developers building accessible e-learning platforms who require a straightforward, no-nonsense API without monthly subscriptions or hidden fees.

Text laut vorlesen: Reliable TTS for E-Learning Teams

Frequently asked questions

What does "text laut vorlesen" mean in this context?

It is German for "read text aloud." We use this phrase to demonstrate that the API supports German, one of the 23 supported languages. This capability is essential for LMS platforms and online course modules where learners need audio versions of textual content delivered via a simple API endpoint.

Does the API support SSML for better control?

No, the API does not support SSML. It accepts plain text input up to 4096 characters. You control the output only through the voice, speed, and language parameters. For precise timing or pronunciation, you must manage pacing and pauses within the text content itself before sending the request.

Can I clone a specific voice for my brand?

No, custom voice cloning is not offered. You must choose from eight preset voices (Aria, Nova, Luna, Sage, Felix, Milo, Atlas, Orion) based on licensed recordings. These voices are static and cannot be customized or cloned to match a specific brand personality or individual speaker's unique vocal traits.

Is there a free trial available for new accounts?

Yes, signing in with Google provides $0.50 of credit, valid for 7 days. Accounts created with email and password start without trial credit. This allows engineering teams to test the API endpoints and audio quality before committing to USDT top-ups for production workloads in your LMS integration.

How are failed requests charged?

Failed requests are free. If synthesis fails, the charge is returned in full. You only pay for successful audio generation. This ensures predictable billing for your engineering team, as you are charged strictly for usable audio files delivered via the API response, regardless of the input text length.

What happens if I exceed the 4096 character limit?

Each API request accepts a maximum of 4096 characters. For longer texts, you must split the content into parts, send separate requests, and join the resulting audio files. This approach handles large-scale audiobook generation efficiently, ensuring each chunk is processed independently while maintaining the overall narrative structure.

Does the API support streaming audio?

No, the API does not support streaming or WebSocket connections. It returns the complete audio file in the response after synthesis is finished. Requests are processed sequentially, so under load, a request may wait in a queue before generating the final audio file for download or playback.

Are the voices based on real human recordings?

Yes, every voice is based on licensed recordings from LibriTTS-R (CC BY 4.0) and LibriVox public-domain audiobook readings. Each generated file carries an inaudible watermark marking it as synthetic speech. This marks the file as synthetic speech.

Can I use the API for commercial audiobooks?

Yes, the API is designed for large-scale audiobook generation and LMS integrations. There are no restrictions on commercial use. You pay $0.01 per 1,000 characters, and generated audio is returned in the response without being stored, allowing you to distribute the files directly to your users or platform.

How do I top up my balance?

Top up using USDT on the TRON network (TRC-20) only. The minimum top-up is $5, and credits are automatically added within minutes. There are no subscriptions or invoices. Send the transfer to the address provided in your dashboard to ensure your engineering team has sufficient balance for API calls.

Is there a minimum spend requirement?

No, there is no minimum spend requirement. You can top up any amount above $5 and pay only for the characters you use. This model suits engineering teams with variable workloads, allowing you to scale usage up or down without locking capital into monthly plans or annual contracts.

Do you offer an SLA for uptime?

No, we do not offer an SLA, uptime guarantee, or enterprise contract. There is no enterprise contract or on-premise install option. Support is provided via email only. This reflects our focus on providing a reliable, cost-effective API for LMS integrations without the overhead of traditional enterprise service level agreements.

Which languages are not supported?

Unsupported languages include Vietnamese, Indonesian, Thai, Ukrainian, Romanian, Czech, Bengali, and all others not in our list of 23 supported languages. If you need support for these languages, you must use a different service. Our API strictly supports only the specified languages, regardless of the selected voice preset.

How is the language detected if not specified?

If the language field is omitted, the API guesses the language from the text script. Latin script text defaults to English. For non-English Latin-script text, you should explicitly set the language parameter to ensure accurate pronunciation. This automatic detection simplifies integration for English-heavy LMS content.

First request

curl

curl https://api.m9871.info/v1/audio/speech \
  -H "Authorization: Bearer $TTS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"tts-1","voice":"aria","input":"Hello from the API.","response_format":"mp3"}' \
  --output hello.mp3

How it works

Sound wave illustration for: How it works

Send text to our endpoint and receive an audio file. The API uses the same request shape as the OpenAI speech endpoint, allowing engineering teams to leverage existing OpenAI SDKs by simply updating the base URL.

Requests are processed sequentially. Input text is converted to speech and returned as a downloadable audio file, ready for immediate integration into your LMS or audiobook pipeline.

OpenAI-compatible endpoint

OpenAI-compatible endpoint

Use the standard POST https://api.m9871.info/v1/audio/speech endpoint. The request body mirrors the OpenAI format, ensuring seamless drop-in compatibility for teams already using OpenAI client libraries.

  • Same JSON structure as OpenAI /v1/audio/speech

Simple JSON requests

Define the model, input text, voice, and desired format in a single JSON payload. The API handles the synthesis, returning the audio file in the response body after generation is complete.

  • Supports tts-1 and tts-1-hd models

Instant audio delivery

Audio is generated and returned immediately upon successful synthesis. For long texts, split the input into chunks of up to 4096 characters and join the resulting audio files for complete narration.

Why for LMS?

Sound wave illustration for: Why for LMS?

Text-to-speech integration ensures content meets accessibility standards (WCAG) by providing audio alternatives for reading materials. The API handles high-volume generation efficiently, allowing educational teams to convert large course libraries into consistent, clear audio files without manual intervention.

Accessibility compliance

Generate audio files directly from your LMS content to support diverse learners. The service handles character limits and language detection automatically, ensuring consistent output quality across thousands of modules.

  • WCAG-compliant audio generation
  • Automatic language detection
  • Consistent voice output

Large team support

Designed for engineering teams managing multiple courses. Requests are processed sequentially, so under load a request may wait in a queue.

  • Concurrent request handling
  • Predictable latency
  • Scalable architecture

No monthly subscriptions

Pay only for what you use. With USDT top-ups and no minimum spend, costs align directly with content production. This model eliminates waste from unused seats or unused monthly credits.

  • Pay per character
  • No minimum spend
  • USDT billing only

Voices & Languages

Sound wave illustration for: Voices & Languages

CourseSpeak provides 8 distinct voice presets engineered for clear educational delivery. Each voice is derived from licensed LibriTTS-R recordings and carries an inaudible watermark. You can select from female voices like Aria for narration or Luna for storytelling, and male voices like Felix for energetic promos or Atlas for neutral news-style content, as well as Milo, Sage, and Orion.

8 preset voices

The available voices cover a range of tones suitable for e-learning, from the warm and clear Aria to the calm, instructional Sage. All models use the same underlying engine, ensuring consistent quality across tts-1 and tts-1-hd.

  • Aria: Warm, clear narrator
  • Nova: Bright, upbeat
  • Luna: Soft, storytelling
  • Sage: Calm, instructional
  • Felix: Energetic, promo
  • Milo: Friendly, conversational

23 supported languages

Our API supports 23 languages, allowing any voice to speak any supported language. This flexibility simplifies multilingual course production without managing multiple voice models.

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

Automatic language detection

The API automatically detects language from the text script. Latin script text defaults to English. For non-English Latin-script text, explicitly set the language parameter to ensure accurate synthesis.

Technical Specs

Sound wave illustration for: Technical Specs

Engineers integrating CourseSpeak into LMS platforms should configure their clients according to strict API limits. Requests are processed sequentially, so under load a request may wait in a queue. Understanding these constraints ensures smooth audio pipeline integration.

Rate limits explained

Our API enforces a limit of 60 requests per minute per API key. New accounts without an active top-up start with a lower threshold of 10 requests per minute. These limits apply to the POST /v1/audio/speech endpoint and reset on a sliding window basis.

Character limits per request

Supported audio formats

Pricing Model

Sound wave illustration for: Pricing Model

The API charges $0.01 per 1,000 characters, including spaces and punctuation. Failed requests incur no cost, with the charge returned in full. This model ensures predictable billing for large-scale audiobook generation without minimum spend requirements.

Pay per character

Each request processes up to 4,096 characters. Longer texts must be split into parts of up to 4096 characters and joined by the client. The rate is $10 per million characters, with no monthly plans or per-seat fees.

  • 0.01 USD per 1,000 characters
  • Failed requests are free
  • No minimum spend

USDT top-up only

Payments are processed via USDT on the TRON network (TRC-20). Top-ups start at $5 and credit automatically within minutes. Balances do not expire, and no invoices with VAT are issued.

  • USDT (TRC-20) only
  • Minimum top-up: $5
  • Auto-credit within minutes

No hidden fees

The free trial provides $0.50 credit (7 days) for Google sign-ins. Email/password accounts start without trial credit. There are no subscription tiers, hidden usage fees, or expiration dates on your balance.

  • Free trial: $0.50 credit
  • No subscription tiers
  • Balance never expires
Pricing Model

Integration

Sound wave illustration for: Integration

The API endpoint mirrors the OpenAI speech structure, allowing engineering teams to leverage existing OpenAI SDKs with minimal configuration changes. By simply updating the base URL to https://api.m9871.info/v1 and providing your unique API key, your current integration logic remains intact while gaining access to CourseSpeak’s TTS capabilities.

Use OpenAI SDKs

Official OpenAI SDKs work seamlessly by pointing to our base URL. This ensures consistent request shapes for model, input, voice, and response format parameters, reducing boilerplate code for LMS audio generation pipelines.

  • Compatible with standard OpenAI client libraries
  • Identical JSON body structure
  • Supports all standard TTS parameters

cURL examples

Direct HTTP requests are straightforward. Use POST to the speech endpoint with your Bearer token in the Authorization header. The body contains the text payload and desired voice settings, returning audio data directly.

  • POST https://api.m9871.info/v1/audio/speech
  • Header: Authorization: Bearer tts-...
  • Body: JSON with model, input, voice

Base URL configuration

Set your API base to https://api.m9871.info/v1. This single change directs all requests to our infrastructure. Ensure your API key is valid and associated with an account holding sufficient USDT balance.

Data Privacy

Sound wave illustration for: Data Privacy

Input text is used exclusively for synthesis and is never used to train our models. Generated audio is returned in the response and not stored on our servers after delivery, ensuring your course content remains yours.

Request metadata, including timestamp, character count, and status, is retained solely for billing accuracy and troubleshooting. This minimal data keeps your usage transparent without retaining the actual audio files or source text long-term.

No training on input

Our engine processes your text strictly for the immediate generation of audio. Unlike many consumer-grade TTS services, we do not use your input data to improve or train the underlying speech models, keeping your educational content private.

No audio storage

Once the audio file is delivered to your client or LMS, we do not retain a copy. This ensures that your generated lectures or audiobooks are not stored in our infrastructure, reducing your liability and data exposure.

Billing metadata kept

We store request metadata such as time, character count, and status to ensure accurate billing and support. This minimal data allows us to verify charges and troubleshoot issues without storing the actual content you are processing.

Support

Sound wave illustration for: Support

Our support model prioritizes self-service efficiency for engineering teams. We provide comprehensive documentation to resolve integration issues quickly, ensuring your LMS workflow remains uninterrupted without waiting on queue times.

Email support only

All inquiries are handled via email. This asynchronous approach allows our engineers to provide detailed, technical responses tailored to your specific integration context without the pressure of real-time availability.

  • Direct line to engineering support
  • Detailed technical responses
  • No phone numbers or ticketing systems

No live chat

We do not offer live chat or instant messaging widgets. This eliminates variable wait times and ensures that every support interaction receives full attention from a qualified engineer rather than a generalist.

Documentation first

Start with our /docs/ page for API references, cURL examples, and voice specifications. Most integration questions regarding rate limits, character counts, and format options are answered immediately in the technical specs.

FAQ Overview

Sound wave illustration for: FAQ Overview

Frequently asked questions address core usage patterns, billing mechanics, and technical constraints for LMS integrations. This section clarifies how character counting works, how USDT top-ups are processed, and what limits apply during high-volume audiobook generation.

Common questions

Characters include spaces and punctuation. Failed requests incur no charge. The free trial provides $0.50 for 7 days.

  • How are characters counted?
  • Do failed requests cost money?
  • How long does top-up take?

Technical limits

Requests are limited to 4,096 characters. Rate limit is 60 requests per minute. Audio formats include mp3, wav, opus, flac, and pcm.

  • Max characters per request
  • Rate limit per key
  • Supported audio formats

Voice customization

We offer 8 preset voices. Custom voice cloning is not available. Voices are licensed from LibriTTS-R and LibriVox.

  • 8 preset voices
  • No custom cloning
  • Licensed recordings

Listen to the 8 voices

Each sample below was generated by this API from the same sentence. These errors stem from assuming consumer-grade features or overlooking technical constraints defined in the specification.

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. Node.js documentation
  4. curl documentation
  5. openai-node on GitHub
  6. LibriVox public-domain audiobooks
  7. IETF RFC 7845: Ogg Opus
  8. W3C WAI: making audio and video accessible
  9. Creative Commons Attribution 4.0
  10. MDN: Web Speech API
  11. ISO 639 language codes
  12. LibriTTS-R corpus (OpenSLR 141)

More on this site