Cloud Text-to-Speech API for Audiobook Narration

By ReadCast editorial team · Updated 2026-11-19

ReadCast API delivers reliable, character-based text-to-speech generation tailored for independent authors and audiobook narrators. This page outlines how our cloud API simplifies the production pipeline from manuscript to audio file, offering consistent voice quality without enterprise contracts. You will find specific details on our 8 distinct narration styles, support for 23 languages, and transparent pricing designed for content creators who need predictable costs.

We provide an endpoint compatible with the OpenAI speech format that integrates into your existing workflow by changing the base URL. Explore our documentation for technical specifications, voice options, and pricing models. Whether you are producing long-form audiobooks or short-form content, our solution offers rapid prototyping and standard protocols to ensure your audio files are generated efficiently and accurately.

Cloud Text-to-Speech API for Audiobook Narration

Frequently asked questions

What does 'text laut vorlesen lassen' mean in the context of audiobooks?

It means having text read aloud. Our API converts your manuscript text into audio files via a simple POST request. You send the text, and we return the synthesized speech. This allows authors to convert written chapters into listenable audio formats efficiently without hiring human narrators for every project.

How many characters can I process in a single API request?

You can process up to 4096 characters per single API request. For longer manuscripts, you split the text into parts of this size and join the resulting audio files. This limit ensures consistent processing speed and allows you to manage generation loads effectively during your audiobook production workflow.

Are the voices suitable for full-length audiobooks?

Yes, our eight preset voices are designed for consistent narration. Voices like Aria and Luna offer clear, storytelling tones suitable for long-form content. Since the API returns standard audio files, you can assemble them into complete audiobooks. The voices are based on licensed recordings, ensuring professional quality for your projects.

Do I need to credit the original voice actors?

The voices are based on recordings from LibriTTS-R (CC BY 4.0) and LibriVox public-domain readings. While the source material is public domain, we do not mandate specific attribution for API usage. You receive the audio file directly, and no additional licensing steps or credits are required for commercial or personal use.

Can I generate audio in multiple languages with the same voice?

Yes, every voice can speak any of our 23 supported languages. You can use the same voice preset for English, German, or Japanese text by specifying the language code. If omitted, the system guesses the language, but setting it explicitly ensures accurate pronunciation across different linguistic contexts for your multilingual audiobooks.

What happens if a synthesis 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. You can retry the request or adjust parameters like speed or voice without financial penalty, maintaining predictable costs for your audiobook production pipeline.

Is there a limit to how long an audiobook can be?

There is no hard limit on total audiobook length. You can process unlimited text by splitting it into chunks of 4096 characters per request. Simply join the resulting audio files. The only constraint is the character limit per individual API call, allowing you to generate feature-length audiobooks of any duration.

Do you support SSML for fine-tuning pronunciation?

No, we do not support SSML. Our API uses simple text input with optional language codes. Pronunciation is handled by the voice model automatically. If you need specific phrasing, you can adjust the input text directly. We do not offer phoneme dictionaries or custom pronunciation lexicons for fine-tuning.

How long does it take to generate an hour of audio?

Generation takes roughly real time, about 25 characters per second of audio. For an hour of audio, expect approximately one hour of processing time, plus queue time under load. Requests are processed sequentially, so high volume may increase total generation time. Short phrases take a few seconds each.

Can I use the generated audio for commercial projects?

Yes, you can use the generated audio for commercial projects. The voices are based on licensed recordings, and you receive the audio files directly. You own the generated audio files, making them suitable for self-published audiobooks, podcasts, or commercial narration. You own the generated audio files, making them suitable for self-published audiobooks, podcasts, or commercial narration.

What audio formats are available for download?

You can choose from mp3, wav, opus, flac, and pcm formats. Select the desired format in your API request body. These standard formats ensure compatibility with most audiobook platforms and editing software. The generated files include an inaudible watermark to mark them as synthetic speech, as per our product specifications.

Is there a free trial available for new users?

Yes, signing in with Google provides $0.50 of credit, valid for 7 days. This covers about 50,000 characters. Accounts created with email and password start without trial credit. You can top up with USDT on the TRON network for ongoing usage. The trial allows you to test voice quality and integration.

How are characters counted for pricing?

Pricing is $0.01 per 1,000 characters. Spaces and punctuation count as characters. You are charged based on the total character count in your input text. Failed requests are free. This predictable, character-based model allows you to estimate costs accurately for your manuscript length before generating the audio files.

Do I have to use the OpenAI SDK to integrate?

No, you can use the official OpenAI SDK by changing the base URL to https://api.link02.info/v1. Alternatively, you can use plain HTTP requests. The request shape matches the OpenAI speech endpoint, making integration straightforward. You do not need our proprietary SDK, allowing flexibility in your development stack.

First request

curl

curl https://api.link02.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.mp3

From Manuscript to Audio

Sound wave illustration for: From Manuscript to Audio

ReadCast API transforms written manuscripts into professional audio files through a straightforward cloud workflow. By sending your text to the API endpoint, you receive synthesized speech files ready for distribution, eliminating the need for complex recording studios or hardware setups.

This solution is designed for independent authors who need consistent quality without enterprise contracts. The system handles the technical details, allowing you to focus on the story while ensuring every chapter is produced with uniform narration standards.

Automated Narration

Automated Narration

The API accepts text input and returns audio files directly. You can process entire chapters by splitting longer texts into 4096-character segments, which the system synthesizes and joins seamlessly.

This automation simplifies the workflow from manuscript to audio, enabling self-published works to be produced without complex recording setups.

  • Send text, receive audio file
  • Automatic segment joining for long texts
  • No manual recording required

Consistent Voice Quality

Each voice preset maintains a uniform tone across your entire project. Whether using Aria for warm narration or Atlas for neutral news-style reading, the engine ensures consistent character voice.

This consistency is critical for audiobook listeners, preventing jarring shifts in tone between chapters or sections.

  • Uniform voice across chapters
  • 8 distinct preset voices
  • No variation in delivery style within a single voice preset

Rapid Prototyping

With a free trial credit of $0.50, you can generate sample audio quickly to test voice suitability for your book. This allows you to evaluate pacing and tone before committing to full-length production.

The straightforward API structure means you can prototype your audio pipeline in minutes using standard HTTP requests or OpenAI-compatible SDKs.

  • Quick trial credit usage
  • Test voices before full production
  • Simple integration setup

8 Distinct Narration Styles

Sound wave illustration for: 8 Distinct Narration Styles

ReadCast API offers eight distinct voice presets, each calibrated for specific narrative tones. These voices are based on licensed recordings from LibriTTS-R and LibriVox, providing a consistent baseline for audiobook production.

Warm Narrator (Aria)

Aria delivers a clear, warm tone ideal for standard fiction and memoirs. Her narration style ensures readability and emotional engagement, making her suitable for long-form storytelling where consistency matters most.

  • Clear, warm narration tone
  • Ideal for standard fiction and memoirs
  • Consistent character voice

Upbeat Promo (Nova)

Nova brings a bright, energetic quality perfect for promotional clips or younger audiences. Her upbeat cadence keeps listeners engaged during shorter segments or marketing materials derived from your manuscript.

  • Bright, energetic delivery
  • Optimized for promotional content
  • High engagement cadence

Soft Storytelling (Luna)

Luna offers a soft, soothing voice well-suited for bedtime stories or intimate narratives. Her gentle pacing reduces listener fatigue during extended listening sessions, supporting a calm production workflow.

  • Soft, soothing delivery
  • Reduced listener fatigue
  • Ideal for intimate narratives

Global Reach with 23 Languages

Sound wave illustration for: Global Reach with 23 Languages

ReadCast API supports 23 languages, enabling independent authors to reach global audiences without hiring multiple voice actors. The service covers major markets including Arabic, Chinese, English, French, German, Hindi, Japanese, Korean, Portuguese, Russian, Spanish, and Swahili, ensuring consistent quality across diverse linguistic groups.

Multi-language Support

Our API handles 23 languages including Chinese, Japanese, Korean, Hindi, and Swahili. Each voice preset can speak any supported language, allowing you to maintain a consistent narrative tone across your entire catalog regardless of the target market.

  • Full coverage of major global languages
  • Consistent voice quality across all 23 languages
  • No separate pricing per language

Automatic Language Detection

The system automatically detects the language from the input script, defaulting to English for Latin text. For non-English texts using Latin characters, you can explicitly set the language parameter to ensure accurate pronunciation and intonation.

Cross-lingual Clarity

Voices are designed for clarity and natural flow. Supported languages include Arabic, Danish, Dutch, Finnish, Greek, Hebrew, Italian, Malay, Norwegian, Norwegian, Polish, Portuguese, Russian, Spanish, Swedish, and Turkish. Languages like Vietnamese, Indonesian, Thai, Ukrainian, and Romanian are not yet supported.

Pricing for Independent Creators

Sound wave illustration for: Pricing for Independent Creators

ReadCast API charges $10 per 1 million characters, equating to $0.01 per 1,000 characters. This character-based model includes spaces and punctuation, ensuring predictable costs for long manuscripts without hidden volume tiers or seat limits.

Pay Per Character

Usage is calculated strictly on character count, not request count. Failed requests incur no charge, and credits are returned in full if synthesis fails. This structure aligns costs directly with content length, ideal for variable-length audiobook projects.

  • $10 per 1 million characters
  • $0.01 per 1,000 characters
  • Spaces and punctuation count
  • Failed requests are free

No Monthly Fees

There are no monthly plans, subscriptions, or minimum spend requirements. Accounts do not expire, and balance does not expire. You only pay for the audio you generate, making it suitable for sporadic publishing schedules.

Transparent Costs

Top-ups are accepted via USDT (TRC-20) on the TRON network, with a minimum of $5. Credits are credited automatically within minutes. No invoices or VAT are added to your base rate.

Technical Simplicity

Sound wave illustration for: Technical Simplicity

ReadCast API aligns with the standard OpenAI speech endpoint structure, allowing you to reuse existing libraries like the official OpenAI SDK by simply adjusting the base URL to https://api.link02.info/v1. This compatibility allows you to reuse existing libraries like the official OpenAI SDK by adjusting the base URL.

OpenAI Compatible SDK

By mimicking the standard request shape, developers can switch providers without rewriting core logic. Send a POST request with your API key in the Authorization header, and receive audio in return.

Multiple Audio Formats

Select output formats including mp3, wav, opus, flac, or pcm directly in the request body. This flexibility ensures compatibility with various audiobook distribution platforms and editing software without requiring post-processing conversions.

Easy Integration

Integration requires only standard JSON payloads with fields like model, input, voice, and response_format. The API handles character limits up to 4096 per request, simplifying the workflow for manuscript splitting and audio joining.

Technical Simplicity

Reliability for Production

Sound wave illustration for: Reliability for Production

ReadCast API delivers consistent audio quality by using a single, stable engine for both the "tts-1" and "tts-1-hd" models. This uniformity ensures that your narration maintains a steady tone and clarity, regardless of request volume or time of day, which is critical for maintaining listener engagement across long-form audiobooks.

Requests are processed sequentially, with typical generation speeds of roughly 25 characters per second of audio. While short phrases may take a few seconds, longer texts are split into 4,096-character chunks and joined seamlessly. Under heavy load, requests may queue briefly, but the engine remains stable without unexpected failures.

Consistent Engine

Both "tts-1" and "tts-1-hd" use the same underlying engine, ensuring identical voice characteristics and audio structure. This consistency simplifies quality control for producers who need uniform output across different chapters or segments of a book.

Predictable Latency

Generation speed averages roughly real-time, producing about 25 characters of text per second of audio. Short phrases may take a few seconds to synthesize, while longer texts are processed in manageable chunks to maintain stability.

Requests are processed one after another. Under load, a request may wait in a queue, but the system ensures complete audio files are delivered.

Standard Protocols

The API uses standard HTTP POST requests with JSON bodies, compatible with the official OpenAI SDKs by simply changing the base URL. This allows developers to use existing libraries for authentication and error handling without custom integrations.

  • Standard HTTP/JSON interface
  • Compatible with OpenAI SDKs
  • No custom protocols required

Content Ownership and Rights

Sound wave illustration for: Content Ownership and Rights

ReadCast API uses voices derived from the LibriTTS-R dataset (CC BY 4.0) and public-domain LibriVox readings, providing a clear licensing foundation for independent creators. Generated audio is returned in the response and not stored, ensuring your input text is used solely for synthesis and never for model training.

Licensed Source Voices

All eight voice presets are based on licensed recordings from established open-source datasets. This ensures that the audio you generate has a transparent origin, avoiding the ambiguity often found with proprietary voice models. Creators can rely on consistent, pre-vetted source material for their audiobook projects without negotiating individual voice rights.

  • Voices derived from LibriTTS-R (CC BY 4.0)
  • Based on public-domain LibriVox audiobook readings
  • Transparent licensing based on CC BY 4.0 and public domain sources

Synthetic Watermarking

Every generated audio file carries an inaudible watermark that marks it as synthetic speech. This digital signature helps identify the content's origin as AI-generated without affecting the listening experience. It provides a layer of authenticity for publishers and platforms that require disclosure of synthetic media.

No Training Data Usage

Input text is used only to produce the audio and is not added to our training data. Unlike some competitors, we do not retain your manuscript for future model improvement. Request metadata is kept solely for billing purposes, ensuring your creative work remains private and yours.

  • Input text not used for training
  • No retention of manuscript content
  • Metadata kept only for billing

Accessibility and Inclusion

Sound wave illustration for: Accessibility and Inclusion

ReadCast API supports 23 languages, enabling independent authors to reach global audiences with consistent audio quality. The system automatically detects language from the script, though users can explicitly set the ISO code for non-English Latin texts to ensure accurate pronunciation.

With eight distinct voice presets ranging from warm narrators to deep documentary styles, creators can select tones that match their content’s mood without needing multiple voice actors.

Clear Speech Synthesis

The engine delivers clear, natural-sounding speech suitable for long-form narration. Text is processed in chunks of up to 4096 characters, ensuring consistent audio quality throughout lengthy manuscripts.

Diverse Voice Options

Eight voices cover a wide range of tones: female options like Aria (warm narrator) and Luna (soft storytelling), and male choices like Felix (energetic) and Orion (deep documentary). Any voice can speak any supported language, allowing flexible casting.

Universal Access

Audio files are delivered in standard formats (mp3, wav, opus, flac, pcm), ensuring compatibility with all major audiobook platforms and devices. No proprietary players are required for distribution.

  • Supports 23 languages including English, Spanish, German, Japanese, and Hindi
  • No special hardware required for playback
  • Standard audio formats ensure broad device compatibility

Getting Started with ReadCast

Sound wave illustration for: Getting Started with ReadCast

Begin by signing up on our /get-api-key/ page using Google or an email account. This process takes seconds and immediately provides your unique API key, current balance, and a ready-to-use cURL example for testing.

Before integrating, explore our demo audio samples to hear the distinct narration styles. You can verify voice quality and language clarity directly in your browser, ensuring the selected voice matches your audiobook’s tone.

Quick Sign Up

Registration is instant via Google or email. Upon creation, you receive a single active API key and access to $0.50 in free trial credit, valid for 7 days. This allows immediate testing without a credit card.

  • Google or email registration
  • Instant API key generation
  • $0.50 trial credit included
  • No minimum spend required

Demo Audio Samples

Listen to the eight voice presets to evaluate clarity and pacing. Each sample demonstrates the specific character range, from Aria’s warm narration to Orion’s deep documentary style, helping you select the best fit for your manuscript.

  • 8 distinct voice presets
  • Real-time audio playback
  • Variety of tones and speeds

Developer Documentation

Visit /docs/ for complete API specifications. The endpoint follows the OpenAI speech format, allowing you to use standard SDKs by simply changing the base URL. Detailed examples cover request structure, voice selection, and format options.

  • OpenAI-compatible endpoint
  • Clear request/response examples
  • Support for all 8 voices

Listen to the 8 voices

Each sample below was generated by this API from the same sentence. The ability to specify language codes ensures accurate pronunciation for non-native speakers, enhancing accessibility for diverse student demographics.

Avatar of the voice aria
ariafemale
Avatar of the voice nova
novafemale
Avatar of the voice luna
lunafemale
Avatar of the voice sage
sagefemale
Avatar of the voice felix
felixmale
Avatar of the voice milo
milomale
Avatar of the voice atlas
atlasmale
Avatar of the voice orion
orionmale

23 languages

Any voice speaks any of these languages.

Sources and further reading

  1. Wikipedia
  2. IETF RFC 7845: Ogg Opus
  3. Node.js documentation
  4. ISO 639 language codes
  5. Python documentation
  6. LibriVox public-domain audiobooks
  7. Tether (USDT)
  8. FFmpeg documentation
  9. W3C WAI: making audio and video accessible
  10. TRON developer hub: TRC-20
  11. openai-node on GitHub
  12. MDN: Web Speech API

More on this site