A previous release had provenance metadata, but this release does not. View details.
Parlot
Parlot shows whether production voice agents actually work — turns, handoffs, and goal completion with an evidence trail — not just that the pipeline returned 200s.
Call parlotize() once at startup. MIT OpenTelemetry instrumentation for LiveKit Agents (and LangGraph when you already run voice).
Docs: parlot.ai/docs · Product: parlot.ai
Install
pip install "parlot[livekit]"
# or: pip install "parlot[langgraph]"
# or: pip install "parlot[all]"
Or install an instrumentation package directly:
pip install parlot-instrumentation-livekit
# or: pip install parlot-instrumentation-langgraph
Instrument (LiveKit)
Call parlotize("…") before constructing AgentSession, then await ctx.connect() before session.start():
from parlot.instrumentation.livekit import parlotize
parlotize("my-agent")
from livekit.agents import AgentSession, JobContext
async def entrypoint(ctx: JobContext):
await ctx.connect()
session = AgentSession(...)
await session.start(agent=..., room=ctx.room)
Configure
export PARLOT_ENDPOINT=https://ingest.parlot.ai
export PARLOT_API_KEY=<org-scoped-key>
Mint the API key in Parlot Settings → API Keys.
Next
Metadata
Release files for parlot 0.3.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Loss of provenance
These files do not have provenance metadata, despite files in a prior release including this data.
We recommend further investigation before installing these files. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| parlot-0.3.2.tar.gz | 2.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| parlot-0.3.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.6 kB
Release files / parlot-0.3.2.tar.gz
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | parlot-0.3.2.tar.gz |
|---|---|
| Size | 2.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cc96dab58f10c2e51dd76644046a08925decc82ea529d51b89eb70df8226bbba
|
|
BLAKE2b-256 checksum How to use checksums |
32259b01b7f9cb6ba7298fd8dcf5fd54b59232de547488b2256a138c0b395f9e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.13
|
Release files / parlot-0.3.2-py3-none-any.whl
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | parlot-0.3.2-py3-none-any.whl |
|---|---|
| Size | 2.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d7021affd5c29c1308c81dac278091fcb4a389e701b64e42791e11025ae322e8
|
|
BLAKE2b-256 checksum How to use checksums |
59a0635539155cd26ba2d64520f522779a69e72013248a47eeac276be44f63c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.13
|
Security for parlot 0.3.2
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.
Loss of provenance
A previous release of these files had provenance metadata, but this release does not.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Release comparison
- Removed 0.3.1 2 files With provenance
- Added 0.3.2 2 files Without provenance
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.