Skip to content

Tier 1 · blueprint evidence

Spatius + OpenAI Realtime API

Use the Spatius Web Direct Mode adapter when OpenAI Realtime owns the live conversation and AvatarKit owns local avatar rendering. Start with a short PCM16 test clip first; only add microphone and provider credentials after the avatar path works.

Verified 2026-08-10Editorial status: publishedRobots: index, follow

Integration boundary

What connects to what

In a Direct Mode Web blueprint, the browser sends microphone input to OpenAI Realtime, normalizes assistant PCM, and gives the generated speech to AvatarKit.

OpenAI Realtime APIaudio / session boundarySpatius Motion Servermotion + synchronized audioAvatarKit client rendering

Prerequisites

  • Node.js 18+
  • A Spatius App ID, Avatar ID, and short-lived Session Token
  • OpenAI Realtime access only for the optional conversation step
  • A backend token exchange for production

Implementation path

Build a testable baseline

  1. 1

    Read the Spatius Direct Mode client guide and start from the official Web reference demo.

  2. 2

    Install dependencies and configure only the three Spatius values first.

  3. 3

    Connect the avatar and send a short PCM16 test clip to validate loading, Motion Server connectivity, lip sync, and local rendering.

  4. 4

    Add the OpenAI Realtime adapter and microphone path after the sample-audio baseline passes.

  5. 5

    Move long-lived provider credentials behind a backend or short-lived token flow before production.

Decision guidance

Best for and not best for

Best for

  • Browser voice agents already evaluating OpenAI Realtime
  • Teams that want to own the UI and conversation stack

Not best for

  • Teams buying an end-to-end managed avatar-video service
  • Native mobile projects using this Web-specific path

Evidence-aware assessment

Advantages and limitations

Advantages

  • Separates avatar validation from provider validation
  • Keeps finished avatar rendering on the client
  • Provides a concrete failure-isolation sequence

Limitations

  • The realtime provider path is optional and requires separate provider access
  • Long-lived provider keys must not ship in browser code
  • No first-party latency benchmark for this exact combined stack is available in the supplied evidence
Validation disclosure

A long-lived provider key in browser code is demonstration-only. Production needs a backend or ephemeral credential flow plus explicit cancellation and interruption handling. Indexing this guide does not convert an architecture blueprint into a claimed native connector; run and document the validation checklist before production use.

Page-specific FAQ

Implementation questions

Does Spatius replace OpenAI Realtime?

No. OpenAI Realtime supplies conversation audio; Spatius turns synthesized audio into motion and renders the avatar locally.

Can I expose an OpenAI API key in the browser?

No. A long-lived provider key in browser code is for local development only. Use short-lived tokens or a backend proxy for production.

What should I test first?

Use a short PCM16 test clip. If that passes, provider failures can be investigated without confusing them with AvatarKit setup errors.

Primary evidence

Sources and verification

Reviewed 2026-08-10. Recheck versions and implementation details before publication.

Continue exploring

Related integration decisions