> ## Documentation Index
> Fetch the complete documentation index at: https://docs.platform.decart.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Realtime Integration Paths

> Choose how to connect your platform to Decart's realtime AI models

Integrate Decart's realtime video AI models — Lucy Restyle Live and Lucy — into your platform and offer them to your users. Choose from multiple integration paths based on how much control you need over the end-user experience.

## Integration paths

Decart realtime models use **WebRTC** for media (video and audio) and a **control plane** for signaling, prompts, and session events. Each integration path differs in how you connect to the control plane — media quality is identical across all paths.

| Path                                                   | How it works                                        | White-label | Provider visibility | Client requirements | Your infrastructure  |
| ------------------------------------------------------ | --------------------------------------------------- | ----------- | ------------------- | ------------------- | -------------------- |
| [SDK Direct](/integrations/sdk-direct)                 | Your app embeds the Decart SDK                      | No          | Session events only | WebRTC + Decart SDK | Token minting only   |
| [WS Signaling Proxy](/integrations/signaling-proxy-ws) | You proxy WebSocket signaling, WebRTC stays direct  | Yes         | Full                | WebRTC (no SDK)     | WS proxy server      |
| [HTTP Signaling](/integrations/signaling-proxy-http)   | You proxy stateless HTTP calls, WebRTC stays direct | Yes         | Full                | WebRTC (no SDK)     | Stateless HTTP proxy |

## Choosing a path

**Do you need white-label?** If it's OK for your users to connect to Decart endpoints directly (visible in network traffic) and depend on the Decart SDK, use [SDK Direct](/integrations/sdk-direct) — it's the simplest path with zero infrastructure overhead.

**If you do need white-label**, choose based on your infrastructure: if your gateway is HTTP-native (most API platforms), use [HTTP Signaling](/integrations/signaling-proxy-http). If you already run WebSocket infrastructure, use [WS Signaling Proxy](/integrations/signaling-proxy-ws). Both deliver identical media quality.

## Authentication

All integration paths use the same authentication system. You receive a Decart API key for your platform and use it to authenticate requests on behalf of your users.

* **Permanent keys** are used server-side to authenticate with Decart
* **Client tokens** are short-lived keys for browser/mobile use — see [Client Tokens](/getting-started/client-tokens)
* Usage is tracked per API key, so you get full visibility into your users' consumption

<Info>
  Your API key is scoped to your platform. Decart tracks usage per key, so you can query consumption and build your own billing on top.
</Info>

## Next steps

<CardGroup cols={2}>
  <Card title="SDK Direct" icon="plug" href="/integrations/sdk-direct">
    Simplest path — embed the Decart SDK in your app
  </Card>

  <Card title="WS Signaling Proxy" icon="arrows-left-right" href="/integrations/signaling-proxy-ws">
    White-label with WebSocket proxy
  </Card>

  <Card title="HTTP Signaling" icon="globe" href="/integrations/signaling-proxy-http">
    White-label with stateless HTTP proxy
  </Card>
</CardGroup>