Is Kuwi TTS API the Best Alternative to Oddcast?

By Kuwi Audio editorial team · Updated 2026-11-18

This page compares Kuwi’s text-to-speech API against Oddcast, evaluating whether a cloud-first approach serves podcast publishers needing scalable episodic content production. We analyze voice quality, pricing structures, and technical flexibility to help you decide if switching aligns with your production workflow.

Readers will find concrete data on character-based pricing, voice licensing origins, and API integration specifics. This guide is designed for technical decision-makers and audio producers who require predictable costs and consistent broadcast-quality audio without legacy infrastructure constraints.

Is Kuwi TTS API the Best Alternative to Oddcast?

Frequently asked questions

What was Oddcast primarily used for?

Oddcast was primarily used for legacy broadcast and streaming TTS, often requiring dedicated hardware or complex on-premise infrastructure. It served radio and early web streams but lacked the flexibility of modern cloud APIs.

Is Oddcast still a popular TTS solution?

Oddcast remains a known name in broadcast but has lost significant market share to cloud-native APIs. Many publishers have migrated to scalable, API-driven solutions like Kuwi for better integration and predictable costs.

Why are podcasters switching to API-based TTS?

Podcasters switch to API-based TTS for scalability, predictable pricing, and easier integration. Kuwi offers a simple POST endpoint, consistent voice quality, and supports 23 languages without the overhead of managing dedicated hardware.

How does Kuwi differ from Oddcast?

Kuwi is a cloud API with a standard JSON interface, unlike Oddcast’s legacy broadcast focus. Kuwi offers 8 distinct voices, 23 languages, and transparent per-character pricing, whereas Oddcast often relies on complex licensing models.

Is Kuwi better for large-scale podcast production?

Yes, Kuwi is designed for scale. With 60 requests per minute and support for 4096-character inputs, it handles episodic content efficiently. Its predictable $0.01 per 1000 characters pricing aids budget planning for high-volume publishers.

Does Kuwi offer more voice options than Oddcast?

Kuwi provides 8 curated voice presets (4 female, 4 male) with distinct tones. While Oddcast offered various voices, Kuwi’s selection is optimized for clarity and consistency across 23 languages, ensuring uniform quality for series.

How does the pricing of Kuwi compare to Oddcast?

Kuwi charges $0.01 per 1000 characters with no monthly fees or subscriptions. This pay-as-you-go model contrasts with Oddcast’s often complex licensing, offering transparent costs where failed requests are free and balance never expires.

Can I integrate Kuwi into existing workflows?

Yes, Kuwi uses a standard OpenAI-compatible endpoint. You can integrate it using existing HTTP clients or the OpenAI SDK by simply changing the base URL, making it easy to plug into automated podcast pipelines.

What is the audio quality of Kuwi compared to legacy systems?

Kuwi delivers broadcast-quality audio using licensed recordings from LibriTTS and LibriVox. The voices are clear and natural, with an inaudible synthetic watermark, offering consistent quality superior to many older, robotic-sounding legacy TTS systems.

Are there any hidden costs with Kuwi?

No hidden costs. Kuwi charges only for successful synthesis at $0.01 per 1000 characters. Failed requests are free, and there are no subscription fees, seat limits, or minimum spends. Top-ups via USDT on the TRON network are straightforward.

Is Kuwi suitable for audiobook production?

Yes, Kuwi is suitable for audiobooks. It supports 4096 characters per request, allowing you to split longer texts. The voices like Luna (storytelling) and Orion (documentary) are well-suited for long-form narrative content.

How does Kuwi handle language support?

Kuwi supports 23 languages, including English, Spanish, German, and Japanese. Any voice can speak any supported language. You can specify the ISO code or let the API guess it, ensuring accurate pronunciation for global audiences.

What is the latency of Kuwi's API?

Latency is roughly real-time, generating about 25 characters of text per second of audio. Short phrases take a few seconds, while longer texts process sequentially. Requests may queue under load, but typical speed is consistent.

Do I need technical expertise to use Kuwi?

Basic technical knowledge is needed. You send a POST request with JSON body including model, input, voice, and format. Kuwi provides curl examples and works with standard HTTP libraries, making it accessible for developers and technical producers.

Origins of Oddcast

Sound wave illustration for: Origins of Oddcast

History of the Brand

The company built its reputation on delivering reliable, pre-recorded audio streams to terrestrial and digital radio networks. Its infrastructure prioritized stability and long-term archival over the dynamic, request-driven models that dominate modern content creation.

Legacy TTS Technology

While robust for scheduled shows, it lacked the granular control and rapid iteration capabilities required by modern episodic podcast publishers generating content on tight deadlines.

  • Concatenative synthesis foundation
  • Optimized for continuous streams
  • Limited real-time control

Market Position

It maintained a strong presence in traditional broadcasting, serving large networks that required consistent, branded audio identities. However, its pricing and technical structure were less suited for the agile, character-based production workflows typical of independent podcast studios today.

Limitations of Legacy TTS

Sound wave illustration for: Limitations of Legacy TTS

Legacy TTS systems often struggle with natural prosody, resulting in robotic cadence that distracts listeners in long-form content. Voice quality remains static, lacking the emotional nuance expected in modern podcasting.

This structure penalizes high-volume episodic production with predictable overhead costs.

Voice Quality Constraints

Standard legacy engines deliver consistent but flat intonation. They lack the subtle breathiness and pacing variations found in human narration, making extended listening fatiguing.

Voice variety is limited by pre-installed libraries. Switching voices often requires separate license purchases or manual configuration, disrupting workflow efficiency.

  • Flat prosody in long segments
  • Limited emotional range
  • Static voice libraries

Pricing Structure Issues

Many legacy providers charge based on character count with complex tiered discounts that are difficult to forecast. Hidden fees for premium voices or extra languages add unexpected costs.

Monthly minimums mean you pay for capacity you do not use, reducing margin on smaller episodic releases.

  • Complex tiered discounts
  • Hidden premium fees
  • Monthly minimum commitments

Technical Rigidity

Integration often requires on-premise servers or complex middleware, increasing infrastructure overhead. API access is limited or expensive, preventing dynamic content updates.

Updating voice models requires manual upgrades, leading to version drift across different production environments.

  • On-premise dependencies
  • Expensive API access
  • Manual model updates

The Rise of API-First TTS

Sound wave illustration for: The Rise of API-First TTS

The industry has shifted from on-premise servers to cloud APIs, allowing publishers to generate audio directly within their production pipelines. This model eliminates hardware dependencies and enables immediate scaling for episodic content.

Shift to Cloud APIs

Cloud-based architectures allow podcast publishers to integrate text-to-speech generation directly into their editorial workflows. Instead of managing dedicated servers, teams send JSON payloads and receive audio files instantly, streamlining the path from script to broadcast-ready audio.

Developer Experience

Modern TTS APIs follow standard RESTful patterns, making integration straightforward for engineering teams. Using standard HTTP libraries or familiar SDKs, developers can embed voice generation into content management systems without learning proprietary protocols. Authentication is handled via simple bearer tokens, reducing overhead.

Scalability Benefits

Cloud infrastructure handles traffic spikes automatically, ensuring consistent delivery during high-volume publishing periods. Requests are processed sequentially, so under load a request may wait in a queue. This elasticity supports growth without significant upfront infrastructure investment.

Kuwi as a Modern Alternative

Sound wave illustration for: Kuwi as a Modern Alternative

Kuwi Audio offers eight distinct voice presets suitable for diverse podcast formats, from warm narration to energetic promos. Unlike legacy systems requiring separate licenses per voice, Kuwi provides immediate access to all models via a single API key.

Voice Variety

Publishers can choose from female voices like Aria and Nova, or male options such as Felix and Atlas, all capable of speaking any of the 23 supported languages. This allows for consistent audio quality across episodic content without negotiating individual voice rights.

Cost Efficiency

Pricing is transparent at $10 per million characters, with no monthly subscriptions or hidden fees. Failed requests incur no charge, and the free trial provides $0.50 in credit, reducing risk for new publishers testing their production pipeline.

Integration Ease

The API follows the standard OpenAI request shape, allowing immediate use of existing OpenAI SDKs by simply changing the base URL. This minimizes development time for integrating text-to-speech into podcast publishing workflows.

Use Case Comparison

Sound wave illustration for: Use Case Comparison

Oddcast served legacy broadcast infrastructure, while Kuwi targets episodic podcast production via a simple REST API. Publishers can convert full scripts into broadcast-quality audio at scale without managing hardware.

Kuwi’s character-based pricing ($0.01 per 1,000 characters) offers predictable costs for long-form content.

Podcast Production

Kuwi’s eight voice presets support varied narrative styles, from warm narration to energetic promos. Scripts are split into 4096-character segments, ensuring consistent quality even for multi-hour episodes.

The API returns standard audio formats (mp3, wav, opus, flac, pcm), integrating directly into existing podcast workflows without custom middleware.

  • Support for 23 languages
  • Consistent voice quality per episode
  • No minimum spend

Audiobook Creation

With 4096 characters per request, long texts are processed sequentially. Generation takes roughly real-time, allowing steady production pipelines for serialized content.

Audio files include inaudible watermarks, confirming synthetic origin without affecting listener experience.

Real-Time Applications

Kuwi is not designed for real-time streaming or WebSocket delivery. Requests are processed sequentially, so under load, latency increases as requests queue.

Short phrases take a few seconds to generate; large batches may require waiting periods before completion.

Voice Licensing Differences

Sound wave illustration for: Voice Licensing Differences

Kuwi Audio sources its voice data from licensed recordings, primarily drawn from the LibriTTS-R dataset (CC BY 4.0) and public-domain audiobook readings from LibriVox. This foundation ensures that the core vocal models are built upon historically significant, legally cleared audio material.

Public Domain Sources

Our voices are derived from LibriTTS-R, a licensed dataset, and LibriVox public-domain readings. This provides a stable, reproducible base for our eight preset voices without relying on unique, hard-to-license celebrity likenesses.

Commercial Rights

Because the underlying recordings are public domain or broadly licensed, Kuwi Audio grants you full commercial rights to the generated audio files. You can use these files in podcast episodes, sponsored content, or audiobooks without worrying about recurring royalty fees or usage restrictions.

Watermarking

Every generated audio file contains an inaudible watermark that marks it as synthetic speech. This provides transparency for platforms and listeners who may require disclosure of AI-generated content, while remaining imperceptible during normal playback.

Technical Specifications

Sound wave illustration for: Technical Specifications

Kuwi Audio’s API follows the standard OpenAI request shape, accepting text up to 4,096 characters per call. You specify the model (tts-1 or tts-1-hd), voice preset, response format (mp3, wav, opus, flac, pcm), and optional speed or language parameters via a simple JSON POST to /v1/audio/speech.

Request Formats

Send a POST request to https://api.playkuwi.com/v1/audio/speech with your Bearer token. The body includes the text input, voice selection, and desired output format. For longer scripts, split text into chunks and join the resulting audio files.

  • Supports mp3, wav, opus, flac, and pcm formats
  • Text limit: 4,096 characters per request
  • Speed adjustable from 0.25x to 4.0x

Response Latency

Generation speed averages roughly one second of audio per 25 characters of text. Short phrases may take a few seconds due to processing overhead, while longer texts approach real-time generation speeds.

Requests are processed sequentially, so high load may introduce queue delays.

Error Handling

If synthesis fails, the request incurs no charge and the error details are returned in the JSON response. This ensures you only pay for successful audio generation, protecting your budget during unexpected API issues.

Technical Specifications

Pricing Models Compared

Sound wave illustration for: Pricing Models Compared

Oddcast traditionally relied on licensing models suited for broadcast infrastructure, whereas Kuwi Audio uses a straightforward pay-per-use API. This shift eliminates upfront costs and aligns expenses directly with production volume, offering predictable billing for episodic content.

Subscription vs. Pay-Per-Use

Kuwi Audio charges $10 per 1 million characters, equating to $0.01 per 1,000 characters. This model removes monthly commitments, allowing publishers to pay only for what they generate. There are no seats, minimum spends, or subscription tiers to manage.

  • No monthly plans or subscription tiers.
  • Pay only for actual character usage.
  • No minimum spend requirements.

Character Counting

Billing is based on the total character count of your input text, including spaces and punctuation. Each request supports up to 4,096 characters, with longer texts split and joined automatically. Failed requests incur no charge, ensuring you pay only for successful synthesis.

Hidden Fees

Kuwi Audio does not offer invoices with VAT. Payments are processed via USDT on the TRON network (TRC-20), with a $5 minimum top-up. Balances do not expire, and no hidden costs apply to voice selection or format conversion.

Future of Podcast Audio

Sound wave illustration for: Future of Podcast Audio

AI-driven audio generation is reshaping podcast production, enabling publishers to convert scripts into broadcast-quality audio at scale without studio overhead. The shift toward cloud-native APIs allows for consistent voice quality and predictable costs, essential for episodic content.

This transition supports higher output volumes while maintaining audio fidelity, reducing the dependency on traditional voice talent for every episode.

AI Generation Trends

Modern TTS APIs prioritize consistency and speed, allowing publishers to generate hours of content from a single script. The move from on-premise servers to cloud endpoints simplifies infrastructure management for growing podcast networks.

Generative models now handle natural intonation and pacing more effectively, reducing the need for extensive post-production editing.

  • Cloud-based processing reduces hardware dependencies
  • Automated script-to-audio workflows increase production speed

Voice Customization

While true voice cloning is not yet standard, API providers offer a range of preset voices with distinct tonal qualities. Publishers can select voices that match their brand identity, from calm narrators to energetic hosts.

Standardization of voice presets ensures that all episodes maintain a uniform auditory experience, crucial for listener retention.

  • Multiple voice presets for different tones
  • Consistent branding across episodes

Market Growth

The demand for on-demand audio content continues to rise, driving the adoption of scalable TTS solutions. Publishers are increasingly looking for cost-effective alternatives to traditional recording studios to expand their library.

As audio consumption grows, the ability to quickly produce high-quality episodes becomes a competitive advantage for new and established podcasters alike.

  • Rising demand for on-demand audio
  • Cost efficiency drives adoption

Why Publishers Switch

Sound wave illustration for: Why Publishers Switch

Publishers switch to Kuwi Audio to replace legacy TTS contracts with transparent, usage-based billing. With a flat rate of $0.01 per 1,000 characters, production costs become predictable and directly tied to script volume, eliminating unused seat licenses or monthly minimums that inflate overhead for episodic content.

Cost Savings

The API charges only for actual character counts, including spaces and punctuation. Failed requests incur no charge, ensuring you pay solely for delivered audio. This pay-per-use model scales efficiently with your publishing schedule without the waste of reserved capacity.

Quality Improvements

Kuwi offers eight distinct voice presets, ranging from the warm narrator Aria to the deep documentary tone of Orion. These voices, derived from licensed LibriTTS-R recordings, provide broadcast-ready clarity and consistency across episodes, surpassing the robotic limitations of older engine generations.

Flexibility

Support for 23 languages and adjustable speed (0.25–4.0x) allows dynamic adaptation to diverse content needs. The API-first approach integrates directly into existing workflows via standard HTTP requests, offering greater control than rigid, on-premise legacy solutions.

Getting Started with Kuwi

Sound wave illustration for: Getting Started with Kuwi

Kuwi Audio is designed for podcast publishers who need a straightforward, reliable API to convert scripts into broadcast-quality audio. Getting started requires minimal configuration, allowing your team to begin generating episodic content immediately without complex onboarding procedures.

The process focuses on clarity and speed. You create an account, retrieve your authentication key, and make your first API call using standard HTTP requests or the OpenAI SDK. This ensures you can integrate Kuwi into your existing production pipeline with minimal friction.

Account Setup

Sign up at /get-api-key/ using Google or email. Google sign-up includes a $0.50 trial credit valid for 7 days, providing approximately 50,000 characters. Email-based accounts start with zero balance.

Accounts are per site, ensuring isolated usage tracking. No monthly plans or minimum spend requirements apply, allowing you to scale usage up or down freely.

  • Google or email registration
  • $0.50 trial credit with Google sign-up
  • No minimum spend required

API Key Retrieval

Your unique API key is displayed on the dashboard immediately after registration. One active key is issued per account; generating a new key instantly invalidates the previous one.

Use the key in the Authorization: Bearer tts-... header for all requests. The dashboard also shows your current balance, trial status, and character usage.

  • One active key per account
  • Instant key rotation
  • Dashboard shows balance and usage

First Integration

Send a POST request to https://api.playkuwi.com/v1/audio/speech with your JSON body containing model, input, and voice. Use the OpenAI SDK by setting base_url to https://api.playkuwi.com/v1.

The API returns an audio file directly. Failed requests are free, and charges are based on character count, including spaces and punctuation.

  • POST /v1/audio/speech endpoint
  • Supports OpenAI SDK via base_url change
  • Returns audio file directly

Conclusion

Sound wave illustration for: Conclusion

Kuwi Audio offers a predictable, character-based pricing model with high-quality synthetic voices derived from licensed public-domain sources, making it a viable alternative to legacy systems like Oddcast for podcast publishers.

By eliminating subscription fees and offering instant API integration, publishers can scale episodic content production efficiently while maintaining consistent audio quality without the technical rigidity of older TTS engines.

Summary of Benefits

The API provides reliable, cloud-based text-to-speech conversion with eight distinct voice presets and support for 23 languages, ensuring broadcast-ready audio for diverse podcast scripts.

With transparent pricing at $10 per million characters and no hidden fees, publishers gain cost efficiency and scalability without the constraints of traditional licensing models.

  • Predictable pay-per-use pricing
  • 8 high-quality voice presets
  • 23 language support
  • Instant API integration

Recommendation for Publishers

For podcast publishers seeking to automate script-to-audio workflows, Kuwi Audio delivers the consistency and scalability needed for episodic content production.

It is particularly suitable for teams prioritizing cost efficiency and ease of integration.

Next Steps

Sign up for a free trial with $0.50 credit to test voice quality and latency with your own scripts.

Retrieve your API key and integrate the endpoint into your production pipeline to start generating audio at scale.

Listen to the 8 voices

Each sample below was generated by this API from the same sentence.

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. OpenAI API reference: create speech
  3. TRON developer hub: TRC-20
  4. openai-node on GitHub
  5. Tether (USDT)
  6. MDN: Web Speech API
  7. Creative Commons Attribution 4.0
  8. W3C WAI: making audio and video accessible
  9. curl documentation
  10. IETF RFC 7845: Ogg Opus
  11. LibriVox public-domain audiobooks
  12. openai-python on GitHub

More on this site