Choose Your Integration Path

​

Pick your category first

Spatius integrations come in two categories.

• Platform Integrations — you already use a third-party realtime / agent platform; Spatius slots in via a platform-specific package. Today: LiveKit Agents Integration and Agora Convo AI Integration.
• Standalone Integrations — you build directly with Spatius SDKs without going through a third-party agent platform. Today: Direct Mode and Backend Mode.

​

Decision matrix

​

LiveKit Agents Integration

LiveKit Agents Integration is the Platform Integration for LiveKit Agents. The livekit-plugins-spatius Python package attaches to your agent’s AgentSession and pipes agent audio to Motion Server. Use it when:

• Your backend runs a LiveKit Agents worker.
• You want LiveKit room transport handled for you.
• Your Web client renders avatar audio and motion from the LiveKit room.

​

Agora Convo AI Integration

Agora Convo AI Integration is the Platform Integration for Agora Convo AI. Convo AI is Agora’s managed conversational AI service; Spatius is configured as the Convo AI avatar provider in the start-agent request. If you run a TEN Framework graph directly, use the spatius_avatar_python TEN extension instead. Use it when:

• Your voice agent is built with Agora Convo AI.
• You want the Agora channel to carry user audio and avatar output.
• Your Web, iOS, or Android client renders avatar audio and motion from the Agora channel.

​

Direct Mode

Direct Mode maps to DrivingServiceMode.sdk in SDK code. It is the simplest Standalone Integration: your client app connects to Motion Server directly using a short-lived Session Token issued by your backend. Use it when:

• You already have avatar speech audio — your own TTS, a TTS provider, or prerecorded audio.
• You want Web, iOS, Android, or Flutter clients to own avatar playback.
• Your backend can host a minimal Session Token endpoint that calls the Console API.

​

Backend Mode

Backend Mode is the Standalone Integration for teams that need full control over the audio pipeline and downstream transport. Your backend uses a Spatius Server SDK to connect to Motion Server, then delivers encoded audio and motion messages to AvatarKit clients over a transport you choose. Use it when:

• Your backend owns ASR, LLM, TTS, turn-taking, and interruption policy.
• You need to tune latency or transport behavior.
• You need a custom WebSocket or RTC transport between your backend and clients.

​

Transport is a second decision

Transport options live inside an integration path, not as separate top-level choices: LiveKit appears in two completely different positions and these must not be confused:

• LiveKit Agents Integration uses LiveKit both as the agent framework (via livekit-plugins-spatius) and as the room transport. Choose this when you build agents on LiveKit Agents.
• Backend Mode with LiveKit uses your own backend with the Spatius Server SDK, and merely uses LiveKit as the downstream transport between your backend and your clients. No LiveKit Agents involved.

Agora has a similar distinction:

• Agora Convo AI Integration uses Agora Convo AI as the agent platform and an Agora channel as the transport. The Spatius integration is configured through the Convo AI avatar provider block, or through spatius_avatar_python when you run a TEN Framework graph directly.
• Backend Mode with Agora egress is a custom Server SDK pattern where your backend owns the whole pipeline and uses Agora only as the downstream transport. See Python SDK Agora Egress Mode.

​

Next steps