Accessible Cloud TTS API for Dyslexia Support

By LuminaRead editorial team · Updated 2026-11-18

This guide explains how product teams use the LuminaRead API to convert text into natural speech, creating accessible digital experiences for users with dyslexia and visual impairments. You will learn how our simple, reliable tool integrates into your workflow to turn written content into clear audio files via a standard cloud endpoint.

We cover voice options, language support, and pricing transparently. Read on to understand technical details like the 4096-character limit, USDT top-ups, and data privacy policies. This page is designed for developers who need compliant, straightforward audio generation without unnecessary features or hype.

Frequently asked questions

Is LuminaRead the best TTS API?

We do not claim to be the best. We provide a reliable cloud API for text-to-speech with 8 voice presets and 23 languages. Our focus is on helping product teams build accessible digital experiences for users with dyslexia and visual impairments through a simple, developer-friendly interface.

How does it compare to Google TTS?

Unlike Google TTS, we use licensed recordings from LibriVox public-domain audiobooks. We offer 8 distinct voice presets like Aria and Felix, supporting 23 languages. Our pricing is $0.01 per 1,000 characters, and we do not offer proprietary SDKs or enterprise contracts, keeping the integration simple for developers.

Is it better than Amazon Polly?

We offer a different approach using licensed LibriVox recordings rather than neural synthesis. We provide 8 specific voice presets and support 23 languages. Our pricing is transparent at $0.01 per 1,000 characters, with no monthly plans or minimum spend, making it easy to integrate via standard HTTP requests.

Does it support dyslexia-friendly fonts?

No. We are a text-to-speech API that converts text into audio files. We do not handle visual rendering, so we do not support specific fonts. Our tool focuses on auditory accessibility, converting up to 4,096 characters of text into natural speech for users with dyslexia or visual impairments.

Can it read mathematical equations?

Yes, if the equations are provided as text within the 4,096 character limit. The API reads the input string directly. However, we do not support SSML or custom pronunciation lexicons, so complex mathematical symbols may not be interpreted perfectly unless written out in a way the selected voice can articulate clearly.

Is the voice more natural than robotic TTS?

Our voices are based on licensed recordings from LibriVox public-domain audiobooks, offering a natural, human-like quality. We provide eight distinct presets, including warm narrators and energetic voices, ensuring the audio sounds less robotic than traditional synthetic TTS engines, which is crucial for users with dyslexia who prefer natural speech patterns.

Does it support right-to-left languages?

Yes, we support Arabic and Hebrew. Persian is not in our list of 23 supported languages. Our API handles text input and generates audio regardless of script direction. You must specify the language code if the script does not clearly indicate it, ensuring the correct pronunciation for right-to-left languages like Arabic and Hebrew.

Can I use it for children's apps?

Yes, our voice presets like Luna (soft, storytelling) and Felix (energetic) are suitable for children's applications. The API accepts text input and returns audio files, making it easy to integrate into apps. You can control speed and voice to match the tone appropriate for young users effectively.

Is the API reliable during high traffic?

Requests are processed sequentially, so under heavy load, a request may wait in a queue. Typical speed is roughly real-time. We enforce a rate limit of 60 requests per minute per key. Failed requests are free, ensuring you are not charged for errors during high-traffic periods.

Do I need a developer to integrate it?

Yes, integration requires sending JSON POST requests to our API endpoint. The request shape matches the OpenAI speech endpoint, so existing OpenAI SDKs work by changing the base URL. Developers can use standard HTTP libraries or SDKs to send text and receive audio files programmatically.

Can I use the API for commercial products?

Yes, you can use the generated audio in commercial products. Input text is used only to produce audio and is not used for training. Generated audio is returned in the response and not stored by us, allowing you to integrate the audio files directly into your accessible digital experiences.

Is there a free tier available?

We offer a free trial with $0.50 of credit (about 50,000 characters) valid for 7 days when signing in with Google. Standard accounts start without trial credit. There is no permanent free tier, but you can top up with USDT on the TRON network starting at $5.

How do I choose between tts-1 and tts-1-hd?

Both models use the same engine and have the same price of $10 per 1 million characters. The choice is purely based on your preference for audio quality. Both support the same 8 voice presets, 23 languages, and response formats, so you can switch between them without changing your integration logic.

Does it work on mobile devices?

Yes, the API returns standard audio files (mp3, wav, opus, flac, pcm) that play on any mobile device. Since we do not provide a native mobile SDK, you integrate the API via HTTP requests in your mobile app. The audio files are compatible with standard mobile media players.

Why Choose a Cloud TTS API for Accessibility?

Sound wave illustration for: Why Choose a Cloud TTS API for Accessibility?

Turning text into natural speech allows users with dyslexia to bypass reading barriers, accessing content through auditory channels. This API provides a straightforward way to convert written material into audio, supporting diverse learning needs without complex setup.

Cloud-based TTS ensures consistent performance and easy integration into existing digital products. By offloading processing to the cloud, teams can deliver reliable audio experiences that scale with user demand, maintaining a smooth workflow for accessibility features.

Supporting Dyslexia with Audio Conversion

Audio conversion reduces cognitive load by allowing users to listen to text instead of decoding it visually. This method supports comprehension and retention, making digital content more inclusive for individuals with dyslexia and visual impairments.

The Benefits of Cloud-Based Text-to-Speech

Cloud infrastructure handles processing efficiently, ensuring quick response times for text-to-audio conversion. Developers benefit from simple JSON endpoints and standard SDK compatibility, reducing the engineering effort required to implement audio features in their applications.

  • Simple integration with existing tech stacks
  • Scalable processing for varying user loads
  • Consistent audio quality across all devices

Ensuring Compliance with Digital Accessibility Standards

Providing audio alternatives for text helps meet requirements of standards like WCAG. By offering clear, natural-sounding speech, products can better support users who rely on assistive technologies, ensuring a more inclusive digital experience.

How the LuminaRead API Works

Sound wave illustration for: How the LuminaRead API Works

LuminaRead simplifies audio generation by accepting text input and returning a synthesized audio file. This straightforward process ensures your product team can easily integrate natural speech into accessible digital experiences without managing complex infrastructure.

Sending Text and Receiving Audio Files

You send text to the API and receive an audio file. Each request handles up to 4,096 characters, making it ideal for concise content or structured long-form text that you split and join.

Using the Standard OpenAI-Compatible Endpoint

The API follows the same request shape as the OpenAI speech endpoint. By changing the base_url to https://api.playmx52.com/v1, you can use official OpenAI SDKs directly, reducing integration effort for your developers.

Understanding the POST /v1/audio/speech Request

Send a POST request with a JSON body containing your text, voice selection, and preferred format. Authentication is handled via a Bearer token, ensuring secure access to your account's generated audio.

  • Endpoint: POST https://api.playmx52.com/v1/audio/speech
  • Format: JSON body with input, voice, and model fields
  • Auth: Authorization: Bearer tts-... header

Voice Options for Clear Auditory Output

Sound wave illustration for: Voice Options for Clear Auditory Output

LuminaRead offers eight distinct voice presets, each derived from licensed LibriTTS-R recordings and public-domain audiobook readings. These voices provide clear, natural auditory output essential for users with dyslexia and visual impairments, ensuring that converted text remains engaging and easy to follow.

Female Voices: Aria, Nova, Luna, and Sage

Aria offers a warm, clear narration style ideal for general reading. Nova provides a bright, upbeat tone suitable for lighter content. Luna delivers a soft, storytelling voice for narrative texts, while Sage brings a calm, instructional presence perfect for educational materials.

Male Voices: Felix, Milo, Atlas, and Orion

Felix is energetic and well-suited for promotional content. Milo offers a friendly, conversational tone for everyday texts. Atlas provides a neutral, news-style delivery, and Orion adds a deep, documentary feel for serious or detailed subjects.

Choosing the Right Voice for Different Content Types

Select a voice that matches the emotional tone of your text to enhance comprehension. Pairing a calm voice like Sage with instructional guides or a warm voice like Aria with general articles helps reduce cognitive load for users with reading difficulties.

All eight voices support any of the 23 available languages, allowing consistent audio quality across diverse content types without needing voice-specific language models.

Language Support for Global Audiences

Sound wave illustration for: Language Support for Global Audiences

LuminaRead supports 23 languages, allowing you to reach diverse user bases without managing separate voice models. Every voice can speak all supported languages, ensuring consistent quality across your product’s international audience.

23 Supported Languages and Scripts

We support Arabic, Chinese, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hindi, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Russian, Spanish, Swahili, Swedish, and Turkish. This wide coverage ensures your accessibility features work for most major markets.

Automatic Language Detection and Manual Override

The API guesses the language from the script if you omit the language field, defaulting to English for Latin text. For non-English Latin-script content, explicitly set the language parameter to ensure accurate pronunciation and natural intonation.

Limitations: Languages Not Currently Supported

We do not currently support Vietnamese, Indonesian, Thai, Ukrainian, Romanian, Czech, Bengali, and all others not in the list. If your users require these specific languages, you may need to integrate a secondary provider.

Audio Formats and Speed Control

Sound wave illustration for: Audio Formats and Speed Control

The LuminaRead API returns audio in five standard formats: MP3, WAV, Opus, FLAC, and PCM. This flexibility ensures compatibility with various accessibility tools and web players used by product teams. Each format serves different needs, from compressed efficiency to lossless clarity.

Adjusting the speed parameter (0.25–4.0) allows users to tailor speech pace. Slower speeds aid comprehension for those with processing difficulties, while faster rates help experienced listeners. The engine maintains natural intonation across all speeds.

Available Output Formats: MP3, WAV, Opus, FLAC, PCM

Select your preferred response_format in the request. MP3 offers small file sizes for web delivery. WAV and FLAC provide high-quality, uncompressed audio for archival or high-fidelity playback. PCM is ideal for raw audio processing pipelines.

Opus delivers efficient compression suitable for low-bandwidth environments, ensuring smooth playback on mobile devices used by visually impaired or dyslexic users.

  • MP3: Compressed, web-friendly
  • WAV/FLAC: Lossless, high quality
  • PCM: Raw data stream
  • Opus: Efficient low-bandwidth

Adjusting Speech Speed from 0.25x to 4.0x

Set the speed value between 0.25 and 4.0. A lower speed (e.g., 0.75x) aids readers who need more time to process text. Higher speeds (e.g., 1.5x) suit familiar content or quick scanning.

The engine preserves voice character and clarity even at extreme speeds, ensuring the audio remains pleasant and intelligible for assistive technology integration.

  • Range: 0.25 to 4.0
  • Lower speeds: Better comprehension
  • Higher speeds: Faster consumption
  • Natural tone maintained

Optimizing Audio Quality for Different Use Cases

For detailed educational content, use WAV or FLAC with a moderate speed. For background narration in apps, MP3 or Opus at 1.0x speed balances quality and performance.

Experiment with speed settings to find the optimal balance for your specific audience. The API processes requests sequentially, so longer, slower audio may experience slight queue delays during high traffic.

image': 'Close-up of a smartphone screen displaying a simple audio player interface with a waveform visualization, resting on a desk next to a pair of over-ear headphones, soft natural lighting, minimal design, no text or logos visible'}

Handling Long Texts Efficiently

Sound wave illustration for: Handling Long Texts Efficiently

The LuminaRead API processes text in chunks of up to 4,096 characters per request. This constraint ensures consistent processing speed and reliable audio generation for your accessibility features. Longer documents require your application to handle segmentation before sending data to the endpoint.

The 4096-Character Limit per Request

Each API call accepts a maximum of 4,096 characters, including spaces and punctuation. Exceeding this limit results in a rejection, so your integration must split larger texts into manageable segments before submission.

Splitting and Joining Audio for Longer Content

To read lengthy articles or reports, your system should divide the input text into 4,096-character blocks. You then send each block to the API and concatenate the returned audio files seamlessly for the user.

Managing Queue Times During High Traffic

Requests are processed sequentially. While typical generation is near real-time (25 characters per second), high load may introduce queue delays. Plan your audio generation timing to ensure a smooth listening experience for users with visual impairments or dyslexia.

Pricing and Payment Transparency

Sound wave illustration for: Pricing and Payment Transparency

Pricing is straightforward: $0.01 per 1,000 characters, including spaces and punctuation. Failed requests are free, ensuring you only pay for successful synthesis.

No monthly plans, seats, or minimum spend. The balance never expires, and there are no VAT invoices or hidden fees.

$0.01 per 1,000 Characters with No Hidden Fees

The cost scales linearly with usage. You pay $10 per million characters processed. This simple model helps product teams predict costs accurately without complex tiered structures.

Free Trial Credit for New Accounts

New accounts created via Google sign-in receive $0.50 in trial credit, valid for 7 days. This equals approximately 50,000 characters, allowing teams to test audio quality before committing.

Accounts created with email and password do not receive this trial credit.

  • Trial credit: $0.50
  • Validity: 7 days
  • Eligibility: Google sign-in only

Top-Up via USDT (TRC-20) with Instant Crediting

Top-ups are processed via USDT on the TRON network (TRC-20). The minimum top-up amount is $5. Funds are credited automatically within minutes after the transfer is confirmed.

We do not accept cards, PayPal, or subscriptions. This method supports global accessibility by removing banking barriers for international product teams.

  • Network: TRON (TRC-20)
  • Minimum: $5
  • Speed: Minutes
  • Methods: USDT only

Technical Integration Guide

Sound wave illustration for: Technical Integration Guide

Integrate LuminaRead into your accessibility workflow using standard authentication. Include your unique API key in the request header as Authorization: Bearer tts-.... This simple token ensures secure access to the synthesis engine without requiring complex OAuth flows.

Authentication with Bearer Tokens

Each account holds one active key. If you rotate the key, the previous one stops immediately, ensuring tight security for your product teams. Generate new keys directly from the /get-api-key/ dashboard.

Using the OpenAI SDK with Custom Base URL

The API mirrors the OpenAI speech endpoint structure. Use the official OpenAI SDKs by setting base_url to https://api.playmx52.com/v1. This allows you to reuse existing code with minimal changes.

Testing with Ready-Made cURL Examples

The dashboard provides a ready cURL example for immediate testing. Send a POST request to /v1/audio/speech with your text and chosen voice to receive the audio file instantly.

Data Privacy and Usage Rights

Sound wave illustration for: Data Privacy and Usage Rights

LuminaRead prioritizes your data integrity by ensuring that input text is used exclusively for the immediate production of audio files and is not utilized for model training. This guarantees that your unique content remains private and distinct from the training datasets used to refine the underlying voice engines.

Input Text Not Used for Training

Your submitted text serves a single purpose: generating the requested audio. Unlike some services that repurpose content to improve their AI, LuminaRead keeps your input isolated, ensuring that your specific phrasing or proprietary information does not influence future voice models or become publicly accessible.

Audio Generation and Storage Policies

Generated audio files are returned directly in the API response and are not stored on our servers after delivery. This ephemeral handling ensures that once you receive the file, we hold no copy of your audio content, reducing liability and maintaining strict data minimization principles.

Inaudible Watermarking of Synthetic Speech

Every audio file produced by LuminaRead contains an inaudible watermark that clearly marks the content as synthetic speech. This subtle digital signature helps identify the audio origin without affecting the listening experience, providing transparency for users with visual impairments or dyslexia who rely on the audio.

Rate Limits and Reliability

Sound wave illustration for: Rate Limits and Reliability

To ensure consistent performance for your accessibility features, the API enforces a rate limit of 60 requests per minute for standard keys. New accounts without a top-up start with a lower limit of 10 requests per minute, allowing you to test integration before scaling up your digital experience.

60 Requests per Minute Limit per Key

Each API key is independently capped at 60 requests per minute. This limit applies to all synthesis attempts, regardless of text length. If your product serves many users simultaneously, you may need to implement client-side queuing or distribute requests across multiple keys.

  • Standard limit: 60 requests/minute per key.
  • New account limit: 10 requests/minute.
  • Limits reset every 60 seconds.

Understanding Queue Processing Under Load

Requests are processed sequentially. Under heavy load, a request may wait in a queue before synthesis begins. While typical speed is roughly real-time, short phrases may take a few seconds to generate. Plan your user interface to show loading states appropriately so users with dyslexia are not confused by delays.

Managing Key Rotation for Continuous Access

You can issue a new API key at any time from your dashboard. The new key becomes active immediately, and the old key stops working at once. This allows you to rotate keys for security without downtime, ensuring your accessibility features remain reliable for your users.

What’s Not Included

Sound wave illustration for: What’s Not Included

LuminaRead delivers reliable, static audio files via a straightforward API. We focus on core synthesis without adding layers of complexity that may not be necessary for your accessibility workflows. This keeps the integration simple and the output consistent.

No Streaming, SSML, or Voice Cloning

We do not offer real-time streaming, WebSocket connections, or SSML support. You receive complete audio files upon successful synthesis. Additionally, we do not provide custom voice cloning or emotion tags; our eight preset voices cover the standard needs for clear, accessible narration.

No Mobile SDKs or WordPress Plugins

Our integration relies on the standard OpenAI-compatible HTTP endpoint. There is no dedicated mobile SDK or WordPress plugin. Developers can easily integrate via any HTTP client or the official OpenAI SDK by adjusting the base URL.

No SLA or Enterprise Contracts

LuminaRead operates as an independent storefront without formal SLAs, uptime guarantees, or enterprise contracts. Support is provided via email only. We do not offer on-premise installations or specific data-center choices, keeping our infrastructure simple and cost-effective.

Getting Started with LuminaRead

Sound wave illustration for: Getting Started with LuminaRead

Begin by visiting the /get-api-key/ page to create your account. You can sign up instantly using your Google account or provide an email and password. This process establishes your unique identity within the LuminaRead ecosystem, allowing you to access the API dashboard where your usage and credits are tracked.

Signing Up via Google or Email

Google sign-up includes a $0.50 free trial credit valid for seven days, giving you approximately 50,000 characters to test the service. Email-based accounts start with zero balance and require a top-up before use. This flexibility ensures that product teams can evaluate the API’s quality without immediate financial commitment.

Retrieving Your API Key and Balance

Once registered, the dashboard displays your active API key, current balance, and character usage statistics. You can issue a new key at any time, which immediately invalidates the previous one for enhanced security. The interface provides a ready-to-use cURL example, making it easy to verify your credentials before integration.

Generating Your First Audio File

Use the POST /v1/audio/speech endpoint with your API key in the Authorization header. Send your text in the JSON body, selecting a voice like Aria or Milo and your preferred format. The API returns the audio file directly, allowing you to integrate natural speech into your accessible digital experiences immediately.

  • Supports Google sign-up with trial credit
  • Instant key rotation available
  • Ready cURL examples provided
  • Direct audio file response

Listen to the 8 voices

Each sample below was generated by this API from the same sentence.

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. ISO 639 language codes
  3. Tether (USDT)
  4. curl documentation
  5. LibriTTS-R paper (arXiv 2305.18802)
  6. W3C WAI: making audio and video accessible
  7. LibriVox public-domain audiobooks
  8. FFmpeg documentation
  9. IETF RFC 7845: Ogg Opus
  10. openai-python on GitHub
  11. openai-node on GitHub
  12. TRON developer hub: TRC-20

More on this site