LiveKit Plugins Spatius
Agent Framework plugin for Spatius avatars.
See the Spatius documentation for Spatius account setup and avatar configuration.
Client-side rendering
Spatius avatars are rendered on the client instead of being sent as conventional server-rendered video. The avatar's LiveKit video track carries motion data in otherwise black frames, so a standard LiveKit video renderer will display a black screen. Your frontend must use the Spatius client SDK and LiveKit adapter to decode the track and render the avatar.
See the client integration guide and the reference frontend for a working implementation.
Installation
pip install livekit-plugins-spatius
Usage
from livekit.plugins import spatius
avatar = spatius.AvatarSession()
await avatar.start(session, room=ctx.room)
The plugin reads SPATIUS_API_KEY, SPATIUS_APP_ID, and SPATIUS_AVATAR_ID from the
environment when constructor arguments are omitted.
Warm-up
At session start, the Spatius SDK resolves the ingress region via the bootstrap API
(with the default region="auto") and exchanges the API key for a session token —
two sequential HTTPS round trips on the room-join critical path. Register the
plugin's prewarm function to move that work into process warm-up, before a job is
dispatched:
from livekit import agents
from livekit.plugins import spatius
def prewarm(proc: agents.JobProcess):
spatius.prewarm(proc)
if __name__ == "__main__":
agents.cli.run_app(
agents.WorkerOptions(entrypoint_fnc=entrypoint, prewarm_fnc=prewarm)
)
The spatius SDK caches the resolved region (5 minutes) and the prefetched session
token (until shortly before expiry) process-wide, so AvatarSession.start() in the
dispatched job reuses them and goes straight to the ingress WebSocket connect. It
also opens throwaway TLS connections to the console and ingress endpoints to prime
DNS and the shared TLS session cache. Warm-up is best-effort and never fails
process initialization; without it, everything resolves inline as before.
Session-token prefetch assumes the Spatius backend allows a token to back more than
one session; opt out with spatius.prewarm(proc, prefetch_session_token=False).
Metadata
Release files for livekit-plugins-spatius 1.8.4
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_spatius-1.8.4.tar.gz | 10.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| livekit_plugins_spatius-1.8.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.4 kB
Release files / livekit_plugins_spatius-1.8.4.tar.gz
| Download URL | livekit_plugins_spatius-1.8.4.tar.gz |
|---|---|
| Size | 10.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ac9b5f65c4304ea31175d9d78aadf3142fa096cecba0270357a21c69df5e724c
|
|
BLAKE2b-256 checksum How to use checksums |
cbb13e2d54dbd7281c31218ff90aa1c7fe8ef1e15d771d5240144558854509ba
|
| 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 1, 2026.
Transparency logRelease files / livekit_plugins_spatius-1.8.4-py3-none-any.whl
| Download URL | livekit_plugins_spatius-1.8.4-py3-none-any.whl |
|---|---|
| Size | 11.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
95b67be510601be3662c211515511f335c0767dc02e8f7bfea13eb1cdaa42e28
|
|
BLAKE2b-256 checksum How to use checksums |
4e38ca4a89b295b69df0c4ad65da1c0b290c97cc8362d8279148c85f19543e6d
|
| 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 1, 2026.
Transparency log
