Frequently asked questions
What is a text-to-speech API?
It is a cloud service where you send text via a POST request and receive an audio file. You use the endpoint https://api.playz555.com/v1/audio/speech with a JSON body containing your text, voice, and format preferences. It works like the OpenAI speech endpoint, allowing you to integrate voice generation directly into your application code.
How is it different from a web app?
A web app is a user interface you visit in a browser, while an API is a programmatic tool for developers. We provide a REST API that returns audio files via code, not a visual player. You control the integration, voice selection, and delivery method, making it ideal for embedding voice features into your own software products.
Do I need a server?
No, you do not need a dedicated server for the TTS processing. Our cloud handles the synthesis. You only need a client capable of sending HTTP requests, such as a backend server in your app or a browser script. You send text to https://api.playz555.com/v1 and receive the audio file directly in response.
Can I use it in a mobile app?
Yes. Since we do not offer a mobile SDK, you can use the OpenAI SDK or plain HTTP requests. Simply change the base URL to https://api.playz555.com/v1 in your mobile app code. This allows you to generate audio files on demand and play them locally within your iOS or Android application.
Is it real-time?
It is not real-time streaming. You send a request and wait for the full audio file to be returned. Generation takes roughly real-time speed (25 characters per second) plus queue time. For long texts, you must split the input into chunks of 4096 characters, generate each part, and join the audio files.
Does it support SSML?
No, we do not support SSML (Speech Synthesis Markup Language). You pass plain text in the input field. If you need pauses or emphasis, you can adjust the speed parameter or split your text into separate requests. We do not offer phoneme dictionaries or custom pronunciation lexicons for fine-grained control.
Can I clone voices?
No, we do not offer custom voice cloning. You choose from eight preset voices like Aria, Nova, or Felix, which are based on licensed recordings. These voices speak all 23 supported languages. You cannot upload your own audio to create a custom clone, nor can you design a new voice from scratch.
Is it secure?
Input text is used only to produce audio and is not used for training. Generated audio is returned in the response and not stored. We keep request metadata for billing purposes. We do not offer SLAs or certifications like SOC 2 or HIPAA, but we use standard HTTPS for data transmission.
How do I handle errors?
If synthesis fails, the charge is returned in full. You should check the HTTP status code and response body for details. Common issues include exceeding the 4096 character limit or invalid voice names. Ensure your API key is correct and active. Failed requests incur no cost, so you can retry safely.
What languages are supported?
We support 23 languages including English, Spanish, German, French, Japanese, and Arabic. Any voice can speak any of these languages. If you do not set the language field, it guesses from the script. We do not support Vietnamese, Indonesian, Thai, or Ukrainian. Always specify the language for non-English Latin text.
Can I change speed?
Yes, you can adjust the speed parameter between 0.25 and 4.0. This allows you to slow down audio for educational clarity or speed it up for quick reviews. The default speed is 1.0. This setting applies to all generated audio files and is included in the JSON request body.
Is there a limit on requests?
Yes, you are limited to 60 requests per minute per API key. Before your first top-up, the limit is 10 requests per minute. If you exceed this, requests may be queued or rejected. Longer texts require multiple requests due to the 4096 character limit per request, so plan your batching accordingly.
Do I need to store audio?
No, you do not need to store audio on our servers. The audio is returned directly in the HTTP response. You can save it to your own storage, stream it to users, or play it immediately. We do not retain the generated audio files after delivery, so you manage your own storage needs.
Can I use it commercially?
Yes, you can use the API commercially. We charge $0.01 per 1,000 characters with no monthly plans or minimum spend. You pay only for what you use via USDT top-ups. The voices are based on licensed recordings, allowing you to integrate them into your educational apps.
Definition
A text-to-speech API is a cloud service that converts written text into audio files via simple HTTP requests. It allows developers to integrate voice features into applications without managing complex speech synthesis engines locally.
Text to audio conversion
Our API accepts text input and returns synthesized audio files in formats like MP3 or WAV. The engine handles pronunciation, pacing, and intonation based on the selected voice preset, delivering ready-to-play audio without external dependencies.
Cloud-based service
Processing happens on our servers, so you do not need to install heavy libraries or manage infrastructure on your devices. This keeps your educational apps lightweight and ensures consistent voice quality across all user devices, from mobile phones to desktops.
Programmatic access
Access is entirely API-driven. You send a JSON payload with your text and preferences, and receive an audio file. This programmatic approach lets you automate audio generation for lessons, exercises, or audiobooks directly from your application logic.
How it works
The API converts written lessons into audio by processing requests in the cloud. You send a simple HTTP call with your text and voice preference, and the service handles the synthesis without requiring local installation or heavy compute power on your device.
Send JSON request
Construct a POST request to the /v1/audio/speech endpoint. Include your text (up to 4,096 characters), the desired model (tts-1 or tts-1-hd), and a voice preset like nova or atlas. Authentication is handled via a Bearer token in the header.
- Endpoint:
POST https://api.playz555.com/v1/audio/speech - Body: JSON with
model,input,voice, andresponse_format - Header:
Authorization: Bearer tts-...
Receive audio file
The service returns the synthesized audio directly in the response body. Supported formats include mp3, wav, opus, flac, and pcm. For texts exceeding the character limit, split the input into parts, generate each segment, and join the resulting audio files.
- Formats: mp3, wav, opus, flac, pcm
- Response contains raw audio data
- Join segments for longer lessons
No local processing
Since synthesis occurs on our cloud servers, your app remains lightweight. You do not need to manage voice engines or handle audio rendering logic. The client simply forwards the text and plays the returned file, ensuring consistent quality across all devices.

Use cases for devs
ReadAloud lets indie developers add voice features to educational apps without building the engine. Teachers get text-to-speech results delivered as audio files, so students can listen to lessons or exercises anywhere, even offline.
Educational apps
You can turn lesson plans or textbook chapters into audio files using our API. With support for 23 languages and voices like Luna for storytelling or Sage for instruction, developers can create engaging content that students can listen to on any device.
- Convert lessons into audio files students can listen to anywhere
Audiobook players
Use the API to generate audiobook segments from text. With a 4,096-character limit per request and options for MP3 or WAV formats, you can build players that stream synthesized speech efficiently.
- Generate audio from text up to 4,096 characters per request
Accessibility tools
Provide audio alternatives for text-heavy content. Our API handles the conversion, allowing users with visual impairments or reading difficulties to access educational material through clear, synthetic speech voices.
- Deliver clear synthetic speech for improved accessibility
Integration steps
Integrating ReadAloud into your educational app requires three straightforward steps. You start by securing your access credentials, then format your lesson text into a standard JSON payload, and finally process the returned audio file for playback.
This process works seamlessly with existing HTTP clients and requires no complex middleware, making it ideal for indie developers building voice features for teachers and students.
Get API key
Visit the /get-api-key/ page to sign in via Google or create an account with your email. Once authenticated, you will receive a unique Bearer token (starting with 'tts-') and see your available balance and character count on the dashboard.
This key is the only credential you need for all API requests. You can generate a new key at any time if needed, and the old one stops immediately.
- Supports Google sign-in or email/password registration
- Key format: Bearer tts-...
Send request
Use the OpenAI SDK or any HTTP client to send a POST request to https://api.playz555.com/v1/audio/speech. Include your API key in the Authorization header and specify your desired model ('tts-1' or 'tts-1-hd'), voice, input text, and language.
Ensure your text does not exceed 4096 characters per request. If your lesson is longer, split it into chunks and join the resulting audio files later.
- Endpoint: POST /v1/audio/speech
- Model options: tts-1 or tts-1-hd
- Auth header: Bearer tts-...
Handle response
Upon successful synthesis, the API returns an audio file in your chosen format (mp3, wav, opus, flac, or pcm). You can save this file to your server or play it on the user’s device.
If the request fails, no charge is applied, and you will receive an error message detailing the issue, allowing you to retry or adjust your input parameters.
- Formats: mp3, wav, opus, flac, pcm
- Failed requests are free
Data flow
Data moves from your app to our cloud servers, where your lesson text is converted into synthetic speech. This process keeps your local environment clean while delivering high-quality audio files ready for playback in any educational setting.
Input text
Your application sends the text payload to our API endpoint. Each request can contain up to 4096 characters, including spaces and punctuation. The system detects the language automatically or uses the specified ISO code.
Cloud processing
Requests are processed sequentially, meaning under heavy load a request may wait in a queue. The engine generates audio at roughly real-time speed, taking about 25 characters per second for standard lengths. Short phrases may take a few seconds to complete.
Audio return
The server returns the generated audio file directly in the response. Input text is used only for synthesis and not stored for training. Generated audio is returned immediately and not retained on our servers, ensuring a clean data flow for your students.
Cost model
Our pricing is straightforward: you pay only for the characters you process. The rate is $10 per 1 million characters, which equals $0.01 per 1,000 characters. Spaces and punctuation count toward this total. If a synthesis request fails, you are charged nothing, and any pre-charged amount is returned in full.
Pay per character
You are billed based on the exact length of the input text. This includes every space and punctuation mark. There are no hidden fees for processing or formatting.
No server costs
Unlike self-hosted solutions, you do not need to maintain voice servers or manage GPU instances. You simply send a request and receive an audio file. This eliminates infrastructure overhead, allowing you to focus on building your educational app or teacher tool.
Scalable pricing
Start with a free trial of $0.50 credit, valid for 7 days. As your usage grows, top up with USDT (TRC-20) starting from $5. Your balance never expires, and there are no monthly subscriptions or minimum spend requirements.
Technical requirements
To use our text-to-speech API, your application needs a stable internet connection. Requests are processed in the cloud, so local processing power doesn’t matter. You just need to send text and receive an audio file over HTTPS.
Your code requires an HTTP client to handle the POST requests and a JSON parser to interpret the response. Most modern languages have built-in libraries for this, making integration straightforward for indie developers building educational apps or accessibility tools.
Internet connection
A reliable internet connection is essential since all synthesis happens on our servers. Your app sends the text payload and waits for the audio file to return. Latency depends on queue load, but typical generation is near real-time for long texts.
- HTTPS required for all requests
- No local TTS engine needed
- Works on any device with web access
HTTP client
Use any standard HTTP library to send the POST request to https://api.playz555.com/v1/audio/speech. Pass your Bearer token in the Authorization header. The client handles the connection details, so you focus on the payload structure.
- Supports any language with HTTP libraries
- Simple POST request structure
- Handles headers automatically
JSON parser
The API returns the audio file data directly in the response body. Parse this response to extract the audio bytes. Ensure your parser handles the input field (up to 4096 characters) and response_format correctly.
- Parse JSON response body
- Extract audio data or URL
- Handle up to 4096 characters per request

Security
Security is built into every interaction. We use standard Bearer token authentication to ensure only your API key can access your account. HTTPS encryption protects your requests during transit, keeping your data safe as it moves between your server and our cloud.
We respect your privacy by not storing the audio files we generate. Input text is processed solely to create the audio file and is not used for training models. Only request metadata, such as time and status, is retained for billing purposes.
Bearer token
Every request must include your unique API key in the Authorization header. We support a single active key per account, which can be rotated instantly if needed.
This simple method integrates with any HTTP client, ensuring that only authorized requests trigger character usage from your balance.
- Key format: tts-...
- Rotate key anytime via dashboard
HTTPS only
All communication occurs over secure HTTPS connections. Your text and credentials are encrypted in transit, preventing interception by third parties.
Our API endpoint is strictly secured, ensuring that your educational content and exercise texts remain private during synthesis.
No data storage
Generated audio files are returned in the response and not stored on our servers. Input text is used only for synthesis and is not used for training.
We retain minimal metadata for billing accuracy, ensuring transparency without compromising your content's privacy.
Limitations
Our API is designed for straightforward text-to-audio conversion, but it has specific boundaries. Understanding these limits helps you design robust educational apps and audio players without unexpected errors during peak usage or when handling long lesson texts.
The system processes requests sequentially, so high volume may introduce slight delays. However, the predictable pricing and clear constraints make it easy to plan your development cycle effectively.
Character limits
Each API request accepts a maximum of 4,096 characters, including spaces and punctuation. For longer texts like full lessons, you must split the input into chunks and join the resulting audio files.
Short phrases may take a few seconds to generate, while longer texts process at roughly real-time speed (25 characters per second).
- Max 4,096 characters per request
- Spaces and punctuation count toward the limit
- Split longer texts manually for best results
Rate limits
You are allowed 60 requests per minute per API key. Before your first top-up, this limit is stricter at 10 requests per minute.
Requests are processed one after another, so under heavy load, a request may wait in a queue before synthesis begins.
- 60 requests per minute after top-up
- 10 requests per minute for new accounts
- Sequential processing may cause minor delays
No SSML
We do not support Speech Synthesis Markup Language (SSML). This means you cannot control pronunciation, pauses, or emphasis via XML tags.
The API uses a simple JSON body with a voice preset and optional language code to determine output. For complex audio needs, you must handle formatting in your app code.
Voices are based on licensed recordings and carry an inaudible synthetic watermark, ensuring clarity without complex markup overhead.
- No SSML support
- No custom pronunciation lexicons
- Simple JSON input only
Comparison
Comparing our API against local engines or other providers helps you choose the right architecture for your educational app. Local TTS requires managing device resources, while our cloud API offloads processing to our servers.
vs local TTS
Local TTS runs on the user’s device, consuming CPU and battery. Our API sends text to our cloud, returning ready-to-play audio files. This keeps your app lightweight and ensures consistent voice quality across all devices, from low-end tablets to high-end phones.
- Offloads processing power to our servers
- Consistent audio quality across all devices
- No local model installation or updates needed
vs other APIs
We focus on simplicity and specific educational use cases. Unlike complex platforms offering dozens of models, we provide two clear options (tts-1 and tts-1-hd) with straightforward pricing. We do not charge for monthly plans or seats, making it easier for indie developers to budget.
- Flat rate: $0.01 per 1,000 characters
- No monthly plans or hidden fees
- Simple JSON integration compatible with OpenAI SDKs
Pros and cons
Our strength is predictable pricing and easy integration. You pay only for what you use, with failed requests refunded. The trade-off is that you need an internet connection for every request, and you cannot use SSML for fine-grained control over pronunciation or pauses.
- Predictable per-character pricing
- Failed requests are free
- Requires internet connection
- No SSML support
Next steps
Ready to add voice to your educational app? Start by creating an account to receive $0.50 in trial credit, valid for seven days. This allows you to generate approximately 50,000 characters of audio without any financial commitment, letting you test voice quality and integration speed immediately.
Try free trial
Sign up via Google or email on our get-api-key page. You will receive a unique API key and access to your dashboard, where you can monitor usage and balance. This trial credit is perfect for validating your integration workflow before committing to paid top-ups via USDT.
Read docs
Our documentation provides concrete examples for sending text to our speech endpoint. You will find ready-to-use curl commands and details on supported voices like Aria or Nova, along with parameters for speed and language. Understanding the 4096-character limit and rate limits ensures your app handles long lessons smoothly.
Build app
Integrate the API into your educational platform by sending JSON requests and receiving audio files. Teachers can instantly convert lessons or exercises into audio for students to listen to anywhere. With transparent pricing at $10 per million characters, your costs scale directly with usage, keeping overhead low for indie developers.

Support
We keep things simple. Support is available by email only, with no phone numbers or live chat to navigate. Our documentation is the primary resource, offering clear examples and integration guides tailored for indie developers building educational tools.
There is no dedicated community channel or forum to check. We focus on providing reliable, straightforward access to our TTS API so you can build your voice features without unnecessary overhead.
Email support
For any issues with your API key, billing, or integration, reach out via email. We do not offer phone support or real-time chat, ensuring your queries are handled thoroughly without the noise of live queues.
Documentation
Our docs cover everything from setting up your API key to handling rate limits. You will find ready-to-use curl examples and clear explanations of request fields like voice and speed to help you integrate quickly.
Community
We do not currently host a public community forum or social channels. Instead, we rely on clear, self-service documentation to guide developers through common integration steps and troubleshooting scenarios.
Listen to the 8 voices
Each sample below was generated by this API from the same sentence. Help teachers manage their classrooms by integrating essential tools directly into the learning platform.
23 languages
Any voice speaks any of these languages.
