Frequently asked questions
What is a Text-to-Speech API?
AssistVoice is a cloud text-to-speech API that converts text into audio files via a simple POST request. It uses the same request shape as OpenAI, allowing you to use the official OpenAI SDKs by changing the base_url to https://api.playsv77.com/v1. This provides a reliable, standard interface for generating natural speech for assistive devices and elderly care applications without complex infrastructure.
How does a TTS API work?
Send a JSON payload with your text, voice selection, and format preference to the /v1/audio/speech endpoint. The system processes the request and returns the audio file. For texts exceeding 4096 characters, split the input into parts and join the resulting audio files. Requests are processed sequentially, so high load may introduce slight delays.
What are the benefits of using a TTS API?
Our API offers transparent per-character pricing with no hidden fees or monthly plans. You pay only for successful synthesis, as failed requests are free. The service supports 23 languages and 8 distinct voices, ensuring clear, natural speech suitable for accessibility. Integration is straightforward using standard HTTP or OpenAI SDKs, reducing development complexity.
Who can use a TTS API?
The API is designed for startups building assistive devices and elderly care apps. It supports developers who need reliable, clear speech synthesis without enterprise overhead. You can sign up with Google or email to get an API key. The simple pricing model and standard integration make it accessible for teams of any size.
What languages are supported?
We support 23 languages: Arabic, Chinese, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hindi, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Russian, Spanish, Swahili, Swedish, and Turkish. Any voice can speak any of these languages. If the language is not specified, it is guessed from the script, defaulting to English for Latin text.
What voices are available?
We offer 8 presets based on licensed recordings. Female voices include Aria (warm narrator), Nova (bright), Luna (soft storytelling), and Sage (calm instruction). Male voices include Felix (energetic), Milo (friendly), Atlas (neutral news), and Orion (deep documentary). All voices are based on licensed recordings from LibriTTS-R (CC BY 4.0) and LibriVox public-domain audiobook readings.
What audio formats are supported?
You can generate audio in MP3, WAV, OPUS, FLAC, and PCM formats. Select the format that best fits your device or application requirements via the response_format field. Each generated file includes an inaudible watermark to identify it as synthetic speech. The API returns the audio file directly in the response for immediate use.
How much does a TTS API cost?
Pricing is $10 per 1 million characters, or $0.01 per 1,000 characters. Spaces and punctuation count toward the total. Failed requests are free, with charges returned in full. You can top up using USDT on the TRON network (TRC-20) with a minimum of $5. There are no monthly plans, seats, or minimum spends.
Is there a free trial?
Yes, signing in with Google provides $0.50 of trial credit, valid for 7 days, allowing approximately 50,000 characters. Accounts created with email and password start without trial credit. Your balance does not expire, and you can top up anytime via USDT. This allows you to test the API’s quality before committing to paid usage.
How do I integrate a TTS API?
Use the OpenAI SDKs by changing the base_url to https://api.playsv77.com/v1. Alternatively, send a POST request to /v1/audio/speech with your API key in the Authorization header. The request body requires the model, input text, voice, and format. This standard approach simplifies integration for existing OpenAI-compatible applications.
What are the rate limits?
The API allows 60 requests per minute per key. Before your first top-up, the limit is 10 requests per minute. Requests are processed sequentially, so under heavy load, a request may wait in a queue. This ensures stable performance for your assistive device or app without sudden throttling issues during normal operation.
Is my data 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 (time, characters, status) solely for billing purposes. This ensures your content remains private and is processed efficiently without long-term retention of the audio files.
Can I use the API for commercial purposes?
Yes, the API is fully available for commercial use in assistive devices and apps. The voices are based on licensed recordings from LibriTTS-R (CC BY 4.0) and LibriVox public-domain sources. The API is fully available for commercial use.
How do I handle errors?
If synthesis fails, the charge is returned in full, so you are not billed for unsuccessful requests. You can monitor the status of your requests and check your balance via the dashboard. For support, contact us via email. We do not offer phone support or live chat, so email is the primary channel for assistance.
Definition of TTS API
Our Text-to-Speech API is a cloud-based service designed for assistive technology startups. It accepts plain text and returns synthesized audio, enabling devices to speak clearly for elderly care and accessibility applications without complex infrastructure.
Text Input
Send up to 4096 characters per request via a simple JSON POST endpoint. The API handles language detection or accepts explicit ISO codes, ensuring accurate pronunciation for assistive contexts.
- Plain text input up to 4096 characters
- Optional language specification for clarity
- Supports standard JSON formatting
Audio Output
Receive synthesized speech as an audio file. The service generates clear, natural-sounding speech suitable for reading assistance, with options for MP3, WAV, OPUS, FLAC, or PCM formats.
- Multiple audio formats (MP3, WAV, etc.)
- Natural-sounding synthetic speech
- Inaudible watermark marks synthetic origin
Cloud-Based Service
No on-premise servers required. The API runs on cloud infrastructure, processing requests sequentially. You interact via standard HTTP calls, making it easy to integrate into existing mobile or web apps.
- No hardware maintenance
- Standard HTTP/JSON interface
- Easy integration for startups
How TTS Works
Our API processes input text through a streamlined cloud pipeline, converting written characters into audible speech.
The synthesis engine selects the appropriate voice preset and applies the requested parameters, such as speed and audio format, to generate natural-sounding speech tailored for assistive devices.
Each request is processed sequentially, ensuring consistent output quality. The final audio file is delivered directly to your application for immediate playback.
Text Processing
The API accepts raw text strings up to 4096 characters. It automatically detects the language based on the script, though you can explicitly set it for better accuracy. Spaces and punctuation are counted toward your character limit.
- Handles up to 4096 characters per request
- Automatic language detection or explicit ISO code setting
- Counts spaces and punctuation as characters
Voice Synthesis
The engine uses licensed recordings from LibriTTS-R and LibriVox to synthesize speech. It applies the chosen voice preset, such as 'Aria' for warm narration or 'Atlas' for neutral news reading, and adjusts the speed between 0.25x and 4.0x.
- 8 distinct voice presets available
- Adjustable speed from 0.25x to 4.0x
- Uses licensed recordings for natural tone
Audio Generation
The system generates the final audio file in your chosen format, such as MP3, WAV, OPUS, FLAC, or PCM. Each file includes an inaudible watermark to identify it as synthetic speech. Failed requests incur no charge, and the audio is returned immediately in the response.
- Supports MP3, WAV, OPUS, FLAC, and PCM
- Inaudible watermark for synthetic identification
- Failed requests are free
Benefits for Assistive Tech
AssistVoice delivers clear, natural speech optimized for accessibility, ensuring that assistive devices and elderly care apps provide understandable audio output for users with visual or cognitive impairments. By converting text to high-quality audio, we enable seamless interaction with digital content without requiring visual attention.
Our API is designed for ease of integration, allowing developers to focus on user experience rather than complex voice engineering. With straightforward JSON requests and support for major OpenAI SDKs, teams can quickly deploy reliable TTS capabilities into their existing workflows.
Accessibility
We prioritize clarity and natural rhythm in synthesized speech, making it easier for elderly users and those with reading difficulties to consume content independently. Our voices are based on licensed recordings, providing clear, natural-sounding speech.
- Clear, natural speech patterns suitable for visually impaired users
- Reduced cognitive load compared to robotic TTS
- Supports diverse reading speeds via adjustable parameters
Ease of Use
Developers can integrate our API using standard HTTP requests or the OpenAI SDK by changing the base_url to https://api.playsv77.com/v1. This familiarity reduces onboarding time and allows startups to leverage existing developer knowledge without learning a new proprietary system.
Response formats like MP3 and WAV are widely supported by existing accessibility tools and hardware, ensuring broad compatibility across different assistive devices.
- Standard JSON and OpenAI SDK compatibility
- Wide format support (MP3, WAV, OPUS, FLAC, PCM)
- Simple integration reduces development overhead
Customization
While we do not offer voice cloning or SSML, our eight preset voices and adjustable speed (0.25–4.0x) allow teams to tailor the audio output to specific user preferences. Users can select voices that best suit their listening comfort, such as calm narration for reading or energetic tones for alerts.
- Eight distinct voice presets for different use cases
- Adjustable speed from 0.25x to 4.0x
- Optional language specification for accurate pronunciation
Technical Requirements
The API is a cloud service, so your assistive device or app needs an active internet connection to send text and receive audio. Latency is typically real-time for long texts, though short phrases may take a few seconds depending on queue load.
You only need standard developer skills to integrate the REST API. No custom SDK or mobile library is required; you can use the OpenAI SDK or plain HTTP requests. A stable connection ensures reliable delivery of synthesized speech files.
Internet Connection
Since AssistVoice is cloud-based, your device or app must have an active internet connection to send text requests and receive audio files. There is no local processing unit.
Typical generation speed is roughly real-time for long texts. Short phrases may take a few seconds, as requests are processed sequentially and may wait in a queue under load.
- Requires stable Wi-Fi or cellular data
- No local hardware acceleration needed
- Cloud-based processing only
API Key
Access is secured via a single Bearer token sent in the Authorization header. You can generate this key on your dashboard at /get-api-key/.
Each account holds one active key. If compromised, you can issue a new key immediately, invalidating the old one instantly. No complex OAuth flows are necessary.
- Bearer token authentication
- Single key per account
- Instant revocation support
Developer Skills
Integration requires basic HTTP knowledge. The endpoint follows a standard JSON structure compatible with the OpenAI SDK.
You can use any language that supports HTTP POST requests. No proprietary SDK, WordPress plugin, or mobile-specific library is required for implementation.
- REST API interface
- JSON request body
- OpenAI SDK compatible
Use Cases
For startups in assistive devices and elderly care, the AssistVoice API transforms static text into clear, natural speech. By sending text to our endpoint, you receive an audio file ready for playback, ensuring high accessibility for users with visual impairments or reading difficulties.
Elderly Care
Generate calming narration for medication reminders or daily schedules. The warm, clear voices like Aria or Luna are suitable for calming narration, while the simple API integration allows care apps to speak instructions clearly.
- Clear narration for medication reminders
- Calming tones for daily schedules
- Simple integration for care apps
Reading Assistance
Convert articles, books, or UI text into audio instantly. With support for 23 languages and up to 4096 characters per request, the API handles long texts by splitting and joining audio files seamlessly, ensuring continuous listening experiences.
- Instant conversion of articles and books
- Support for 23 languages
- Seamless handling of long texts
Voice Commands
Provide audio feedback for user interactions in assistive interfaces. The neutral, news-style voice Atlas or friendly Milo offers clear confirmation tones, enhancing usability for devices where visual attention is limited or eyes are occupied.
- Audio feedback for user interactions
- Clear confirmation tones
- Enhanced usability for limited visual attention
Integration Process
To integrate AssistVoice into your assistive device or elderly care app, start by creating an account on our /get-api-key/ page. You can sign in quickly using Google or set up a standard email and password account. This initial step registers your developer identity and prepares your workspace for API access.
Sign Up
Visit the registration page to create your account. The process is straightforward, requiring only basic contact information or a Google login. Once registered, you receive immediate access to your dashboard, where you can monitor your balance and usage statistics.
- Google or email/password registration
- Instant access to developer dashboard
- No credit card required for trial
Get API Key
After signing up, your unique API key is displayed immediately in your dashboard. This key authenticates your requests to the API. You can regenerate this key at any time, which invalidates the previous one instantly for security. Ensure you store this key securely in your application’s environment variables.
- Key generated instantly upon registration
- Regenerate anytime to invalidate old key
- One active key per account
Make First Request
Use the provided curl example or the OpenAI-compatible SDK to send your first request. Point your base URL to https://api.playsv77.com/v1 and include your Bearer token. Send a POST request to /v1/audio/speech with your text, desired voice, and output format. You will receive the audio file directly in the response, ready for playback in your assistive application.
- Base URL: https://api.playsv77.com/v1
- Standard OpenAI-compatible SDK support
- Returns audio file in response
Supported Languages
Our API supports 23 languages, ensuring clear speech for assistive devices and elderly care apps worldwide. English is the default for Latin-script text. Spanish is fully supported, allowing natural speech generation for Spanish-speaking users. Any voice can speak any of these languages, providing flexibility for diverse user bases without requiring specific voice models per language.
English
English is the default for Latin-script text. This ensures immediate usability for navigation and reading aids without explicit configuration. The API accurately detects the language from the script, making integration straightforward for developers building English-first assistive tools.
Spanish
Spanish is fully supported, allowing natural speech generation for Spanish-speaking users. This supports clear audio output for elderly care applications and accessibility tools where Spanish is the primary language of interaction.
23 Languages
The API supports 23 languages: Arabic, Chinese, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hindi, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Russian, Spanish, Swahili, Swedish, and Turkish. If the language is not set, it is guessed from the script. For non-English Latin-script text, we recommend setting the language parameter explicitly to ensure accurate pronunciation.
- Arabic
- Chinese
- Danish
- Dutch
- French
- German
- Greek
- Hebrew
- Hindi
- Italian
- Japanese
- Korean
- Malay
- Norwegian
- Polish
- Portuguese
- Russian
- Spanish
- Swahili
- Swedish
- Turkish
- English

Voice Options
We offer eight distinct voice presets designed for clarity and natural rhythm, ensuring assistive devices sound helpful rather than robotic. Each voice is trained on licensed recordings, providing a consistent and pleasant listening experience for users.
Female Voices
Aria offers a warm, clear narration style ideal for calming elderly users. Nova provides a bright, upbeat tone for engaging interactions, while Luna delivers a soft, storytelling voice perfect for bedtime stories or relaxation apps.
- Aria: warm, clear narrator
- Nova: bright, upbeat
- Luna: soft, storytelling
- Sage: calm, instructional
Male Voices
Atlas serves as a neutral, news-style voice for clear information delivery. Felix adds energy for promotional content, while Milo creates a friendly, conversational tone for daily check-ins. Orion provides a deep, documentary style for immersive experiences.
- Felix: energetic, promo
- Milo: friendly, conversational
- Atlas: neutral, news
- Orion: deep, documentary
Different Styles
All voices support 23 languages, ensuring broad accessibility. You can adjust the speed between 0.25x and 4.0x to match the user’s hearing capacity or cognitive processing speed, making the API highly customizable for specific assistive needs.
Audio Formats
The API supports MP3, WAV, Opus, FLAC, and PCM formats. MP3 is ideal for mobile apps where file size matters. WAV provides uncompressed quality for local playback or processing pipelines.
Choose PCM for raw data streams or FLAC for lossless archival. All formats include an inaudible watermark to identify synthetic speech. You specify the format in the response_format field of your request.
MP3
MP3 is the standard for web and mobile delivery. It balances quality with small file sizes, making it perfect for assistive devices with limited storage.
- Compressed format for efficient storage
- Ideal for mobile and web applications
- Standard compatibility across devices
WAV
WAV provides uncompressed, high-fidelity audio. Use this format for local playback or when integrating with other audio processing tools that require raw data.
- Uncompressed audio quality
- Best for local playback
- Easy integration with audio tools
Other Formats
We also offer Opus, FLAC, and PCM. Opus is efficient for low-bandwidth connections. FLAC ensures lossless quality for archival purposes. PCM returns raw audio data.
- Opus: efficient for low bandwidth
- FLAC: lossless quality
- PCM: raw audio data
Pricing Model
Our pricing model is designed for predictability and transparency, charging strictly based on usage rather than arbitrary tiers. You pay $0.01 per 1,000 characters, ensuring that every byte of text generates a precise cost without hidden fees or data overage surprises.
Per Character
Billing is calculated at $10 per million characters, which equals $0.01 per 1,000 characters. Spaces and punctuation count toward this total. Failed requests are free, so you only pay for successful synthesis.
No Monthly Fees
There are no monthly subscriptions, seats, or minimum spend requirements. Your balance does not expire, allowing you to top up only when needed. Top-ups are processed via USDT (TRC-20) on the TRON network.
- Zero monthly subscriptions
- No minimum spend
- Balance never expires
Free Trial
New accounts signed in with Google receive $0.50 in credit, valid for 7 days. This provides approximately 50,000 characters to test the API’s quality before committing to top-ups. Email-signup accounts start without trial credit.
Data Privacy
Your input text is used exclusively for generating the audio file and is never used to train our models. Once the audio is returned in the response, the generated content is not stored on our servers, ensuring that your specific content remains transient and private.
No Training Data
Unlike many commercial TTS providers, we do not ingest your text to improve our voice engines. The data flows directly from your request to the synthesis engine and back, with no secondary usage rights claimed for your content.
Inaudible Watermark
Every generated audio file carries an inaudible watermark that clearly marks it as synthetic speech. This helps downstream applications, such as assistive reading devices or elderly care apps, distinguish AI-generated narration from human-recorded audio without requiring user intervention.
Secure Storage
We retain only the request metadata—such as timestamp, character count, and status—for billing and audit purposes. This minimal data set is sufficient to verify charges but contains no text content or audio files, keeping your core data secure and private.
Comparison with Other Services
AssistVoice simplifies voice integration by mirroring the OpenAI SDK structure, allowing startups to switch providers by changing a single base URL without rewriting their codebase. This reduces development friction compared to proprietary SDKs that require extensive library updates.
Our pricing is strictly per character at $10 per million, eliminating complex tiered plans or monthly commitments. Failed requests incur no charge, providing predictable cost control for high-volume assistive devices without hidden fees or minimum spend requirements.
Simplicity
Unlike providers requiring custom SDKs or complex authentication flows, AssistVoice uses standard HTTP requests compatible with existing OpenAI clients. This allows teams to integrate voice capabilities into elderly care apps with minimal engineering overhead, focusing on user experience rather than infrastructure.
Cost
We charge $0.01 per 1,000 characters with no monthly fees or seat limits. This transparent model scales linearly with usage, ensuring that assistive device startups avoid the over-provisioning costs common in tiered enterprise plans. Payment via USDT (TRC-20) is processed automatically.
Accessibility Focus
Our 23 languages and 8 distinct voice presets are optimized for clarity, crucial for elderly users with hearing impairments. We prioritize clear, natural speech over novelty features like SSML or voice cloning, ensuring consistent, reliable audio output for critical communication tasks.
Listen to the 8 voices
Each sample below was generated by this API from the same sentence. Input text is used exclusively for audio generation and never for model training.
23 languages
Any voice speaks any of these languages.
