The plugin routes through the SLNG gateway. Switching between Deepgram, ElevenLabs, Sarvam, Rime, Cartesia, and the rest is a model string change. No rewrites, and your agent logic doesn't move.

Prerequisites:

• Python 3.10+
• livekit-agents>=1.5.1
• A LiveKit Agents project
• An SLNG API key

import os
from livekit.agents import AgentSession
from livekit.plugins import slng, silero

session = AgentSession(
    stt=slng.STT(
        api_key=os.environ["SLNG_API_KEY"],
        model="deepgram/nova:3",
        language="en",
    ),
    tts=slng.TTS(
        api_key=os.environ["SLNG_API_KEY"],
        model="deepgram/aura:2",
        voice="aura-2-thalia-en",
    ),
    vad=silero.VAD.load(),
)

Swap model="sarvam/bulbul:v3" for Sarvam Bulbul TTS, or model="slng/deepgram/nova:3-multi" for multilingual Nova-3.

Full catalog in the docs.

If your agents run under data residency requirements like EU, UK, India, UAE, region_override pins traffic to the right gateway hub. Audio is processed in-region and stays there. No architecture changes or separate deployment needed.

STT accepts a list of model_endpoints. If the active one returns an error, the plugin falls over to the next automatically. No retry logic to write, no single provider bringing your agent down.

Also included

• WebSocket streaming STT and TTS
• Connection pooling for TTS
• Interim transcription results
• Speaker diarization The plugin is open source: livekit/agents repo.

1. Get an API key
2. Read the plugin docs for the full model catalog and configuration reference
3. LiveKit Agents quickstart if you're new to the framework

What is the SLNG plugin for LiveKit Agents?

The SLNG plugin connects LiveKit Agents to the SLNG voice AI gateway. It gives your agent access to every STT and TTS model in the SLNG catalog — Deepgram, ElevenLabs, Sarvam, Rime, Cartesia, and others — through a single integration. You install it with uv add "livekit-agents[slng]~=1.5" and configure it like any other LiveKit plugin.

Does the SLNG plugin change how I write my agent logic?

No. Your agent logic stays the same. The plugin routes through the SLNG gateway at the model level — switching providers is a model string change, not a code change.

How do I switch between STT or TTS providers with the SLNG plugin?

Change the model parameter. For example, swap model="deepgram/nova:3" for model="deepgram/nova:3-multi" for multilingual STT, or model="sarvam/bulbul:v3" for Sarvam TTS. No other changes needed.

Does SLNG support data residency requirements in LiveKit agents?

Yes. Pass region_override on the STT or TTS class to pin traffic to a specific gateway hub — EU, UK, India, UAE, and others. Audio is processed in-region and stays there.

What happens if a model endpoint goes down?

The STT class accepts a list of model_endpoints. If the active one returns an error, the plugin falls over to the next one automatically. No retry logic required on your side.

Is the SLNG LiveKit plugin open source?

Yes. The plugin is part of the official livekit/agents repo.

Which LiveKit Agents version is required?

livekit-agents 1.5.7 or later.