D-ID plugin for LiveKit Agents
Support for the D-ID virtual avatar.
See the D-ID integration docs for more information.
Installation
pip install livekit-plugins-did
Pre-requisites
You'll need an API key from D-ID. It can be set as an environment variable: DID_API_KEY
Supported avatars
This plugin only supports v4 avatars (type: expressive). Earlier avatar versions are not compatible. See the D-ID Create Agent API for details on creating a compatible agent.
Example — creating an expressive agent via the D-ID API:
curl -X POST https://api.d-id.com/agents \
-H "Authorization: Basic <YOUR_API_KEY>" \
-H "Content-Type: application/json" \
-d '{
"presenter": {
"type": "expressive",
"presenter_id": "public_mia_elegant@avt_TJ0Tq5"
},
"preview_name": "My Expressive Agent"
}'
Use the agent ID from the response as the agent_id parameter in the plugin.
1 maintainer
Metadata
1 maintainer
Release files for livekit-plugins-did 1.8.10
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_did-1.8.10.tar.gz | 6.0 kB | With provenance | Details for livekit_plugins_did-1.8.10.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| livekit_plugins_did-1.8.10-py3-none-any.whl | Python 3 | none | any | Details for livekit_plugins_did-1.8.10-py3-none-any.whl |
Total release size: 12.9 kB
Release files / livekit_plugins_did-1.8.10.tar.gz
| Download URL | livekit_plugins_did-1.8.10.tar.gz |
|---|---|
| Size | 6.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6f303c9df04085043e569e21d16788645b2af125570f4b7e8e693fe61b603da2
|
|
BLAKE2b-256 checksum How to use checksums |
d923975cdee11c528833d7eccb4a57fcce4c2c598b1e02204c2c841de0e57fa5
|
| 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 Oct 28, 2026.
Transparency logRelease files / livekit_plugins_did-1.8.10-py3-none-any.whl
| Download URL | livekit_plugins_did-1.8.10-py3-none-any.whl |
|---|---|
| Size | 6.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
948cc37316af96516e660295bf825680136c0c1e289b88e92b10c697f4c97ea6
|
|
BLAKE2b-256 checksum How to use checksums |
42ade3a78513673ffb36e66267b78ae8741185e9a62f8e30a491dae99275a3b9
|
| 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 Oct 28, 2026.
Transparency logSecurity for livekit-plugins-did 1.8.10
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 livekit_plugins_did-1.8.10.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 Oct 28, 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.
