This release is a pre-release and may not be stable for production use.
Speechmatics STT plugin for LiveKit Agents
Support for Speechmatics STT.
See https://docs.livekit.io/agents/integrations/stt/speechmatics/ for more information.
Installation
pip install livekit-plugins-speechmatics
Model
model selects the transcription model and defaults to linden-1
(speechmatics.Model.LINDEN_1). It is sent as given. operating_point, which Speechmatics
deprecated in favour of model, is not accepted.
Turn detection modes
The turn_detection_mode parameter controls how end-of-turn (endpointing) is detected:
VAD— Speechmatics runs its own VAD and closes turns itself (service-side endpointing). Novadis required. Pair it withturn_detection="stt"in theVoiceSession'sturn_handling, otherwise the session's own turn detector decides and Speechmatics' end-of-turn is ignored.EXTERNAL(default) — Speechmatics does not endpoint on its own. Turns close when the caller callsfinalize(). The plugin'svaddrivesfinalize()on end-of-speech; when none is passed,livekit-plugins-silerois loaded if it is installed. LiveKit does not callfinalize()for you, so withvad=None(and without callingfinalize()yourself) turns never close. The session's own turn detector decides when the user's turn ends;finalize()only makes Speechmatics flush what it has as a final segment.
The earlier FIXED, ADAPTIVE and SMART_TURN modes were removed: Agent STT exposes a single
service-side endpointing strategy, so select VAD or EXTERNAL. There is no replacement for
FIXED's end_of_utterance_silence_trigger timing, nor for speaker focus (focus_speakers,
ignore_speakers, focus_mode, update_speakers()); the other pre-Agent-STT arguments were removed
too, and diarization_sensitivity, enable_partials and speaker_active_format are now
speaker_sensitivity, include_partials and speaker_format.
Usage — service-side endpointing (VAD)
Let Speechmatics detect turns and tell the session to act on them:
from livekit.agents import TurnHandlingOptions, VoiceSession
from livekit.plugins import speechmatics
session = VoiceSession(
stt=speechmatics.STT(turn_detection_mode=speechmatics.TurnDetectionMode.VAD),
turn_handling=TurnHandlingOptions(turn_detection="stt"),
...
)
Usage — caller-driven endpointing (EXTERNAL, default)
Pass a vad to the plugin; its end-of-speech drives finalize(). VoiceSession loads its own VAD
when none is given, so pass the same instance to both and a single VAD serves the session and the
plugin:
from livekit.agents import VoiceSession, inference
from livekit.plugins import speechmatics
vad = inference.VAD()
session = VoiceSession(
stt=speechmatics.STT(
turn_detection_mode=speechmatics.TurnDetectionMode.EXTERNAL,
# The VAD passed here drives finalize() on end-of-speech.
vad=vad,
speaker_format="[Speaker {speaker_id}] {text}",
),
vad=vad,
...
)
Interim transcripts
The service sends partial segments by default, emitted as interim transcripts. Set
include_partials=False to receive final segments only:
stt = speechmatics.STT(include_partials=False)
Diarization
Speechmatics attributes each transcript segment to a speaker. Diarization is enabled by default
(enable_diarization=True); the segment is the unit of attribution, so each result carries a single
speaker_id and there is no per-word speaker data. To fold the speaker label into the transcript
text, set speaker_format using the {speaker_id} and {text} placeholders:
speaker_format="<{speaker_id}>{text}</{speaker_id}>"-><S1>Hello</S1>speaker_format="[Speaker {speaker_id}] {text}"->[Speaker S1] Hello
Segments the service did not attribute — including every segment when diarization is off — are
labelled UU.
Adjust your system instructions to inform the LLM of this format so it can attribute speakers.
from livekit.agents import VoiceSession
from livekit.plugins import speechmatics
session = VoiceSession(
stt=speechmatics.STT(
enable_diarization=True,
max_speakers=4,
speaker_format="[Speaker {speaker_id}] {text}",
additional_vocab=[
speechmatics.AdditionalVocabEntry(
content="LiveKit",
sounds_like=["live kit"],
),
],
),
...
)
Speaker identification
Speaker labels are per session by default, so S1 in one session is unrelated to S1 in the next.
To carry labels across sessions, read the identifiers out of a live session with
await stt.get_speaker_ids() (call it once each speaker has said a few words), then pass them back
as known_speakers on a later session:
speakers = await stt.get_speaker_ids()
stt = speechmatics.STT(known_speakers=speakers)
Each entry maps a human-readable label to the identifiers the engine recognizes it by. With more
than one open stream the call returns one list per stream instead.
Pre-requisites
You'll need to specify a Speechmatics API Key. It can be set as environment variable
SPEECHMATICS_API_KEY or in a .env.local file.
The plugin connects to wss://eu2.rt.speechmatics.com/v2/agent by default. To use another region or
a self-hosted endpoint, set base_url or the SPEECHMATICS_RT_URL environment variable.
Metadata
Release files for livekit-plugins-speechmatics 2.0.0b2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| livekit_plugins_speechmatics-2.0.0b2.tar.gz | 16.8 kB | With provenance | Details for livekit_plugins_speechmatics-2.0.0b2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| livekit_plugins_speechmatics-2.0.0b2-py3-none-any.whl | Python 3 | none | any | Details for livekit_plugins_speechmatics-2.0.0b2-py3-none-any.whl |
Total release size: 34.9 kB
Release files / livekit_plugins_speechmatics-2.0.0b2.tar.gz
| Download URL | livekit_plugins_speechmatics-2.0.0b2.tar.gz |
|---|---|
| Size | 16.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3f5faeb9e9b34c72c1553489b65ac5246e8dd0a7177fcb23bdfff305b3fedb3d
|
|
BLAKE2b-256 checksum How to use checksums |
a98cff43862ab3381a6911c3c19f4ed0d9ee4f9b7944f03418eeed901560945c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 Nov 18, 2026.
Transparency logRelease files / livekit_plugins_speechmatics-2.0.0b2-py3-none-any.whl
| Download URL | livekit_plugins_speechmatics-2.0.0b2-py3-none-any.whl |
|---|---|
| Size | 18.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e8e498b831980392c10f1f1352b8d854a1593180b5e5ab6fecd4b3bb8e52e01a
|
|
BLAKE2b-256 checksum How to use checksums |
b3d2fe5a48afeef511c4719e788bbf7c43b1b6897d8c13c902d6580d791b0662
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.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 Nov 18, 2026.
Transparency logSecurity for livekit-plugins-speechmatics 2.0.0b2
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for livekit_plugins_speechmatics-2.0.0b2.tar.gz
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 Nov 18, 2026.
Transparency logA 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.