Frequently asked questions
Which TTS API is best for indie developers?
Q: Which TTS API is suitable for indie developers? A: WordCaster is designed for indie developers and no-code builders. It offers a simple pay-as-you-go model at $10 per 1 million characters. The API uses OpenAI-compatible endpoints, allowing you to use existing SDKs by changing the base URL. There are no monthly plans, seats, or minimum spend, keeping infrastructure costs predictable and low.
How does this API compare to OpenAI?
WordCaster is not affiliated with OpenAI. It uses the same request shape as the OpenAI speech endpoint, so official OpenAI SDKs work by changing the base URL to https://api.playtoto155.com/v1. The engine and pricing are distinct. You use your own API key for authentication, and the service operates independently without OpenAI branding or infrastructure.
How does this API compare to ElevenLabs?
Unlike ElevenLabs, WordCaster does not offer custom voice cloning, emotion tags, or a dedicated mobile SDK. It provides eight fixed voice presets based on licensed recordings. Pricing is transparent at $10 per million characters with USDT payments only. It focuses on simplicity and reliability for developers who need standard TTS without complex voice design features.
What is the best voice for narration?
For narration, aria is a warm, clear female narrator. Luna is a soft female voice ideal for storytelling. For male narration, atlas provides a neutral, news-style delivery, while orion offers a deep, documentary tone. All voices support 23 languages. Choose based on the desired emotional tone of your content.
Is USDT payment reliable?
Top-ups use USDT on the TRON network (TRC-20) only. Minimum top-up is $5. Credits are added automatically within minutes after the transfer. There are no subscriptions or invoices. Balance does not expire. Failed requests are free, ensuring you only pay for successful synthesis. This method avoids credit card fees and offers instant funding.
Can I use this API for commercial projects?
Yes. Generated audio files carry an inaudible watermark marking them as synthetic speech. Input text is used only to produce audio and is not used for training. There are no restrictions on commercial use. You pay per character used, with no minimum spend or seat limits, making it suitable for any project scale.
What is the best format for web audio?
MP3 is the most common format for web audio due to its balance of quality and file size. You can also choose WAV, OPUS, FLAC, or PCM. OPUS offers efficient compression for streaming-like experiences. Select the format that best fits your player capabilities and bandwidth constraints. All formats are returned directly in the API response.
How do I handle large texts?
Each request supports up to 4096 characters. For longer texts, split the input into parts of this size. Generate audio for each part separately, then join the resulting audio files. This ensures reliable synthesis. Typical speed is roughly real-time, so long texts will take time proportional to their length.
Is the API suitable for mobile apps?
Yes, though there is no official mobile SDK. You can use the standard HTTP endpoint or OpenAI SDKs in your app. Be aware of rate limits: 60 requests per minute per key. Since requests are processed sequentially, high concurrency may cause queuing delays. Ensure your app handles network latency and audio caching appropriately.
What are the rate limits?
The limit is 60 requests per minute per API key. New accounts start with 10 requests per minute until the first top-up. Requests are processed one after another, so under load, a request may wait in a queue. Exceeding the limit will result in errors until the window resets.
Does the API support multiple languages?
Yes, it supports 23 languages including English, Spanish, French, German, Japanese, and Chinese. Any voice can speak any supported language. If the language is not set, it is guessed from the script. For non-English Latin text, explicitly set the language parameter to ensure accurate pronunciation.
Can I generate audio in bulk?
Yes, you can generate audio in bulk by sending multiple requests. Each request handles up to 4096 characters. Since requests are processed sequentially, large batches may take time. Failed requests are free, so you only pay for successful generations. Monitor your rate limit to avoid queuing delays during high-volume operations.
How do I track my usage?
Log in to your account on the /get-api-key/ page. The dashboard shows your balance, characters left, and usage history. Request metadata, including time, characters, and status, is kept for billing. You can also view your API key and generate a new one if needed. All data is transparent and accessible.
What happens if I exceed my limit?
If you exceed the 60 requests per minute limit, subsequent requests will be queued or rejected until the window resets. New accounts start with 10 requests per minute. Ensure your application handles rate limit errors gracefully. Failed synthesis requests are free, but exceeded limits do not incur charges, only delays or errors.
Why indie devs need a TTS API
Indie developers often face the challenge of integrating high-quality audio without hiring a dedicated audio engineer or managing complex infrastructure. A TTS API solves this by offloading the heavy lifting of audio synthesis to a reliable cloud service, allowing you to focus on your core product features rather than backend audio processing.
Scalability needs
As your user base grows, audio generation demands can spike unexpectedly. A cloud API handles this load, but requests are processed sequentially and may queue under load.
- Automatic handling of traffic spikes
- No server maintenance required
Cost efficiency
Unlike fixed monthly subscriptions that may include unused capacity, a pay-as-you-go model aligns costs directly with usage. You only pay for the characters you generate, making it ideal for projects with variable audio requirements.
Ease of integration
With OpenAI-compatible endpoints, you can integrate WordCaster using familiar tools and SDKs. A simple POST request converts text to audio, reducing the time from concept to a working prototype.
Key features to look for
When evaluating a Text-to-Speech API, compatibility and flexibility determine how quickly you can integrate audio into your workflow. An OpenAI-compatible endpoint allows you to reuse existing code or SDKs with minimal changes, while a diverse voice library and broad language support ensure your content reaches the right audience without needing multiple providers.
WordCaster offers a straightforward approach: a single endpoint compatible with standard tools, eight distinct voice presets, and support for 23 languages. This combination reduces integration friction and keeps your project moving without complex infrastructure.
OpenAI compatibility ['The API uses the same request structure as the OpenAI speech endpoint. You can use official OpenAI SDKs by changing base_url to https://api.playtoto155.com/v1. This allows indie developers to leverage familiar libraries without writing custom HTTP clients.', 'Authentication is handled via a Bearer token in the Authorization header. The endpoint POST /v1/audio/speech accepts JSON bodies with fields like model, input, voice, and response_format.', {'h3': 'Voice variety', 'paras': ['The service provides eight preset voices, including female options like Aria and Nova, and male options like Felix and Milo. Each voice has a distinct character, from warm narration to energetic promo styles.', 'All voices are based on licensed recordings from LibriTTS-R and LibriVox. Every generated audio file includes an inaudible watermark to mark it as synthetic speech.', 'There is no custom voice cloning or emotion tagging. You select from the existing presets based on the tone you need.']}, {'h3': 'Language support', 'paras': ['The API supports 23 languages, including English, Spanish, German, Japanese, and Hindi. Any voice can speak any of these languages, offering flexibility in content creation.', 'If the language field is not set, the system guesses the language from the script. Latin text defaults to English, so you should explicitly set the language for other Latin-script languages.', 'Vietnamese, Indonesian, Thai, Ukrainian, Romanian, Czech, and Bengali are not supported.']}] A clean, modern illustration showing a laptop screen with code snippets and audio waveforms, symbolizing seamless integration for indie developers building multilingual apps
Pricing comparison
WordCaster eliminates monthly subscriptions and seat fees, offering a straightforward pay-as-you-go model. Indie developers pay only for what they use, with no minimum spend or annual commitments. This structure aligns costs directly with project growth, making it ideal for variable traffic or prototype phases.
The pricing is transparent: $10 per 1 million characters, or $0.01 per 1,000 characters. Spaces and punctuation count toward the total. Failed requests are free, ensuring you never pay for broken output. A $0.50 free trial (7 days) helps you test the API before committing.
Pay-per-use vs subscriptions
WordCaster uses a pure pay-per-use model. There are no monthly plans, no seats, and no minimum spend. You top up your balance via USDT (TRC-20) and spend it as needed. This avoids the waste of unused credits common in subscription tiers.
- No monthly plans
- No seats or minimum spend
- Balance does not expire
Character counting methods
Every character in your input text counts, including spaces and punctuation. The API calculates usage per request, so splitting long texts into 4,096-character chunks may affect efficiency slightly due to overhead, but ensures reliable processing.
- Spaces and punctuation count
- $0.01 per 1,000 characters
- Failed requests are free
Hidden fees
There are no hidden fees. No VAT invoices, no currency conversion charges, and no extra costs for different models (tts-1 and tts-1-hd share the same engine and price). The only cost is the character usage itself.
- No VAT invoices
- No currency conversion fees
- Same price for all models
Voice quality and options
WordCaster provides eight distinct voice presets, each tailored for specific use cases. You can choose warm narrators like Aria, energetic promo voices like Felix, or neutral news readers like Atlas. Every voice supports all 23 listed languages, allowing consistent audio quality across diverse linguistic projects without needing multiple engine subscriptions.
The choice between standard and HD models is straightforward. Both "tts-1" and "tts-1-hd" use the same engine and incur identical pricing. You pay $0.01 per 1,000 characters regardless of which model you select, making the decision purely about your preference for audio fidelity versus processing time.
Preset voices
Eight voices cover most narrative needs. Options range from soft storytelling with Luna to deep documentary tones with Orion. Each voice is based on licensed recordings from LibriVox, ensuring clear, professional audio without licensing complexity.
- Aria (warm narrator)
- Nova (bright upbeat)
- Luna (soft storytelling)
- Sage (calm instructional)
- Felix (energetic promo)
- Milo (friendly conversational)
- Atlas (neutral news)
- Orion (deep documentary)
HD vs standard
Both models share the same engine and price point. There is no cost difference between "tts-1" and "tts-1-hd". Select the HD model if you prefer higher fidelity, but know that processing time and billing remain identical.
Emotion and tone
The API does not support emotion tags or custom tone adjustments. Voice character is baked into the preset selection. You control the mood by choosing the appropriate voice preset rather than adjusting parameters during generation.
Integration ease
Integration simplicity matters for indie developers who prefer no-code or low-code workflows. WordCaster uses an OpenAI-compatible endpoint shape, meaning you can use the official OpenAI SDKs by simply changing the base_url. This eliminates the need to learn a proprietary protocol or manage custom authentication headers.
The API also accepts standard HTTP requests, making it easy to test with tools like cURL or Postman before writing code. This flexibility ensures that both Python developers and JavaScript no-code builders can integrate speech generation quickly without complex infrastructure setup.
SDK availability
We do not provide a proprietary SDK. Instead, we rely on the widely adopted OpenAI Python and JavaScript SDKs. By setting base_url to https://api.playtoto155.com/v1, you can use the same code structure you already know. This approach saves development time and reduces the learning curve for teams already familiar with OpenAI’s ecosystem.
There is no official WordCaster SDK, nor are there mobile-specific or WordPress plugins. This keeps the integration lightweight and agnostic to your stack.
- Use official OpenAI SDKs
- Change
base_urlonly - No proprietary SDK required
cURL simplicity
Testing is straightforward with a single cURL command. You send a POST request to /v1/audio/speech with a JSON body containing model, input, and voice. The API returns the audio file directly, allowing you to verify output format and speed before committing to a full integration.
This method is ideal for quick prototypes or serverless functions where importing a full SDK might be overkill. You can paste your Bearer token and text directly into the terminal to see immediate results.
Documentation quality
Our documentation provides clear examples for every supported response_format and voice preset. We list the exact request fields and authentication headers required for both standard and HD models.
The docs also clarify character limits and language guessing behavior, ensuring you avoid common pitfalls like sending non-Latin text without setting the language parameter. This transparency helps developers debug issues faster.
Limitations to consider
While the API handles complex synthesis tasks efficiently, understanding its boundaries helps prevent integration surprises. The service prioritizes stability and simplicity over real-time interactivity, meaning you must design your workflows around batch processing rather than instant audio feedback.
No streaming
The API returns complete audio files rather than streaming partial chunks. This means you must wait for the full synthesis to finish before playing or storing the audio, which is ideal for static content but less suitable for live conversational interfaces requiring instant response.
No SSML
Unlike some competitors, WordCaster does not support SSML tags for fine-grained control over pauses, emphasis, or pronunciation. Voice control is limited to selecting from the eight preset voices and adjusting the overall speed between 0.25x and 4.0x.
Character limits
Each request accepts a maximum of 4096 characters. For longer texts, your application must split the input into chunks, send multiple requests, and join the resulting audio files. This requires basic logic in your backend to manage the segmentation.
Data privacy and rights
For indie developers building audio features, understanding data handling is critical. WordCaster ensures your input text is used solely for the immediate synthesis of the requested audio file, without being stored or repurposed for model training. This keeps your content private and reduces compliance overhead for small teams.
The generated audio is returned directly in the response and is not persisted on our servers after delivery. You retain full ownership of the resulting sound files, which can be embedded in your apps or websites without recurring licensing fees tied to usage volume.
Training data usage
Input text is processed only to produce the specific audio file requested. It is not added to any training dataset or used to improve the underlying voice models. This ensures that your unique content remains confidential and is not leveraged by the provider for commercial model development.
Audio ownership
You own the generated audio files immediately upon successful synthesis. Since the voices are based on licensed and public-domain recordings, you can integrate these audio clips into your projects without worrying about complex royalty structures.
Data retention
While the audio itself is not stored, request metadata—including timestamp, character count, and status—is retained for billing and debugging purposes. This minimal data keeps your account accurate and helps resolve any discrepancies in usage charges without keeping your actual text content on file.

Support and reliability
WordCaster provides support exclusively via email. There is no phone number or live chat available, so responses depend on email volume. This approach keeps overhead low, allowing funds to go directly into the API infrastructure rather than maintaining a large support team.
Email support
All inquiries are handled through email. You can reach the team at the contact page for any technical or billing questions. Since there is no live chat, expect a response within a reasonable timeframe, but no guaranteed SLA.
- Email-only support channel
- No phone or live chat
- No guaranteed response time
Uptime expectations
We do not offer a formal Service Level Agreement (SLA) or uptime guarantee. The API is reliable for typical use cases, but there is no enterprise contract to back it up. During high load, requests may queue, but the service remains functional.
Rate limits
Each API key is limited to 60 requests per minute. Before your first top-up, this limit is stricter at 10 requests per minute. This ensures fair usage and prevents any single account from monopolizing the processing queue during peak times.
- 60 requests/minute per key
- 10 requests/minute before top-up
- Queued processing under load
Technical requirements
Sending text to the API requires a standard HTTPS connection. The endpoint is POST https://api.playtoto155.com/v1/audio/speech. You need internet access to submit requests and receive the audio file. Short phrases take a few seconds; longer texts process in roughly real time.
Network requirements
Use a standard HTTPS POST request. The API handles the conversion, so your client just sends the JSON body and receives the audio file.
Authentication methods
Include your API key in the Authorization header. Use the format: Authorization: Bearer tts-... . Each account has one active key. If you issue a new key, the old one stops immediately.
Error handling
Check the response status code. Failed requests are free, so you can retry without worry. If synthesis fails, the charge is returned in full. Always handle network timeouts gracefully, as requests are processed sequentially.
Use case examples
Converting static text into spoken audio helps indie developers add accessibility and engagement to their projects without hiring voice actors. By integrating a simple API, you can generate natural-sounding audio files on demand, keeping your infrastructure lightweight and costs predictable.
E-learning platforms
Use the API to convert lesson text into audio for students. With 23 languages and 8 distinct voice presets, you can create diverse learning materials. The pay-as-you-go model ensures you only pay for the content you actually generate, making it ideal for course platforms with fluctuating demand.
- Support for 23 languages including English, Spanish, and Japanese
- 8 voice presets for varied narrator styles
- Pay per 1,000 characters, no monthly minimums
News aggregators
Turn article text into audio summaries for users who prefer listening. The API handles up to 4,000 characters per request, allowing you to split longer articles seamlessly. Voices like Atlas provide a neutral tone suitable for news, while Orion offers a deeper style for documentaries.
- Split long texts into 4,096-character chunks
- Neutral voices like Atlas for news
- Audio generation for updates
Mobile apps
Enhance apps with voice features by sending text to the API and receiving audio files. The OpenAI-compatible endpoint simplifies integration using existing SDKs. With no need for complex infrastructure, you can add voice features to iOS or Android apps with minimal code changes.
- OpenAI-compatible endpoints for easy SDK use
- Support for mp3, wav, opus, flac, pcm
- No extra infrastructure required
Getting started
Getting started with WordCaster is designed for speed, allowing indie developers to move from sign-up to generated audio in minutes. The process requires minimal configuration, focusing on simplicity so you can integrate text-to-speech into your no-code workflows or custom applications without wrestling with complex infrastructure.
You begin by creating an account, which provides immediate access to your API key and a small trial balance. This setup ensures you can validate the integration step before committing to larger usage, keeping your project momentum intact from day one.
Account creation
Visit the /get-api-key/ page to create your account using either Google sign-in or a standard email and password. Google sign-up includes a $0.50 trial credit valid for seven days, giving you approximately 50,000 characters to test the service immediately. Accounts created with email start without this trial credit but are ready for top-up at any time.
API key setup
Once registered, your dashboard displays your unique API key, current balance, and usage statistics. This key is used for authentication via the Authorization: Bearer header in your requests. You can issue a new key at any time, which instantly invalidates the previous one, ensuring secure access control for your indie projects.
- One active key per account
- Instant invalidation of old keys
- Visible balance and character count
First test
Use the provided cURL example on your dashboard to send your first request. Point your base_url to https://api.playtoto155.com/v1 and use the tts-1 model. Send a short text input, and you will receive an audio file in your chosen format, confirming the integration is working correctly before you scale up.
- Use the ready cURL example
- Set base_url to api.playtoto155.com/v1
- Receive audio file in response
Final recommendations
Selecting a TTS API depends on your specific volume and workflow needs. WordCaster offers distinct advantages for different stages of development, from initial prototyping to production scaling.
Best for testing
Indie developers can start with the $0.50 Google sign-up trial, providing approximately 50,000 characters for seven days. This low barrier allows quick validation of voice fit without financial commitment.
Best for scaling
With transparent pay-as-you-go pricing at $0.01 per 1,000 characters and no monthly minimums, you only pay for what you use. The API handles character splitting automatically, ensuring consistent audio output for large texts.
Best for ease of use
The OpenAI-compatible endpoint structure means existing SDKs work by simply changing the base URL. With ready-to-use cURL examples and clear documentation, integration is straightforward for no-code builders and developers alike.
Listen to the 8 voices
Each sample below was generated by this API from the same sentence. Each voice is based on licensed recordings from LibriVox, ensuring clear, professional audio without licensing complexity.
23 languages
Any voice speaks any of these languages.
