Skip to main content
The Inference Gateway is a unified entry point for the model stack. Instead of holding a separate API key for each provider, you authenticate once with your Zero Runtime auth token and route speech-to-text, LLM, text-to-speech, turn detection, and denoise through the gateway. It manages the upstream provider connections, resampling, and streaming server-side.

Setup

Gateway providers connect using your Zero Runtime auth token, no provider API keys are required. Set it in the worker environment:

Usage

Import gateway providers from zrt.inference and drop them into the pipeline exactly like normal plugins. Every gateway class is a drop-in replacement for its zrt.plugins equivalent. Turn detection is the unified TurnDetector (imported from zrt.plugins) using an Echo model, which also routes through the gateway:
You can mix gateway and direct-provider components freely in the same pipeline. For example, run STT and TTS through the gateway while the LLM uses its own key.

Supported providers

Import paths

Every gateway class is imported from the single zrt.inference module: Denoisers also expose factory methods, Denoise.sanas() and Denoise.aicoustics(), which return the same configured component as the named aliases above.

Why use it

  • One credential. Authenticate with a single Zero Runtime token instead of provisioning and rotating a key for every provider.
  • Less client work. Connection management, resampling, and streaming happen server-side.
  • Easy switching. Swap a gateway provider without onboarding a new API key.

What’s next

Configure a Pipeline

How gateway providers slot into a pipeline, with cascading and realtime examples.

Plugins

The full catalog of STT, LLM, TTS, and denoise providers.