Skip to main content

livekit-plugins-oogam

Oogam for LiveKit Agents: streaming speech-to-text, text-to-speech (Naad) and Sutra, for 27 Indian languages and English.

Service Class Oogam endpoint
Speech to text oogam.STT wss://platform.oogam.ai/v1/realtime?intent=transcription
Text to speech oogam.TTS POST /v1/audio/speech (streamed PCM)
Sutra oogam.LLM POST /v1/chat/completions

Install

pip install "livekit-agents[silero]~=1.8" livekit-plugins-oogam python-dotenv

Python 3.10 or later, LiveKit Agents 1.8. Create an API key with the NAAD product (and SUTRA for the LLM) on the Oogam Platform and set OOGAM_API_KEY.

Quick start

from dotenv import load_dotenv

from livekit import agents
from livekit.agents import Agent, AgentServer, AgentSession
from livekit.plugins import oogam, silero

load_dotenv()


class Assistant(Agent):
    def __init__(self) -> None:
        super().__init__(
            instructions="You are a helpful assistant. Reply in one or two short spoken sentences, in the caller's language.",
        )

    async def on_enter(self) -> None:
        self.session.generate_reply(instructions="Greet the caller in Hindi.")


server = AgentServer()


@server.rtc_session()
async def entrypoint(ctx: agents.JobContext):
    session = AgentSession(
        stt=oogam.STT(language="hi"),
        llm=oogam.LLM(),
        tts=oogam.TTS(voice="aditi", language="hi"),
        vad=silero.VAD.load(),
    )
    await session.start(room=ctx.room, agent=Assistant())


if __name__ == "__main__":
    agents.cli.run_app(server)
python agent.py console   # talk to it in the terminal
python agent.py dev       # join a LiveKit room

LiveKit's own CLI runs the same file with lk agent console and lk agent dev.

Turn-taking

Keep a VAD, as the quick start does. The STT declares manual_flush: when LiveKit decides the caller has stopped — Silero's end of speech, or your turn detector's verdict — it flushes the stream and the plugin sends Oogam finalize, so the turn closes at that moment. The VAD also lets callers interrupt the agent.

Measured on live calls (Hindi and Indian English, LiveKit Agents 1.8, Sutra and Oogam TTS, 14 calls):

Setup Transcript after the caller stops Agent starts speaking
vad=silero.VAD.load() 0.6–0.75 s 1.8–2.0 s
silero.VAD.load(min_silence_duration=0.3) 0.6–0.75 s 1.55–1.85 s
turn_detection="stt", min_delay 0.07 0.65–0.8 s 1.75–1.95 s
turn_detection="stt", default min_delay 0.65–0.75 s 2.1–2.3 s

Most of the time to the agent's first word is Sutra and the first sentence of speech. A shorter min_silence_duration answers sooner, but may cut in on a caller who pauses mid-sentence — test it with your callers.

LiveKit ignores the caller for the first 3 seconds the agent speaks in a call, while its echo cancellation warms up, so the greeting cannot be interrupted. Pass aec_warmup_duration=None to AgentSession if your callers are on headsets or phone lines and should be able to.

To let Oogam end each turn by itself (each transcript then arrives as START_OF_SPEECH, FINAL_TRANSCRIPT, END_OF_SPEECH), lower LiveKit's endpointing delay too, or it waits another 0.5 s after every transcript:

session = AgentSession(
    ...,
    turn_handling={"turn_detection": "stt", "endpointing": {"min_delay": 0.07}},
)

Languages

language takes Oogam's short codes (hi, gu, ta, en-IN, bho …), BCP-47 tags (hi-IN, gu-IN) or Oogam's 3-letter speech codes (HIN). Oogam does not detect the language at the start of a call: a session starts in the language you give it, so start in the caller's language when you know it. Plain en is American English; use en-IN for Indian English.

To follow a caller who switches language mid-call, turn on auto_switch and move the TTS with each transcript:

tts = oogam.TTS(voice="aditi", language="hi")
session = AgentSession(
    stt=oogam.STT(language="hi", auto_switch=True, candidates=["hi", "en-IN"]),
    llm=oogam.LLM(),
    tts=tts,
    vad=silero.VAD.load(),
)


@session.on("user_input_transcribed")
def follow_caller_language(ev):
    # Speak in the language the caller was last heard in.
    if ev.is_final and ev.language:
        tts.update_options(language=ev.language)

What to expect, measured on live calls (15 Nov 2026). A switch is noticed from a sentence that has already been transcribed, so it applies from the caller's second sentence (sometimes the third), and that first sentence is usually misheard. The engine also takes a few seconds to change language, so a sentence spoken while it switches can come back several seconds late. Hindi → English is the most reliable; Hindi → Tamil, Bengali and Marathi, and Tamil → English or Hindi, also switched. Hindi ↔ Gujarati, English → Hindi and Gujarati → English were not noticed: for those callers, start the session in their language, or switch it yourself with stt.update_options(language=...), which applies at once.

The voice follows the text. Oogam speaks a text only in a language that is written in its script, and refuses it otherwise. Since 0.1.1 a sentence that is not in the script of the TTS language — a Tamil reply while the TTS is set to Hindi — is spoken in the language that script belongs to, with the same voice, instead of failing and leaving the caller in silence. Text in Latin letters is always spoken in the TTS language. oogam.TTS(auto_language=False) turns this off; the refusal is then reported once, without retries.

Sutra and tools

Sutra does not support function calling yet: an agent with tools gets a 400 (tools_not_supported). For agents that need tools, keep oogam.STT and oogam.TTS and pair them with an LLM that supports tools.

Billing and limits

From your prepaid wallet: speech to text per second the session is open, text to speech per character, Sutra per token. An empty wallet is refused with a 402.

Each Sutra reply and each sentence the agent speaks is one request against your API key's requests-per-minute limit (60 on the Free plan; set per key in the dashboard). One live call makes roughly 15–25 a minute, so size the limit to the number of calls you run at once. A 429 is retried by LiveKit with backoff. Realtime sessions are admitted per key and per language.

MIT licensed. Maintained by DWET Labs.

Metadata

Release files for livekit-plugins-oogam 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for livekit-plugins-oogam 0.1.1
File Size Uploaded Provenance Actions
livekit_plugins_oogam-0.1.1.tar.gz 27.1 kB Without provenance Details for livekit_plugins_oogam-0.1.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for livekit-plugins-oogam 0.1.1
File Interpreter ABI Platform Actions
livekit_plugins_oogam-0.1.1-py3-none-any.whl Python 3 none any Details for livekit_plugins_oogam-0.1.1-py3-none-any.whl

Total release size: 47.2 kB

Release files / livekit_plugins_oogam-0.1.1.tar.gz

Download URL livekit_plugins_oogam-0.1.1.tar.gz
Size 27.1 kB
Tags Source
SHA-256 checksum
How to use checksums
81963a3c6117cd88f2d026914ce0114d461f390c706b9e3ef6527a355fc00b92
BLAKE2b-256 checksum
How to use checksums
ba626380417e70034391811893421fced80a67293410046add8c024d2400789d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.7

Release files / livekit_plugins_oogam-0.1.1-py3-none-any.whl

Download URL livekit_plugins_oogam-0.1.1-py3-none-any.whl
Size 20.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b2a87d113c77792951d4d2f4cf15c37a6673d82b28696bcbfc227b3280321447
BLAKE2b-256 checksum
How to use checksums
4a700707231629fc8f2cca3aff717eb0fd76a9764f8717e2b92cda7b060d6a14
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.7

Security for livekit-plugins-oogam 0.1.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page