Frequently asked questions
Which TTS API is best for dubbing?
Q: Which TTS API is suitable for dubbing? A: Our API is optimized for professional dubbing pipelines, offering consistent synthetic voices across 23 languages. You can generate audio from scripts using eight distinct voice presets, ensuring uniform quality for localization teams without managing individual voice talent for every language project.
How many languages do you support?
We support 23 languages including English, Spanish, German, Japanese, and Arabic. Any voice can speak any of these languages. If the language is not specified, the system guesses it from the script, defaulting to English for Latin text.
Is your API cheaper than competitors?
We charge $10 per 1 million characters, or $0.01 per 1,000 characters. Failed requests are free, so you only pay for successful synthesis. This flat rate applies to both tts-1 and tts-1-hd models without monthly plans or minimum spend.
Do you have a free tier?
Accounts created with Google sign-in receive $0.50 of credit, valid for 7 days, which covers about 50,000 characters. Email-based accounts start without trial credit. You can top up with USDT on the TRON network starting at $5.
Can I use your API for YouTube?
Yes, you can use our API for YouTube. Generated files carry an inaudible watermark marking them as synthetic speech. The voices are based on licensed recordings from LibriTTS-R (CC BY 4.0) and LibriVox public-domain audiobook readings, suitable for content creation.
Is the voice quality high?
We offer eight presets like Aria, Nova, and Atlas, based on licensed recordings. Each generated file carries an inaudible watermark. Our voices provide clear, consistent audio suitable for professional dubbing workflows.
Do you support SSML?
No, we do not support SSML. You send plain text via JSON to the speech endpoint. If you need precise control, you can split text into parts and adjust speed between 0.25 and 4.0 using the standard request parameters.
How fast is the API?
Typical speed is roughly real time, about 25 characters of text per second of generation. Short phrases may take a few seconds. Requests are processed sequentially, so under load, a request may wait in a queue before synthesis begins.
Is there a voice cloning option?
No, we do not offer custom voice cloning. You choose from eight preset voices like Felix, Luna, or Orion. These are based on licensed recordings and cannot be customized or cloned further. We do not upload your own voice for cloning.
Can I export audio files?
Yes, you receive the audio file directly in the API response. You can choose formats including mp3, wav, opus, flac, and pcm. The audio is not stored by us; it is returned immediately for you to download and use in your pipeline.
Do you offer SLA?
No, we do not offer an SLA or uptime guarantee. We are an independent storefront without enterprise contracts or certifications. Support is provided via email only, with no phone number or live chat available.
Is there a mobile app?
No, there is no mobile app or mobile SDK. We provide a standard REST API compatible with the OpenAI SDK. You can integrate directly into your existing tools using HTTP requests or any programming language that supports JSON over HTTPS.
Can I integrate with WordPress?
No, we do not offer a WordPress plugin. However, you can integrate our API into any WordPress site using custom code. Since we support standard HTTP requests, you can use our curl examples or OpenAI SDK to connect your theme or plugin.
Do you have a developer portal?
We provide documentation at /docs/ and a key management page at /get-api-key/. You can view your balance, usage, and generate a new API key. We do not have a separate branded portal; use the standard OpenAI SDK with our base URL.
Criteria for Selection
Selecting the right text-to-speech API requires balancing linguistic reach with audio fidelity. For localization agencies, the primary constraint is often the number of supported languages and the consistency of voice quality across different scripts. A robust API must handle diverse phonetic structures without requiring separate voice models for each region.
The pricing model directly impacts your bottom line, especially when processing large volumes of dialogue for dubbing pipelines. Transparent per-character billing ensures you only pay for what you generate, avoiding the overhead of unused monthly seats or hidden fees that can erode margins on high-volume projects.
Language Coverage
Your API must support at least 23 languages, including key markets like Arabic, Chinese, Japanese, and German. Ensure the solution allows any voice to speak any supported language, providing flexibility in casting. Auto-detection helps streamline workflows, though explicitly setting the language code for non-English Latin texts prevents errors.
- Support for 23 distinct languages
- Cross-language voice capability
- Explicit language parameter support
Voice Quality
Consistency is critical for dubbing teams working across multiple projects. The API offers eight preset voices, ranging from warm narrators to energetic promo styles. These voices are derived from licensed recordings, ensuring a professional baseline. Generated audio includes an inaudible watermark, clearly marking it as synthetic speech for rights management.
Voice selection should match the tone of your content, whether it is a soft storytelling piece or a neutral news broadcast. The ability to adjust speed between 0.25 and 4.0 allows fine-tuning for lip-sync requirements without re-generating files.
- 8 distinct voice presets
- Licensed source recordings
- Inaudible synthetic watermark
Pricing Model
Cost efficiency is paramount for localization agencies. The API charges $0.01 per 1,000 characters, with a clear per-character model. Failed requests are free, ensuring you do not pay for errors. This pay-as-you-go structure avoids the waste of unused monthly seats, making it ideal for variable project loads.
A small free trial credit is available for new accounts, allowing you to test quality before committing. Top-ups are processed via USDT on the TRON network, with no minimum spend or monthly subscriptions, providing complete control over your budget.
- $0.01 per 1,000 characters
- Free failed requests
- No monthly subscriptions
Our API Overview
VerbaSync offers a streamlined text-to-speech API designed specifically for localization and dubbing workflows. Our infrastructure delivers consistent, high-quality synthetic audio files directly from your scripts, eliminating the overhead of coordinating human voice talent across multiple languages.
The service relies on eight distinct voice presets and supports 23 languages, ensuring your content sounds natural and professional. By using a familiar OpenAI-compatible endpoint, your team can integrate quickly without learning a new SDK or mastering complex request structures.
8 Preset Voices
We provide eight distinct voice presets, including female options like Aria and Nova, and male voices such as Felix and Atlas. These voices are based on licensed recordings from LibriTTS-R (CC BY 4.0) and LibriVox public-domain audiobook readings, offering a range of tones from warm narration to energetic promos.
Each generated audio file includes an inaudible watermark, marking it as synthetic speech. This ensures transparency while maintaining high audio quality for professional dubbing pipelines.
- Aria: Warm, clear narrator
- Nova: Bright, upbeat
- Luna: Soft, storytelling
- Sage: Calm, instructional
- Felix: Energetic, promo
- Milo: Friendly, conversational
- Atlas: Neutral, news
- Orion: Deep, documentary
23 Languages
Our API supports 23 languages, including 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, allowing for flexible casting.
If the language field is not set, the system guesses the language from the script, defaulting to English for Latin text. For non-English Latin-script text, we recommend setting the language parameter explicitly to ensure accuracy.
OpenAI Compatible
Our API endpoint is POST https://api.ux45.info/v1/audio/speech, with a JSON body identical to the OpenAI speech endpoint. This means you can use the official OpenAI SDKs by simply changing the base_url to https://api.ux45.info/v1 and using your unique API key.
You can also use the GET /v1/voices endpoint to retrieve available voices, languages, formats, and pricing information. This compatibility ensures a smooth transition for teams already familiar with OpenAI’s API structure.
Voice Variety
Selecting the right voice is critical for maintaining narrative consistency across localized content. Our API offers eight distinct presets designed to suit various dubbing contexts, from warm narration to energetic promos.
Each voice is derived from licensed recordings, ensuring high quality while keeping licensing overhead low for agencies managing multiple languages and projects simultaneously.
Female Options
We provide four female voices, each crafted for specific tonal needs. Aria offers a warm, clear narrator style ideal for documentaries. Nova delivers a bright, upbeat tone perfect for commercial spots.
Luna provides a soft, storytelling voice for emotional narratives, while Sage brings a calm, instructional tone suitable for e-learning or corporate training materials.
- Aria: warm, clear narrator
- Nova: bright, upbeat
- Luna: soft, storytelling
- Sage: calm, instructional
Male Options
Our male voices cover a range of professional and creative styles. Felix is energetic and ideal for promotional content. Milo offers a friendly, conversational tone for relatable brand stories.
Atlas provides a neutral, news-like delivery for factual content, while Orion’s deep voice suits serious documentaries or dramatic storytelling.
- Felix: energetic, promo
- Milo: friendly, conversational
- Atlas: neutral, news
- Orion: deep, documentary
Tone Matching
Each voice is based on licensed recordings from LibriTTS-R, ensuring consistent quality. You can select the preset that best matches your script’s emotional tone.
All voices support 23 languages, allowing you to maintain consistent character voices across different localized versions of your content without re-recording.
image":
Language Support
Localization teams need consistent audio across many languages. Our API supports 23 languages, allowing agencies to generate high-quality dubbing without managing separate voice talent for each region.
Supported Languages List
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. Any voice can speak any of these languages, ensuring consistent quality.
Excluded Languages
We do not support Vietnamese, Indonesian, Thai, Ukrainian, Romanian, Czech, Bengali, or other languages outside our core list. Check your project requirements before integrating.
Auto-Detection
If you omit the language field, the API guesses the language from the script. Latin text defaults to English. For non-English Latin-script text, always set the language parameter to ensure accuracy.
Pricing Comparison
VerbaSync charges $10 per million characters, translating to $0.01 per 1,000 characters. This flat rate applies to both tts-1 and tts-1-hd models, ensuring predictable costs for high-volume localization pipelines where character counts remain consistent across translations.
Unlike traditional agencies that require monthly retainers or seat licenses, we operate on a strict pay-as-you-go model. There are no minimum spends, no monthly plans, and no unused credits expiring. Your balance never expires, allowing you to scale usage up or down without financial penalty.
Per Character Cost
Every character, including spaces and punctuation, counts toward your usage. At $0.01 per 1,000 characters, generating one hour of dialogue typically costs a few cents, depending on script length and speed settings.
Monthly Plans vs Pay-As-You-Go
We do not offer monthly subscription tiers or per-seat licenses. You only pay for what you synthesize. This model eliminates the risk of paying for idle team members or underutilized API capacity during quiet production weeks.
Hidden Fees
There are no hidden fees. Failed requests are free, and any charge for a failed synthesis is returned in full. We do not add VAT or invoice processing fees. The only payment method is USDT (TRC-20), with no card processing surcharges.
- Failed requests are refunded in full
- No VAT or invoice fees
- No minimum spend requirements
Technical Integration
Integrating our API into your dubbing pipeline is straightforward, leveraging a request shape identical to the OpenAI speech endpoint. You simply change the base_url to https://api.ux45.info/v1 and use your unique API key. This allows existing scripts to work with minimal code changes, ensuring rapid deployment for localization teams without relearning complex endpoints.
The system accepts standard JSON bodies with fields like model, input, and voice, returning audio files directly. This compatibility means you can use official OpenAI SDKs or simple HTTP requests, maintaining flexibility as your automation workflows evolve.
API Ease of Use
The endpoint POST https://api.ux45.info/v1/audio/speech handles all synthesis logic. You send text (up to 4096 characters) and receive an audio file in formats like MP3, WAV, or FLAC. For longer scripts, split the text into chunks and join the resulting audio files, a process easily automated in Python or Node.js.
Authentication is handled via Authorization: Bearer with a single active key per account. If you need to rotate credentials, issuing a new key immediately invalidates the old one, ensuring secure access control for large teams managing multiple environments.
- - Standard JSON request body
- - Supports MP3, WAV, OPUS, FLAC, PCM
- - Single active API key per account
- - Immediate key revocation upon issuance
SDK Compatibility
Because the request shape mirrors the OpenAI speech endpoint, official OpenAI SDKs work seamlessly by adjusting the base_url. This eliminates the need for custom HTTP clients or complex parsing logic, allowing your developers to focus on integration rather than protocol details.
We do not provide a proprietary SDK, but the open standard ensures broad compatibility. You can integrate with any language that supports HTTP requests, making it easy to plug into existing CI/CD pipelines for automated dubbing workflows.
Rate Limits
Each API key is limited to 60 requests per minute. For new accounts before the first top-up, the limit is 10 requests per minute. This ensures fair usage and consistent performance for your automation scripts.
Requests are processed sequentially, so under heavy load, a request may wait in a queue. Plan your batching strategy accordingly, keeping the 4096-character limit per request in mind to minimize the number of API calls needed for long scripts.
Data Privacy
When you send text to our API, the input is used exclusively to generate the audio response. We do not use your scripts or dialogue lines to train our speech models, ensuring your localization assets remain proprietary and distinct from our general training data.
Generated audio files are returned directly in the API response and are not stored on our servers after delivery. This minimizes data retention risks for agencies handling sensitive scripts or proprietary content for multiple clients simultaneously.
Training Data Usage
Your input text is processed solely for synthesis. We do not retain your raw text or the resulting audio for model improvement, keeping your localization projects isolated from our broader dataset.
This ensures that high-value scripts for film, gaming, or e-learning remain your exclusive intellectual property without contributing to the voice models available to other customers.
- Input text used only for immediate synthesis
- No use of customer scripts for training
- Audio returned in response, not stored
Storage Policies
We maintain minimal request metadata, including timestamp, character count, and status, strictly for billing and usage verification. This data is retained only as long as necessary for accounting purposes.
No long-term archival of your audio files or source texts occurs on our infrastructure, reducing the attack surface for data breaches and simplifying data deletion requests.
- Metadata kept for billing only
- No long-term audio storage
- Minimal data retention period
GDPR Compliance
As a data processor for your content, we support your obligations under GDPR by providing clear data handling practices. Since we do not store your content, we facilitate easier compliance for data subject access and erasure requests.
Our infrastructure supports standard data protection requirements, allowing localization agencies to confidently use our API for EU-based projects.
- Supports GDPR data processor roles
- No content storage simplifies erasure
- No formal certification, but aligned practices

Customer Support
VerbaSync provides support exclusively via email, ensuring that every inquiry is tracked and resolved without the noise of phone queues or live chat interruptions. There is no phone number or live chat widget; you will receive a dedicated response from our technical team directly to your inbox.
Email Support
Our email support is the single channel for all technical and billing questions. Since we do not offer phone support or live chat, this focused approach ensures that your queries about API integration, voice selection, or billing discrepancies are handled by a single, knowledgeable team member rather than a generalist.
- Single point of contact via email
- No phone number or live chat
- No subscription-based support tiers
Response Time
While we do not guarantee a specific SLA, our team prioritizes clear, actionable answers over speed metrics. You can expect a thoughtful response to your email, particularly for complex integration issues involving rate limits or voice selection for dubbing pipelines.
Documentation Quality
Our documentation is designed to get your team synthesizing audio quickly. It includes ready-to-use curl examples, detailed explanations of the OpenAI-compatible endpoint structure, and clear guides on handling the 4096-character input limit for long scripts.
- Clear curl examples
- OpenAI SDK compatibility guides
- Character limit handling instructions
Use Case Examples
Synthetic voices streamline the production pipeline for localization teams, ensuring consistent audio quality across multiple languages without managing individual talent contracts. By using our API, agencies can generate high-quality audio files directly from scripts, optimizing workflows for large-scale projects.
E-Learning Dubbing
Generate consistent narrations for courses in multiple languages. Use voices like Sage for instructional clarity or Luna for storytelling modules. The API handles up to 4096 characters per request, allowing you to batch long scripts efficiently.
- Consistent voice across 23 languages
- Support for instructional and narrative tones
Corporate Training
Produce clear, professional audio for internal training materials. Voice options like Atlas ensure neutral delivery for news-style updates, while Felix adds energy for promotional content. All audio is watermarked as synthetic, maintaining transparency in corporate communications.
- Neutral and energetic voice options
- Transparent synthetic audio watermarking
Video Game Localization
Rapidly prototype dialogue for characters across different regions. With 8 distinct preset voices, you can match character personalities without cloning custom voices. Use the API to generate MP3 or WAV files quickly, integrating them directly into your pipeline.
- 8 distinct preset voices
- Fast generation for rapid prototyping
Pros and Cons
VerbaSync offers a straightforward, transparent pricing model that scales with your actual usage, making it ideal for agencies with fluctuating project volumes. The inclusion of 23 languages and 8 consistent voice presets reduces the overhead of managing external talent for every script.
However, the lack of SSML and custom voice cloning means it is not a replacement for highly specific brand voices. It is suited for teams prioritizing speed, consistency, and cost-efficiency over granular audio control.
Strengths
The API’s compatibility with OpenAI SDKs simplifies integration for developers already familiar with standard TTS workflows. With 60 requests per minute, the system handles bulk processing efficiently, and failed requests are free, ensuring you only pay for successful synthesis.
- OpenAI SDK compatibility for easy integration
- Transparent per-character pricing with no hidden fees
- Failed requests are free
- Consistent voice quality across 23 languages
Limitations
The service does not offer custom voice cloning, SSML support, or streaming capabilities. Users must manage text splitting for longer scripts, and the rate limit of 60 requests per minute may require queuing strategies during high-volume periods.
- No custom voice cloning
- No SSML support
- No streaming or WebSocket support
- Rate limit of 60 requests per minute
Best Fit
This API is ideal for localization agencies needing consistent, licensable synthetic voices for dubbing pipelines without the overhead of managing multiple voice talents. It is less suitable for projects requiring precise emotional control or unique brand voices.
- Localization and dubbing agencies
- Teams needing consistent voice quality
- Projects with fluctuating volume needs
- Budget-conscious projects prioritizing cost-efficiency
Final Recommendation
Choosing the right TTS API depends on your team’s scale and workflow. VerbaSync offers a straightforward, character-based pricing model that scales cleanly with volume, avoiding the overhead of monthly subscriptions or seat limits.
For Small Teams
Start with the free trial credit to test quality. The simple API and OpenAI SDK compatibility mean minimal integration time, letting you focus on content rather than infrastructure.
- No monthly commitments
- Instant API key activation
For Large Agencies
Consistent voice presets across 23 languages ensure brand uniformity. High character limits and bulk processing capabilities support heavy dubbing pipelines without complex licensing management.
- 23 languages supported
- Consistent voice presets
For Budget-Conscious Projects
Pay only for what you use at $10 per million characters. Failed requests are free, and USDT top-ups allow precise budget control without hidden fees.
- $10 per 1M characters
- Free failed requests
Getting Started
To begin, visit our /get-api-key/ page and sign up using your Google account for an instant $0.50 trial credit, or create an account with an email and password. Once registered, you receive a unique API key ready for immediate use.
After signing up, you can make your first API call using standard HTTP POST requests or by configuring the OpenAI SDK with our base URL. The dashboard displays your key, balance, and a ready-to-use cURL example for quick testing.
Sign Up Process
Visit the /get-api-key/ page to create your account. You can authenticate via Google for immediate access to $0.50 trial credit, or register with an email and password. Accounts are specific to this site, ensuring straightforward management for your team.
After registration, your account dashboard displays your active API key, current balance, and remaining characters. You can generate a new key at any time, which immediately invalidates the previous one, ensuring security without downtime.
- Google or email/password authentication
- Instant $0.50 trial credit for Google sign-ins
- Dashboard displays key, balance, and usage
First Request
Use the standard OpenAI-compatible endpoint POST /v1/audio/speech. Send your text (up to 4,096 characters) in the JSON body along with your chosen model, voice, and response format. Include your API key in the Authorization header.
For longer scripts, split the text into chunks of 4,096 characters or less. Synthesize each part separately and join the resulting audio files to create a complete dub. Requests are processed sequentially, so plan your queue accordingly.
- POST to /v1/audio/speech endpoint
- Max 4,096 characters per request
- Use OpenAI SDK or plain HTTP
Monitoring Usage
The dashboard provides real-time visibility into your character consumption, request status, and remaining balance. Failed requests are free, so you can monitor error rates without worrying about unexpected charges.
Request metadata, including time, characters, and status, is retained for billing purposes. Input text is used solely for synthesis and is not stored or used for training, keeping your data secure and private.
- Real-time balance and character tracking
- Failed requests are free
- Billing metadata retained for transparency
Listen to the 8 voices
Each sample below was generated by this API from the same sentence. Failed requests are free, ensuring you do not pay for errors.
23 languages
Any voice speaks any of these languages.
