Parlot
Production voice AI observability — MIT OpenTelemetry instrumentation for LiveKit Agents (and LangGraph when you already run voice).
Know if your voice agent is actually working. Install the sidecar, call configure() once, and Parlot models each call as turns: timeline, multi-agent handoff graph, pipeline waterfall, and goal completion with an evidence trail to the proving turns and audio.
Works with LiveKit Cloud, self-hosted media, and LiveKit on Telnyx.
Install
# LiveKit Agents (recommended)
pip install "parlot[livekit]"
# LangGraph / LangChain (same debugger for text agents alongside voice)
pip install "parlot[langgraph]"
# Both
pip install "parlot[all]"
Or install an instrumentation package directly:
pip install parlot-instrumentation-livekit
# or
pip install parlot-instrumentation-langgraph
Instrument (LiveKit)
from parlot.instrumentation.livekit import configure
configure()
Call configure() before constructing AgentSession, then await ctx.connect() before session.start(). Set PARLOT_ENDPOINT and PARLOT_API_KEY (mint in Settings → API Keys).
Full checklist: LiveKit guide · Quick Start
Documentation
1 maintainer
Metadata
1 maintainer
Release files for parlot 0.1.1
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 | |
|---|---|---|---|---|
| parlot-0.1.1.tar.gz | 2.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| parlot-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.6 kB
Release files / parlot-0.1.1.tar.gz
| Download URL | parlot-0.1.1.tar.gz |
|---|---|
| Size | 2.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
179277990eafec703027e40f1a6c3ef7690d790cedf870077791e335fd8df3a3
|
|
BLAKE2b-256 checksum How to use checksums |
ae68e380e0af208927e573e6f723c8b17056141140b9f9494b106dee8b8eb964
|
| 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 Aug 26, 2026.
Transparency logRelease files / parlot-0.1.1-py3-none-any.whl
| Download URL | parlot-0.1.1-py3-none-any.whl |
|---|---|
| Size | 2.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9ee5c82312764f1a63603df62bf0f9a713c2b3fe5d35917df0981214697de4b1
|
|
BLAKE2b-256 checksum How to use checksums |
11b1844e59344e2806ba700312b90b557a63a42f248ae5a6a3c2697d4094b9bd
|
| 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 Aug 26, 2026.
Transparency logSecurity for parlot 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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for parlot-0.1.1.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 Aug 26, 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.
