Frequently asked questions
Is there a limit on the number of words I can convert?
Each API request accepts up to 4,096 characters, including spaces and punctuation. For longer texts, split the input into parts and join the resulting audio files. This ensures reliable processing without exceeding the single-request character limit defined by the endpoint specifications.
Can I use the audio for monetized YouTube videos?
Yes. The generated audio files are returned in the response and not stored by the service. Since input text is not used for training, you retain the rights to use the synthetic speech in your content, including monetized videos, without ongoing fees.
Do I need technical skills to add TTS to my blog?
Basic technical knowledge helps, but the API is designed for simplicity. You can use the provided curl example or standard HTTP requests. Since it follows the OpenAI SDK shape, many developers integrate it easily.
Does the API work with all WordPress themes?
The API is platform-agnostic. It returns standard audio files (mp3, wav, etc.) that any WordPress theme can play via standard HTML5 audio tags. Integration depends on your theme’s ability to embed audio players, not on specific theme compatibility with the API itself.
Can I change the voice after generating the audio?
No. Once an audio file is generated and returned, it is fixed. To change the voice, you must send a new request with the desired voice preset. The service does not store the audio for later modification or re-rendering with different parameters.
Is the audio quality consistent across different languages?
Yes, all 23 supported languages use the same underlying engine. Voices are based on licensed recordings from LibriVox. While language-specific nuances exist, the synthetic quality and clarity remain consistent across English, Spanish, French, German, and other supported languages using the same model.
Do I need to host the audio files myself?
The API returns the audio file directly in the response. You can save it to your WordPress media library or any storage you prefer. The service does not host the files long-term, so you are responsible for storing and serving the generated audio.
Can I use the API for audiobooks?
Yes. The API supports long texts by splitting them into 4,096-character parts. You can join the resulting audio files to create full audiobooks. The pricing is based on character count, making it scalable for longer content like novels or detailed articles.
How do I track my usage?
Your account dashboard displays your balance, characters left, and usage history. You can also view request metadata, including time, characters, and status, which is kept for billing purposes. This data helps you monitor consumption and manage your TRC-20 top-ups effectively.
Is the API reliable during high traffic periods?
Requests are processed sequentially, so under heavy load, a request may wait in a queue. Typical speed is roughly real-time. While there is no SLA guarantee, the system handles volume by queuing requests rather than failing them, ensuring eventual completion.
Can I customize the speed of the speech?
Yes. You can adjust the speech speed between 0.25 and 4.0 by setting the speed parameter in your request. This allows you to slow down complex content or speed up casual narration, giving you precise control over the audio output duration.
Does the service support Indian English or other accents?
The service supports English but does not offer specific accent variants like Indian or Australian English. It uses eight preset voices that speak standard English. You can set the language parameter to en for Latin-script text to ensure correct language detection.
What happens if I delete my account?
Deleting your account removes your access to the API key and dashboard. Generated audio files are not stored by the service, so any files you downloaded remain yours. Billing metadata is retained for accounting purposes as per standard data retention policies for billing.
Can I get a refund if I am unsatisfied?
Failed requests are refunded in full automatically. For successful requests, refunds are not explicitly guaranteed beyond the free trial credit. The trial credit ($0.50) is valid for 7 days. Top-ups via USDT are generally non-refundable.
The Free Trial Option
ScribeSound offers a straightforward way to test our text-to-speech API without any financial commitment. New users who sign up via Google receive $0.50 in free credit, which translates to approximately 50,000 characters. This allowance is sufficient for multiple test runs, allowing you to generate several short blog summaries or chapter intros to evaluate voice quality and audio fidelity before committing to a paid plan.
This trial requires no credit card and is activated instantly upon connecting your Google account on the /get-api-key/ page. The process bypasses manual email verification, provisioning your API key and free credit immediately so you can start generating audio for your WordPress posts right away.
subsections_h3s_and_content_and_bullets_and_image_prompt = { "subs": [ { "h3": "50k Characters Free", "paras": ["You receive $0.50 of credit upon signing up, which covers about 50,000 characters of text. Spaces and punctuation count toward this limit, so plan your test texts accordingly. This amount is enough to generate multiple short articles or several minutes of audio for testing purposes."], "bullets": [] }, { "h3": "Google Sign-Up", "paras": ["The fastest way to access the trial is by connecting your Google account on the /get-api-key/ page. This method instantly provisions your API key and activates the free credit, bypassing manual email verification steps."], "bullets": [] }, { "h3": "Trial Validity", "paras": ["The free trial credit is valid for 7 days from the moment you sign up with Google. After this period, the credit expires if not used. Accounts created with email and password do not receive this trial credit, so choose Google sign-up to get started quickly."], "bullets": [] } ], "image": "A clean, modern illustration showing a WordPress blog post on a laptop screen with a small audio wave icon emerging from it, symbolizing easy text-to-speech integration for content publishers."}
Cost for Heavy Usage
For WordPress publishers processing large volumes of content, ScribeSound charges $10 per 1 million characters, equating to $0.01 per 1,000 characters. Spaces and punctuation count toward this total. Failed requests are free, ensuring you only pay for successful audio generation.
Budgeting is straightforward with no monthly plans or minimum spend requirements. You can top up using USDT on the TRON network, with credits arriving automatically within minutes. This pay-as-you-go model suits blogs of any size without committing to unused seats.
Per Character Pricing
The rate is fixed at $10 per 1 million characters. Every character in your input text, including spaces and punctuation, contributes to this count. This transparency helps WordPress bloggers estimate costs accurately before generating audio for long articles.
Bulk Costs
Since there are no volume discounts or tiered pricing structures, the cost remains linear. Whether you generate 10,000 characters or 10 million, the price per character stays at $0.01. This predictability simplifies financial planning for content-heavy sites.
Budget Planning
Funding your account via USDT (TRC-20) allows for immediate credit availability. There are no subscriptions to manage or invoices to process. You can top up the minimum $5 whenever your balance runs low, ensuring continuous service for your blog.
Failed requests are free, so you do not pay for errors. This protects your budget when testing new voices or formats before publishing to your live site.
- Minimum top-up: $5 via USDT (TRC-20)

Voice Quality Comparison
ScribeSound uses licensed recordings from LibriTTS-R and LibriVox to deliver clear, human-like audio. With eight distinct voice presets like Aria and Felix, the engine provides natural intonation that fits various content tones.
Pronunciation is accurate across 23 languages, with automatic language detection for Latin scripts (defaulting to English). You can explicitly set the ISO code for non-English texts to ensure correct delivery, avoiding guesswork errors.
Human-like Sound
The voices are based on licensed recordings from LibriTTS-R (CC BY 4.0) and LibriVox public-domain audiobook readings. This foundation provides a warm, clear narrator quality without the robotic monotone typical of older TTS engines.
- Eight presets: Aria, Nova, Luna, Sage, Felix, Milo, Atlas, Orion.
- Inaudible watermark marks synthetic audio.
- Licensed recordings ensure consistent quality.
Natural Intonation
The engine handles natural pauses and emphasis, making the audio sound engaging for long-form blog posts. Speed can be adjusted from 0.25x to 4.0x to match your reading pace or audience preference.
Pronunciation Accuracy
Supports 23 languages including English, Spanish, German, and Japanese. If the language isn't set, it defaults to English for Latin text; set the language field explicitly for other Latin-script languages to avoid errors.
- Supports 23 specific languages.
- Explicit language code recommended for non-English Latin text.
- Not supported: Vietnamese, Thai, Ukrainian, etc.
Technical Requirements
To integrate ScribeSound into your WordPress workflow, you first need an API key. Sign up on our /get-api-key/ page using Google or email to receive your unique key. This key authenticates your requests to our API endpoint and tracks your usage against your balance.
API Key Needed
Your API key is the single credential required to access the service. You can generate a new key at any time via your dashboard, which immediately invalidates the previous one. Keep this key secure in your WordPress environment variables or plugin settings to ensure only your site can consume your character quota.
- One active key per account
- Immediate revocation on new key generation
- Format: Bearer tts-...
Internet Connection
Since ScribeSound is a cloud API, your WordPress site needs an active internet connection to request audio generation. When a visitor triggers audio playback, your server sends a POST request to our endpoint. The generated audio file is then returned and streamed to the user. A stable connection ensures minimal latency during the generation process.
- Cloud-based processing
- Requires outbound HTTP access from your server
- No local processing power needed
Browser Support
The API returns standard audio files in formats like mp3, wav, opus, flac, or pcm. Any modern web browser that supports HTML5 audio tags can play these files, ensuring broad compatibility for your readers. You do not need proprietary plugins or specific browser versions to enjoy the audio content on your blog.
- Supports mp3, wav, opus, flac, pcm
- HTML5 audio tag compatible
- Works on desktop and mobile browsers
Content Rights
Generated audio files are yours to use. We do not store the audio after delivery, and input text is used only for synthesis, not for training. This means your content remains yours, with no hidden retention of your source material.
You may use the audio commercially in blog posts, podcasts, or ads. Our voices are based on licensed recordings (LibriTTS-R, CC BY 4.0) and public-domain readings, so you are not restricted by third-party personality rights.
Ownership of Audio
When you request audio via the API, the resulting file is generated for your specific use. We do not keep copies of the audio files after the response is sent. Your input text is processed solely to create that audio and is not used for model training.
Commercial Use
You can use the generated audio commercially, such as in WordPress blog posts, podcasts, or advertisements. Since we do not offer voice cloning or celebrity licenses, you are not restricted by third-party personality rights when using our eight standard presets.
Attribution
Attribution is not strictly required for commercial use, though it is appreciated. Each audio file contains an inaudible watermark marking it as synthetic speech. You are free to embed these files in your WordPress posts without needing to credit ScribeSound explicitly, though linking back is welcome.
Limitations
While ScribeSound offers robust features, understanding its boundaries helps you plan your WordPress content strategy effectively. The API has specific constraints on input size and generation timing that influence how you structure long-form articles.
Character Limits
Each API request accepts a maximum of 4096 characters. For longer posts, you must split the text into smaller chunks and join the resulting audio files. Spaces and punctuation count toward this limit.
Speed Constraints
Generation takes roughly real-time duration, averaging 25 characters of text per second of audio. Short phrases may take a few seconds, while longer texts process sequentially. Under heavy load, requests may queue, causing slight delays.
Format Options
Output is available in mp3, wav, opus, flac, and pcm. Choose mp3 for web compatibility or wav/flac for higher fidelity. There is no streaming endpoint; the full audio file is returned upon completion.
Alternative Solutions
Before committing to an API, consider manual recording or other TTS services. Manual recording requires equipment and editing time, which can delay publishing schedules. Other providers often charge monthly subscriptions or per-minute rates that scale poorly for high-volume bloggers.
Manual Audio Recording
Hiring voice actors or recording yourself ensures unique content but demands significant time for setup, editing, and hosting. This approach works well for short intros but becomes impractical for long-form articles.
- Requires audio editing software
- Higher per-minute cost for professionals
- Slower content turnaround
Other TTS Providers
Many competitors charge monthly fees for access, even for basic usage. Some limit character counts strictly or restrict voice selection. Our API charges only for what you use, with no mandatory monthly plans.
- Monthly subscription models
- Strict character limits
- Limited voice selection
Open Source Tools
Open-source engines like Coqui or Piper offer free software but require technical expertise to install and maintain on your server. They often lack the polish and natural intonation of licensed recordings.

Implementation Steps
To integrate ScribeSound into your WordPress site, you first need a valid API key from your dashboard. While we do not provide an official WordPress plugin, most publishers use simple shortcodes or embed codes generated from the dashboard.
Install Plugin
While we do not provide an official WordPress plugin, most publishers use simple shortcodes or embed codes generated from the dashboard.
- Copy the shortcode from your /get-api-key/ dashboard
- Paste it into your WordPress post editor
Connect API
Ensure your API key is active. You can generate a new key anytime from your account settings; the old one stops immediately.
- Use the POST endpoint for speech generation
- Include your Bearer token in headers
Test Audio
Send a short test request to verify voice quality and speed. Check that the audio file downloads correctly within your browser.
- Test with 100 characters
- Verify MP3 output
Performance Impact
Generating audio on the fly can slow down your WordPress site because each request triggers a remote API call. With typical speeds of roughly 25 characters per second, longer articles may add noticeable latency. Requests are processed sequentially, so under heavy load, a single synthesis might wait in a queue, increasing initial load time.
Page Load Speed
For short phrases, generation takes only a few seconds, but longer texts require splitting into 4,000-character parts. This sequential processing means your page cannot render the audio instantly. Users on slow connections may experience delays before the player becomes interactive.
Server Load
Your WordPress server handles the request logic but offloads the heavy audio processing to our API. This keeps your database and CPU usage low. However, you must respect the 60 requests per minute limit per API key to avoid throttling, especially if multiple users trigger simultaneous generations.
- Offload processing to the API
- Respect the 60 req/min limit
- Monitor key usage via dashboard
Caching Strategies
Since each request is unique, caching the final MP3 file is crucial. Store generated audio on your media library or a CDN. This ensures subsequent visitors hear the same file instantly without hitting the API again, preserving your character balance and reducing server strain.
- Cache generated MP3s
- Use a CDN for distribution
- Store in media library
User Experience
For WordPress bloggers, integrating audio is straightforward. Our API returns standard audio files that play seamlessly in any browser, keeping your content accessible without complex setups.
Audio Player Design
Use any standard HTML5 player to embed generated speech. The interface remains lightweight, ensuring your blog’s design stays clean and uncluttered for readers.
Mobile Compatibility
Audio files are universally supported on iOS and Android devices. Readers can listen to your articles on the go without needing specific apps or plugins.
Accessibility Benefits
Audio enhances accessibility for visually impaired users or those who prefer listening. It also supports non-native speakers by providing an auditory reference for your text.
Support and Updates
Support is handled via email only, with no phone number or live chat. We prioritize clear, written responses that address specific integration questions for WordPress publishers. Documentation at /docs/ is updated whenever we release new voices or adjust rate limits, ensuring curl examples and SDK instructions match current API behavior to reduce integration errors.
Community feedback helps shape future improvements, though we do not maintain a public roadmap or guarantee specific feature release dates. Updates are driven by user needs and technical stability rather than marketing timelines.
Email Support
We offer email-only support, meaning there is no phone number or live chat option. This approach allows our team to provide detailed, written answers that can be referenced later during your WordPress integration process. You can reach us at the contact page for any questions regarding your API key or billing.
- No phone number
- No live chat
- Email only
Documentation Updates
Our documentation at /docs/ is updated promptly whenever we release new voices or adjust rate limits. WordPress users can rely on accurate curl examples and SDK instructions that match the current API behavior, reducing integration errors. The examples are specifically tailored for common WordPress environments.
Community Feedback
We value feedback from the publishing community to guide our development. While we do not publish a fixed feature roadmap, user insights often influence which improvements we prioritize next. Your suggestions help us keep the API relevant for bloggers and content creators.

Future Updates
ScribeSound continuously refines the underlying TTS engine to deliver smoother intonation and clearer pronunciation without requiring any changes to your WordPress configuration. Updates to the tts-1 and tts-1-hd models occur silently in the background, ensuring your audio remains high-quality as the technology evolves.
We do not have a public roadmap or promised release dates for new features. While we may introduce new voice presets from our licensed LibriTTS-R library, we do not plan to offer custom voice cloning. Any enhancements will be applied automatically to your existing API integration.
New Voices
We may add new voice presets from our licensed LibriTTS-R library in the future. However, there is no guaranteed timeline or specific schedule for these releases. We do not plan to offer custom voice cloning services.
Model Improvements
Updates to the tts-1 and tts-1-hd models will focus on natural intonation and pronunciation accuracy. These improvements happen silently in the background, requiring no action from your WordPress site.
Feature Roadmap
We do not maintain a public feature roadmap or promise specific release dates for new capabilities. Any future additions will be applied automatically to your existing API integration without requiring code changes.
Listen to the 8 voices
Each sample below was generated by this API from the same sentence. Streamline your publishing workflow by integrating reliable hosting solutions with powerful content management systems for seamless performance.
23 languages
Any voice speaks any of these languages.
