Skip to main content
want livekit just for transport (WebRTC rooms, web and mobile SDKs, telephony) but pipecat to run the pipeline? pipecat ships a livekit transport, so the whole agent is one pipecat pipeline that sends and receives audio over a livekit room. no glue code needed.

which livekit setup is this?

this guide is the second row: livekit is transport only.

what you’ll build

one pipecat pipeline, with the livekit transport at both ends: livekit transport.input() → STT → LLM → rumik TTS → livekit transport.output()

before you start

  • python 3.10+
  • a livekit project (URL, API key, secret)
  • a rumik key
  • an STT and LLM (this guide uses deepgram + openai, both swappable)

step 1 · install

the livekit extra adds pipecat’s transport; pipecat-rumik is the voice.

step 2 · keys

.env

step 3 · build the pipeline

the transport is the only livekit-specific line. the rest is plain pipecat with RumikTTSService as the voice.
agent.py
the transport import path and runner API track your pipecat version, see the pipecat docs. RumikTTSService is the same as the pipecat integration reference.

step 4 · connect a caller

mint a livekit token per participant (see livekit’s token docs), start run_agent in the room, and join from your client or the agents playground. once both are in the room you talk to the bot, pipecat handles turn-taking over livekit’s WebRTC.

next steps