Pipecat Cloud Media over QUIC

​

Requirements

• pipecat-ai[moq] 1.13.0 or newer.
• The Pipecat Cloud base image dailyco/pipecat-base 0.2.7 or newer. Name the version in your Dockerfile’s FROM rather than relying on latest: a cloud build can get the previous base image for up to a day after a release.
• pipecatcloud 1.3.0 or newer, if your image installs its own rather than using the one the base image provides.

​

Bot code

pipecat-ai[moq]>=1.13.0

from pipecat.runner.types import RunnerArguments
from pipecat.runner.utils import create_transport
from pipecat.transports.moq.transport import MOQParams

transport_params = {
    "moq": lambda: MOQParams(
        audio_in_enabled=True,
        audio_out_enabled=True,
    ),
}


async def bot(runner_args: RunnerArguments):
    transport = await create_transport(runner_args, transport_params)
    # Build and run your pipeline with `transport`, as with any other transport.

​

Starting a session

curl -X POST "https://api.pipecat.daily.co/v1/public/my-agent/start" \
  -H "Authorization: Bearer pk_your_public_key" \
  -H "Content-Type: application/json" \
  -d '{"transport": "moq", "body": {"greeting": "hello"}}'

{
  "sessionId": "639f91d8-d511-4677-a83b-bd7564d5d92f",
  "moq": {
    "relayUrl": "https://us-west.moq.pipecat.daily.co/?jwt=eyJhbGciOiJFUzI1NiIs...",
    "certHash": null,
    "namespace": "pcc/639f91d8-d511-4677-a83b-bd7564d5d92f",
    "clientId": "request",
    "botId": "response",
    "transcriptTrack": "transcript.json.z"
  }
}

• relayUrl reaches the MoQ relays in your agent’s region, with the browser’s credential for this session in its query string. Treat it as a secret. It stays valid for the agent’s maximum session duration.
• certHash is null: the relays use publicly trusted certificates, so there is nothing to pin.
• namespace, clientId and botId place the browser and the bot in the session: the browser publishes under <namespace>/<clientId> and subscribes to <namespace>/<botId>, and the bot the reverse.

​

Connecting from the browser

import { PipecatClient } from "@pipecat-ai/client-js";
import { MoqTransport } from "@pipecat-ai/moq-transport";

const client = new PipecatClient({
  // relayUrl is required by the type; the /start response replaces it
  transport: new MoqTransport({ relayUrl: "" }),
});

await client.startBotAndConnect({
  endpoint: "https://api.pipecat.daily.co/v1/public/my-agent/start",
  headers: new Headers({ Authorization: "Bearer pk_your_public_key" }),
  requestData: { transport: "moq", body: { greeting: "hello" } },
});

​

Reconnects

​

Errors

• The agent’s latest deployment hasn’t finished reporting what it can serve. This can take a few minutes after a deploy; retry with backoff.
• A new deployment is still rolling out, or the latest one failed while the previous one keeps serving. Retry once a deployment has completed.

• The agent’s current deployment can’t serve MoQ: for example, its image is older than pipecat-base 0.2.7, its pipecat-ai is older than 1.13.0, or the moq extra isn’t installed. Rebuild on the requirements above and deploy again.
• The request also sets createDailyRoom or enableDefaultIceServers to true.
• MoQ isn’t offered in the agent’s region. Deploy the agent to a Daily-hosted region.

​

Related