Frequently asked questions
Is this a natural reader online plugin?
No. We provide a cloud text-to-speech API, not a browser extension or WordPress plugin. You send text via HTTP requests and receive an audio file. While you can integrate it into your workflow, it is a standalone API service, not a direct plugin replacement for Natural Reader Online.
How does the API compare to natural reader online?
Unlike Natural Reader Online, we offer a transparent API with no monthly plans or seats. You pay only $0.01 per 1,000 characters. It supports 23 languages and 8 voice presets, returning audio in formats like MP3 or WAV. There is no free tier, only a $0.50 trial credit for Google sign-ins.
Which voices are best for blog narration?
For blog narration, we recommend Aria (warm, clear narrator) or Luna (soft, storytelling). For instructional content, Sage offers a calm tone, while Felix provides energetic promo-style audio. All voices are based on licensed recordings and can speak any of our 23 supported languages.
Can I use this for WordPress posts?
Yes. Since we do not offer a native WordPress plugin, you can use our API to generate audio files and embed them in your posts manually or via a custom plugin. The API accepts JSON bodies, making it easy to integrate into your existing content workflow.
How many 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. Vietnamese, Indonesian, Thai, and others are not supported.
Is there a free trial for natural reader online alternatives?
Yes. When you sign in with Google, you receive $0.50 of credit, valid for 7 days, which covers about 50,000 characters. Accounts created with email and password do not receive this trial credit. You can top up with USDT on the TRON network for ongoing use.
What happens if a request fails?
If synthesis fails, the charge is returned in full. You are not billed for failed requests. This ensures you only pay for successfully generated audio files. Failed requests are processed without cost to your balance.
Do I need technical skills to use the API?
Basic technical skills are helpful but not required. Our endpoint matches the OpenAI speech endpoint, so existing OpenAI SDKs work by changing the base URL. We provide ready curl examples on the /get-api-key/ page. However, you must handle the HTTP requests and audio file management.
How is the text split for long articles?
You must split text into parts of up to 4096 characters per request. Then, join the resulting audio files. The API does not automatically split long texts or join the audio files for you. This ensures you stay within the character limit for each synthesis job.
Are the voices realistic?
The voices are based on licensed recordings from LibriTTS-R and LibriVox public-domain audiobook readings. Every generated file carries an inaudible watermark marking it as synthetic speech. They are realistic but distinct from human speech due to the watermark and synthesis engine.
Is there a character limit per request?
Yes, each request supports up to 4096 characters in the input field. Spaces and punctuation count toward this limit. For longer articles, you need to split the text into multiple requests and combine the resulting audio files manually.
Can I change my API key?
Yes. You can issue a new API key at any time from your account page. When a new key is issued, the old one stops working immediately. You can have only one active key per account, ensuring secure access to your balance and usage data.
How long does generation take?
Generation takes roughly real time, about 25 characters of text per second of audio. Short phrases may take a few seconds. Requests are processed sequentially, so under load, a request may wait in a queue. Rate limits are 60 requests per minute per key.
Is my input text used for training?
No. Your input text is used only to produce the audio and is not used for training. Generated audio is returned in the response and not stored. We keep request metadata like time, characters, and status for billing purposes only.
First request
curl
curl https://api.play7359.com/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 Plugins to an API?
Plugins lock your audio generation into a specific WordPress ecosystem, creating dependency on updates and third-party reliability. An API decouples your content strategy from the platform, allowing you to generate speech independently of your CMS environment.
This separation ensures that your audio infrastructure remains stable even if you migrate themes or hosts, giving you direct ownership of the generation process.
No WordPress Dependency
By using an API, you remove the risk of plugin deprecation or conflicts breaking your audio playback. Your TTS service becomes a standalone utility, accessible from any frontend or backend system.
This approach future-proofs your blog’s audio features against changes in the WordPress ecosystem or specific plugin maintainers.
- Decoupled architecture
- Platform-agnostic delivery
Full Control Over Audio
Plugins often bundle fixed voice sets and formats. With the API, you choose exactly which voice, speed, and format (MP3, WAV, Opus, FLAC, or PCM) suits your specific episode or article.
You can programmatically adjust parameters like speed (0.25–4.0) or select specific voices like Aria for narration or Felix for promos without waiting for plugin updates.
Simpler Integration
The API follows a standard JSON structure compatible with the OpenAI SDK, making it easy to integrate via simple HTTP requests or custom scripts.
You send text and receive an audio file directly, bypassing the complexity of shortcodes, widget settings, or database bloat associated with traditional plugins.
Voice Selection for Content
Choosing the right voice ensures your content resonates with readers. Our API offers eight distinct presets, allowing you to match the tone of your blog posts precisely.
Narrator Voices for Long Reads
Aria and Luna provide warm, clear narration ideal for storytelling or in-depth articles. Sage offers a calm, instructional tone suitable for tutorials and guides.
- Aria: Warm, clear narrator
- Luna: Soft, storytelling
- Sage: Calm, instructional
Energetic Voices for Promos
Felix brings an energetic, promo-friendly energy to short announcements or sponsored content. Nova adds a bright, upbeat quality perfect for engaging social media snippets.
- Felix: Energetic, promo
- Nova: Bright, upbeat
Neutral Voices for News
Atlas delivers a neutral, news-style delivery for straightforward updates. Orion provides a deep, documentary voice for more serious or historical content.
Each voice is based on licensed recordings from LibriTTS-R (CC BY 4.0) and LibriVox public-domain audiobook readings, ensuring consistent quality across all generated audio files.
- Atlas: Neutral, news
- Orion: Deep, documentary
Language Support for Global Blogs
Global reach requires multilingual support without hiring native speakers for every market. Our API handles 23 languages natively, including Arabic, Chinese, Japanese, and Hindi, allowing bloggers to localize content efficiently. Each voice can speak any supported language, ensuring consistent quality across diverse regions.
23 Supported Languages
We support 23 languages, covering major markets from English and Spanish to Turkish and Swahili. If a language is not in the list, such as Vietnamese or Thai, the API cannot process it. This limited but curated set ensures reliable audio quality for each supported language.
- Arabic, Chinese, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hindi, Italian, Japanese, Korean, Malay, Norwegian, Polish, Portuguese, Russian, Spanish, Swahili, Swedish, Turkish
Auto-Detection vs Explicit
The API guesses language from the script if you do not specify one. Latin script defaults to English. For non-English Latin text, always set the language field to avoid mispronunciation. Explicit setting guarantees the correct voice model activates for your content.
Non-Latin Script Handling
Scripts like Arabic, Hebrew, Hindi, and Japanese are fully supported. The engine processes these characters directly without requiring external conversion. This ensures accurate processing for non-Latin languages, maintaining readability and engagement for your global audience.
Audio Formats for Web Use
Choosing the right audio format ensures your blog’s content loads quickly without sacrificing clarity. The API supports multiple output types, allowing you to balance compatibility, quality, and bandwidth efficiency based on your specific needs.
MP3 for Compatibility
MP3 is the standard for web audio, offering broad support across all browsers and devices. It provides a good balance between file size and sound quality, making it ideal for most blog posts and general listening.
WAV for Quality
WAV files deliver uncompressed, high-fidelity audio. Use this format when preserving the exact nuances of the voice is critical, such as for premium content or archival purposes, though files will be larger.
Opus for Bandwidth
Opus offers superior compression for smaller file sizes while maintaining excellent audio quality. It is ideal for reducing bandwidth costs and speeding up load times on mobile networks or slower connections.
Pricing Transparency
BlogTTS Reviews tests the numbers so your budget stays predictable. Our API charges strictly by input length, meaning you pay only for what you generate. There are no hidden fees for high-quality models or extra voices.
Pay Per Character
The rate is $10 per 1 million characters, or $0.01 per 1,000 characters. Spaces and punctuation count toward this total. Failed requests are free, so you never pay for errors.
No Monthly Fees
We do not offer monthly plans, seats, or minimum spends. Your balance does not expire, and you can top up only when needed. This model fits irregular publishing schedules perfectly.
Trial Credit Available
New accounts signing in with Google receive $0.50 in credit, covering about 50,000 characters for 7 days. Email-based accounts start without this trial credit. You can switch to USDT (TRC-20) top-ups anytime.

Performance for Content Creators
BlogTTS Reviews tests generation speed to ensure your blog updates load smoothly. Synthesis typically runs at roughly real-time speed, processing about 25 characters of text per second for longer articles. Short phrases may take a few seconds, but the API handles standard blog post lengths efficiently without delaying your publishing workflow.
Real-Time Generation Speed
For standard content, generation keeps pace with reading speed. This ensures that when you trigger synthesis, the audio file is ready quickly enough to embed directly into your posts without significant wait times for your readers.
Queue Handling During Load
Requests are processed sequentially. Under heavy load, a request may wait in a queue before synthesis begins. This linear processing ensures consistent quality but means peak usage times might introduce slight delays compared to burst-mode services.
Splitting Long Articles
The API limits input to 4,096 characters per request. For longer blog posts, you must split the text into parts, generate each audio segment, and join the files. This approach keeps individual requests lightweight and manageable for your backend.
Data Privacy for Creators
For content creators, knowing how input data is handled is critical. Our API processes your text exclusively to generate the audio file. We do not use your blog posts or article content to train our models, ensuring your unique voice and content strategy remain proprietary.
No Training on Input
Your submitted text is used solely for synthesis. Unlike some platforms that build training datasets from user content, we keep your words strictly within the generation pipeline. This means your articles are not repurposed to improve our base engine without your explicit consent.
No Audio Storage
The generated audio file is returned directly in the response and is not stored on our servers after delivery. This minimizes data retention risks and ensures that your final audio output does not linger in our cloud infrastructure longer than necessary.
Metadata Retention
We retain request metadata, including timestamps, character counts, and status codes, solely for accurate billing and usage tracking. This data is kept only to verify charges and ensure rate limit compliance, providing a transparent audit trail for your accounting needs.
Setup for WordPress Users
Integrating BlogTTS into your WordPress workflow begins with securing your API key from the /get-api-key/ dashboard. This key authenticates your requests to the API base at https://api.play7359.com/v1. Managing keys is straightforward: you can issue a new key at any time, which instantly invalidates the previous one, ensuring secure access as your blog scales.
For backend integration, use the official OpenAI SDK or plain HTTP. Set the base_url to our API endpoint and pass your key in the Authorization header. This standard approach allows you to generate audio files from post content without relying on heavy WordPress plugins or third-party widgets.
API Key Management
Retrieve your unique key from the dashboard. It starts with tts-. You can rotate this key instantly if needed, with the old key stopping immediately.
Bullets: [
Backend Integration
Use standard HTTP POST requests to https://api.play7359.com/v1/audio/speech. Pass your text, voice selection, and desired format (mp3, wav, etc.) in the JSON body.
Bullets: [
Custom Plugin Options
Since we do not provide an official WordPress plugin, you can build a custom solution. Use the API to convert blog posts to audio on the fly or pre-generate files during publishing.
Bullets: [
Comparison with Other Services
BlogTTS Reviews tests the major players so you don't have to guess. We compare our API against established services to highlight where our transparent pricing and OpenAI-compatible SDK fit your WordPress workflow.
Unlike plugin-heavy solutions, we offer a straightforward API that integrates directly with your backend, giving you full control over audio generation without platform lock-in.
OpenAI SDK Compatibility
Our API uses the exact same request shape as the OpenAI speech endpoint. You can switch by changing the base_url to https://api.play7359.com/v1 and using your BlogTTS key. This means existing OpenAI SDKs work out of the box without custom code.
This compatibility simplifies migration for developers already familiar with the OpenAI ecosystem, ensuring a smooth transition from expensive per-token models to our character-based pricing.
- Same request shape as OpenAI
- Works with official OpenAI SDKs
- No custom library needed
AWS Polly Alternatives
While AWS Polly offers a wide range of neural voices, it requires complex infrastructure setup and billing based on request volume. BlogTTS provides a simpler, unified API with consistent pricing across all voices and languages.
Our service eliminates the need for managing multiple AWS services, offering a direct endpoint for text-to-speech that is easier to integrate into WordPress plugins or custom themes.
- Simpler billing model
- Unified API endpoint
- No infrastructure management
ElevenLabs Differences
ElevenLabs is known for high-quality cloning and emotion tags, which we do not offer. Our voices are based on licensed recordings from LibriTTS and LibriVox, providing consistent, clear narration without the cost of custom voice design.
We focus on transparency and simplicity: $0.01 per 1,000 characters, no monthly plans, and a straightforward API. If you need custom voice cloning or emotion tags, ElevenLabs may be a better fit; otherwise, our API offers better value for blogs.
- No voice cloning
- Licensed recordings
- Transparent pricing
Listen to the 8 voices
Each sample below was generated by this API from the same sentence. The limit resets every minute, so you can plan your generation bursts around peak publishing times.
23 languages
Any voice speaks any of these languages.
Sources and further reading
- Wikipedia
- Python documentation
- MDN: Web Speech API
- LibriTTS-R corpus (OpenSLR 141)
- IETF RFC 7845: Ogg Opus
- openai-python on GitHub
- Node.js documentation
- LibriTTS-R paper (arXiv 2305.18802)
- FFmpeg documentation
- LibriVox public-domain audiobooks
- OpenAI API reference: create speech
- W3C WAI: making audio and video accessible
