omniroute-tts

Route text-to-speech requests through OmniRoute to generate spoken audio.

44.0k|5.9k|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/diegosouzapw/OmniRoute --skill omniroute-tts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omniroute-tts
Source: https://github.com/diegosouzapw/OmniRoute/tree/main/skills/omniroute-tts
Command: npx skills add https://github.com/diegosouzapw/OmniRoute --skill omniroute-tts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OmniRoute TTS removes the hassle of picking the “right” text-to-speech provider by automatically routing a single request to a provider that can fulfill it, producing spoken audio output reliably.

Core Features & Use Cases

  • Unified TTS Endpoint: Send text and get back audio from OmniRoute using the /v1/audio/speech API.
  • Auto-fallback Across Providers: Automatically fall back between OpenAI TTS, ElevenLabs, Azure Neural, and Google Cloud TTS when a provider/model fails.
  • Voice Discovery via Models: Use /v1/models/tts to discover supported voices per provider and select the best one.

Use case: Generate spoken narration for a chatbot response, tutorial script, or app notification while minimizing voice/provider failures and keeping output consistent.

Quick Start

Send a POST request to $OMNIROUTE_URL/v1/audio/speech with Authorization: Bearer $OMNIROUTE_KEY and a JSON body specifying model: "tts-1", your input text, a supported voice name (check /v1/models/tts), and your response_format (such as mp3).

Frequently Asked Questions about omniroute-tts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does text-to-speech fallback routing work across different AI providers?

Text-to-speech fallback routing automatically retries your audio generation request across different AI providers like OpenAI, ElevenLabs, Azure, and Google Cloud if the initial provider fails, ensuring reliable spoken audio output.

How do I generate spoken audio from text using a unified TTS endpoint?

To generate spoken audio, send a POST request to the /v1/audio/speech endpoint with your text input, a TTS model like tts-1, a supported voice, and the desired response format such as mp3 to receive an audio binary.

Do I need an API key to use OmniRoute for audio generation?

Yes, you need an OMNIROUTE_URL and OMNIROUTE_KEY to authenticate audio generation requests using Bearer authorization when sending text-to-speech requests through the OmniRoute API.

How do I discover supported voices for TTS models?

You can discover supported voices per provider by querying the /v1/models/tts endpoint, allowing you to select the best available voice for your text-to-speech audio generation needs.

Can I use mp3 as a response format for TTS audio binaries?

Yes, you can specify mp3 as your response_format in the JSON body of your text-to-speech request to receive audio binaries in mp3 format from the provider.

What is the best way to avoid provider failures when generating voice responses?

The best way to avoid provider failures during voice generation is to use a unified TTS endpoint with auto-fallback routing, which automatically switches to alternative AI providers if the primary one fails.