livekit-plugins-munsit
LiveKit Agents plugin for Munsit voice AI: Arabic speech-to-text (batch and live streaming) and Arabic text-to-speech.
This package consolidates the former
livekit-plugins-faseeh(TTS) — that name now ships a deprecation shim that installs this package.
Installation
pip install livekit-plugins-munsit
Set your API key (from the Munsit dashboard):
export MUNSIT_API_KEY=your-key
Speech-to-Text
from livekit.agents import AgentSession
from livekit.plugins import munsit, silero
session = AgentSession(
stt=munsit.STT(mode="streaming"), # live transcription over WS /api/v1/listen
vad=silero.VAD.load(),
)
Two modes:
mode="streaming" (default) |
mode="batch" |
|
|---|---|---|
| Transport | WS /api/v1/listen |
POST /api/v1/audio/transcribe |
| Interim results | yes (INTERIM_TRANSCRIPT) |
no |
| Turn detection | server-side (endpointing + semantic smart-turn) | client energy VAD |
| Word timestamps + confidence | yes, on finals | yes |
| Models | munsit, munsit-en-ar (default) |
munsit, munsit-en-ar (default) |
Streaming options:
munsit.STT(
mode="streaming",
endpointing_ms=800, # silence that ends a turn (100–5000; retunable live)
smart_turn=True, # semantic end-of-turn gating
hotwords=["فرحان", "تطبيق منصت"], # custom vocabulary (≤200 entries, ≤40 chars)
interim_results=True,
correlation_id="call-1234",
on_enrichment=lambda ev: print(ev), # per-turn Sentiment / Gender events
)
Batch extras: hotwords=[...] and return_confidence=True (per-word confidence on
timestamps). hotwords only bias the Arabic munsit model — with munsit-en-ar
(the default) they are ignored with a warning, in both modes.
Text-to-Speech
from livekit.plugins import munsit
tts = munsit.TTS(
voice_id="ar-hijazi-female-1",
model="faseeh-v1-preview",
)
MUNSIT_API_KEY is used for both engines (the legacy FASEEH_API_KEY env var still works
for TTS).
Documentation
Full API reference: https://docs.munsit.com — see Speech-to-Text Streaming for the
/api/v1/listen protocol (events, close codes, billing).
Development
uv sync
uv run pytest tests/ -k "not Integration" # offline suite (fake server)
MUNSIT_API_KEY=... uv run pytest tests/ # includes live integration tests
License
Apache-2.0
Metadata
Release files for livekit-plugins-munsit 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| livekit_plugins_munsit-0.4.0.tar.gz | 23.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| livekit_plugins_munsit-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 51.5 kB
Release files / livekit_plugins_munsit-0.4.0.tar.gz
| Download URL | livekit_plugins_munsit-0.4.0.tar.gz |
|---|---|
| Size | 23.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
77f90cfd85e443b6df641bd4adf1d5db01a2bc553d50ca0551f18561d7027dde
|
|
BLAKE2b-256 checksum How to use checksums |
64d6652bb6f41f521eb79103958b240139eec67428f65ec50a17873dea6118ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 28, 2026.
Transparency logRelease files / livekit_plugins_munsit-0.4.0-py3-none-any.whl
| Download URL | livekit_plugins_munsit-0.4.0-py3-none-any.whl |
|---|---|
| Size | 27.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
519a115f38008823968e5ee4a51e9f7118fd36f1a4d08de80ce5ca3d95f3a986
|
|
BLAKE2b-256 checksum How to use checksums |
760584722a2c4b25c0820da9d4b0f864ba59c875a8e6b67ae5d713186ad6669c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 28, 2026.
Transparency log