Frequently asked questions
Is this an official Azure TTS API?
No. Takaok Assist is an independent text-to-speech API. We are not affiliated with Microsoft, Azure, or any other brand. Our endpoint structure mimics common patterns, but we operate as a separate service with our own infrastructure, pricing, and key management system.
How does the pricing compare to Azure?
We charge $10 per 1 million characters, or $0.01 per 1,000 characters. This flat rate applies regardless of voice or model tier. There are no monthly commitments, no per-request complexity fees, and failed requests are free, simplifying cost prediction for assistive device deployments.
What languages are supported for elderly care?
We support 23 languages, including English, Spanish, German, French, Japanese, and Chinese. Any voice can speak any supported language. If the language is not specified, the system guesses from the script, defaulting to English for Latin text. Vietnamese and Thai are not supported.
Can I use the OpenAI SDK with this API?
Yes. Our API matches the OpenAI speech endpoint shape. You can use the official OpenAI SDK by changing the base_url to https://api.takaok.info/v1 and providing your Takaok API key. This allows product teams to integrate quickly without rewriting existing client code.
How many characters can I send per request?
Each request supports up to 4,096 characters of input text. For longer texts, split the content into parts of this size and join the resulting audio files. This ensures consistent processing and avoids timeouts during synthesis for longer narratives or instructions.
Is there a minimum monthly spend?
No. There are no monthly plans, no seats, and no minimum spend requirements. You pay only for the characters you generate. Balances do not expire, and you can top up as needed using USDT on the TRON network.
Do you offer voice cloning for specific patients?
No. We do not offer custom voice cloning, voice design, or uploading of your own voice. We provide 8 preset voices based on licensed recordings. Each generated file includes an inaudible watermark to mark it as synthetic speech.
How long does audio generation take?
Generation is roughly real-time, averaging about 25 characters of text per second of audio. Short phrases take a few seconds. Requests are processed sequentially, so under load, a request may wait in a queue before synthesis begins.
Are failed requests charged?
No. If synthesis fails, the charge is returned in full. You only pay for successful audio generation. This ensures that network issues or invalid inputs do not incur unnecessary costs for your assistive device applications.
What audio formats are supported?
We support mp3, wav, opus, flac, and pcm. You can specify the format in the request body. These formats cover most assistive device playback needs.
Can I use this for commercial products?
Yes. The API is designed for integration into commercial applications. Input text is used only to produce audio and is not used for training. Generated audio is returned in the response and not stored, ensuring privacy for user interactions.
Is there a free trial available?
Yes. Signing in with Google provides $0.50 of credit, valid for 7 days, covering about 50,000 characters. Email-based accounts start without trial credit. This allows product teams to test integration and voice quality before committing to usage.
How do I switch my existing integration?
Update your SDK's base_url to https://api.takaok.info/v1 and replace your API key. The request shape matches the OpenAI standard. Ensure you use one of our 8 preset voices and adjust the speed parameter if needed for elderly users.
What happens to my input text data?
Input text is used solely to generate the audio response and is not used for training models. The generated audio is returned in the response and not stored. We retain request metadata, such as time and character count, for billing purposes.
First request
curl
curl https://api.takaok.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.mp3Why Switch from Azure for Assistive Tech?
Legacy providers often charge per request or per second of audio, creating unpredictable costs for assistive apps that generate short, frequent phrases. Our API charges strictly per character, giving you precise control over your development budget.
Predictable Character Pricing
You pay $0.01 per 1,000 characters, regardless of audio duration. This model eliminates the surprise of billing spikes when your device generates longer sentences or repetitive prompts for elderly users.
- Flat rate: $10 per million characters
- Spaces and punctuation count as characters
- Failed requests are free
Simplified SDK Integration
Our API mirrors the OpenAI speech endpoint structure. You can switch from your current provider by simply updating the base URL and injecting your API key into existing code.
- POST /v1/audio/speech endpoint
- Compatible with OpenAI SDKs
- Standard JSON request body
No Minimum Spend Required
There are no monthly subscriptions, seat licenses, or minimum spend requirements. You only pay for the characters you actually use, making it ideal for prototyping or small-scale deployments.
Available Voices for Elderly Care
Choosing the right voice is critical for elderly users who may have hearing impairments or cognitive fatigue. Our eight presets are designed for clarity, warmth, and natural pacing, ensuring that text-to-speech output remains engaging without becoming fatiguing over long reading sessions.
Each voice is derived from licensed public-domain recordings, providing a consistent and recognizable tone. This consistency helps users build familiarity with their assistive device, reducing the cognitive load required to process synthetic speech compared to variable, less distinct voices.
Clear Narrator Voices
For general reading assistance, Aria (warm, clear narrator) and Luna (soft, storytelling) provide excellent readability. Aria’s clarity ensures crisp articulation of complex sentences, while Luna’s softer tone is ideal for bedtime stories or relaxed listening environments.
These voices handle the 4096-character limit effectively, allowing long texts to be synthesized without abrupt tonal shifts. The natural pacing helps elderly users follow along without needing to re-read sections due to rushed delivery.
- Aria: Warm, clear narrator ideal for news and articles.
- Luna: Soft, storytelling tone perfect for fiction and audiobooks.
Calm Instructional Tone
Sage (calm, instructional) is optimized for step-by-step guides and medication reminders. Its steady pace and neutral inflection reduce anxiety often associated with urgent or complex instructions. This makes it ideal for smart home devices guiding users through routines.
Atlas (neutral, news) offers a straightforward delivery for factual content. Its lack of excessive emotion ensures that information is conveyed accurately, which is vital for users relying on speech for critical daily information.
- Sage: Calm, instructional tone for guides and reminders.
- Atlas: Neutral, news-style delivery for factual content.
Friendly Conversational Style
Milo (friendly, conversational) brings a human-like warmth to interactive apps. It is particularly effective for companion bots or social engagement tools where a slightly more personal tone enhances user connection without feeling artificial.
Felix (energetic, promo) can be used for upbeat announcements or motivational prompts. While energetic, it remains clear and does not rush, ensuring that users with slower processing speeds can still understand the content comfortably.
- Milo: Friendly, conversational style for social apps.
- Felix: Energetic tone for announcements and prompts.
Supported Languages
Our API supports 23 languages, allowing assistive devices to serve diverse elderly user bases without language-specific infrastructure. Each voice can speak any supported language, ensuring consistent audio quality regardless of the user's native tongue.
Any voice can speak any of the 23 supported languages. German and French speakers benefit from the same synthesis engine used for all supported languages.
English and Spanish
All 23 supported languages are available with any voice. These languages cover the majority of users in assistive tech markets, ensuring clear comprehension for elderly listeners.
You can explicitly set the language code to avoid auto-detection errors, especially when mixing scripts.
- High clarity for narration and instructions
- Consistent voice quality across both languages
German and French
German and French users receive the same reliable synthesis engine used for other languages. This ensures that complex linguistic structures are handled accurately without requiring separate voice models.
Support includes standard regional variations, making it suitable for diverse European care environments.
- Consistent synthesis engine
- Consistent tone across all supported languages
23 Total Languages
We support 23 languages in total, including Arabic, Chinese, Danish, Dutch, Finnish, Greek, Hebrew, Hindi, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Russian, Swahili, Swedish, and Turkish. Any voice can speak any of these languages.
If the language is not specified, the system guesses from the script, but setting it explicitly ensures accuracy for non-English Latin text.
- Arabic, Chinese, Danish, Dutch
- Finnish, Greek, Hebrew, Hindi
- Italian, Japanese, Korean, Malay
- Norwegian, Polish, Portuguese, Russian
- Spanish, Swahili, Swedish, Turkish
Technical Specifications
The API exposes a standard endpoint at https://api.takaok.info/v1/audio/speech. Sending a POST request with your JSON payload returns the synthesized audio file directly. This structure matches the OpenAI speech endpoint, allowing product teams to reuse existing OpenAI SDKs by simply updating the base URL.
Supported output formats include mp3, wav, opus, flac, and pcm. This flexibility ensures compatibility with various assistive devices and legacy systems without requiring additional conversion steps on the client side.
Standard API Endpoint
Use the POST method on /v1/audio/speech. Pass the model (tts-1 or tts-1-hd), input text, voice selection, and desired response format. Authentication is handled via a Bearer token in the Authorization header.
Multiple Audio Formats
Choose from mp3, wav, opus, flac, or pcm based on your device requirements. This allows optimization for bandwidth or quality depending on the assistive technology’s constraints.
Real-Time Generation Speed
Generation takes roughly 25 characters of text per second of audio. Requests are processed sequentially, so under load a request may wait in a queue.
Pricing Structure
Taste our API with a $0.50 free trial (50,000 characters) when you sign in with Google. Standard accounts begin with zero balance. You only pay for successful synthesis; failed requests are refunded in full.
Cost Per Million Characters
Usage is charged at $10 per 1 million characters, equating to $0.01 per 1,000 characters. Spaces and punctuation count toward the total. This linear model ensures predictable costs for your assistive device or elderly care application.
Free Trial Credit
Sign up with Google to receive $0.50 of trial credit, valid for 7 days. Email-based accounts start without trial credit. This allows your team to verify voice quality and integration speed before committing to a balance.
No Hidden Fees
We do not charge for voice selection, language detection, or speed adjustments. There are no monthly plans, seats, or minimum spend requirements. Balance does not expire, and top-ups via USDT (TRC-20) are credited automatically within minutes.

Data Privacy and Ownership
We use your input text solely to generate the audio file for that specific request. Your text is not used for training our models or improving the synthesis engine, ensuring your content remains private and your intellectual property intact.
Input Text Usage Policy
Input text is processed only to produce the audio and is not retained for training purposes. This ensures your unique content remains yours, with no secondary use by the provider.
Audio Storage Terms
Generated audio is returned directly in the API response and is not stored on our servers after delivery. We retain only request metadata—such as time, character count, and status—for billing and usage verification purposes.
Synthetic Watermarking
Every audio file generated by our API contains an inaudible watermark. This digital signature clearly marks the content as synthetic speech, which is valuable for transparency in assistive devices and elderly care applications.
Integration Guide Overview
Switching your assistive device’s audio engine is straightforward because our API mirrors the OpenAI speech endpoint structure. You only need to update the base_url to https://api.takaok.info/v1 and use your new API key. This allows you to leverage existing OpenAI SDKs without rewriting your core integration logic.
Our clear, predictable pricing and simple request format help product teams focus on user experience rather than managing complex infrastructure or unexpected costs during peak usage periods.
OpenAI SDK Compatibility
Our endpoint accepts the same JSON body as the OpenAI speech API. By simply changing the base_url and injecting your tts-... bearer token, your current code works immediately. This reduces integration time for teams already familiar with standard TTS patterns.
- Supports
tts-1andtts-1-hdmodels - Compatible with official OpenAI SDKs
- Standard JSON request body
Quick Start Example
Use the following curl command to generate speech. Replace YOUR_API_KEY with your key from the dashboard. The request sends text and receives an audio file directly in the response stream.
`curl -X POST 'https://api.takaok.info/v1/audio/speech' \ -H 'Authorization: Bearer YOUR_API_KEY' \ -H 'Content-Type: application/json' \ -d '{"model": "tts-1", "input": "Hello, this is a test.", "voice": "nova"}'`
Error Handling Basics
Failed synthesis requests are returned with a 4xx or 5xx status code and are free, ensuring you are not charged for errors. Always check the response status before processing the audio binary. For rate limits (60 req/min), implement a simple retry logic with exponential backoff to handle queue delays during high load.
Common Use Cases
TTS APIs power the audio output for assistive reading tools and ambient smart speakers. Teams need consistent voice quality and predictable costs to serve elderly users reliably.
Our API handles character limits and format requirements without complex infrastructure. Product teams can integrate speech synthesis directly into their devices or apps using standard patterns.
Elderly Reading Assistance
Use the API to convert daily articles or medication instructions into audio. Voices like Aria or Luna provide clear, calm narration that reduces reading strain for older adults.
Support multiple languages including English, Spanish, and French to serve diverse communities without managing separate voice engines.
- Clear narrator voices for long-form text
- Support for 23 languages including Spanish and French
- Predictable cost per character for budget planning
Smart Home Devices
Generate short response audio for voice assistants or notification systems. The API’s speed handles real-time generation for quick interactions.
Use formats like MP3 or Opus to balance quality and bandwidth. The synthetic watermark ensures users know the audio is AI-generated.
- Fast generation for immediate responses
- Compact audio formats like MP3 and Opus
- Inaudible watermark for synthetic content identification
Accessibility Apps
Integrate speech synthesis into mobile or web apps for visually impaired users. The OpenAI SDK compatibility simplifies development for existing codebases.
Handle up to 4096 characters per request; split longer texts into parts and join the audio files. This ensures consistent audio output without manual chunking logic.
- OpenAI SDK compatibility for easy integration
- Automatic text splitting for long documents
- No minimum spend for scalable usage
Get Started Today
Create your account at /get-api-key/ using your Google credentials or an email and password. The process takes seconds, and you receive a $0.50 free trial credit valid for 7 days to test the service immediately.
Sign Up with Google
Visit the registration page and authenticate via Google. Your account is created instantly, and you are eligible for the trial credit right away. This method is the fastest way to begin testing your assistive device’s audio output.
- No credit card required
- Instant account creation
- Includes $0.50 trial credit
Receive API Key Instantly
Your unique API key appears on the dashboard immediately after signup. You can generate a new key at any time, which invalidates the old one instantly. Use this key in your Authorization header to access the API.
Start Generating Audio
Use the OpenAI-compatible SDK or a simple POST request to send text. For assistive devices, choose voices like Sage for calm instructions or Aria for clear narration. The API returns the audio file directly, ready for playback.
- POST to /v1/audio/speech
- Supports 8 distinct voices
- Outputs MP3, WAV, or FLAC
Listen to the 8 voices
Each sample below was generated by this API from the same sentence. Users can distinguish between different types of alerts based on voice alone.
23 languages
Any voice speaks any of these languages.
