Overview
Pipecat is an open-source framework for building voice agents. Preclinical supports testing Pipecat agents deployed on Pipecat Cloud via WebRTC.Transport Options
Pipecat supports two transport modes:| Transport | Description | Use Case |
|---|---|---|
| Daily WebRTC | Default Pipecat Cloud transport | Standard Pipecat Cloud deployments |
| LiveKit WebRTC | Alternative using LiveKit SDK | When using LiveKit infrastructure |
Configuration (Daily WebRTC)
To add a Pipecat integration with Daily transport, you’ll need:| Field | Description |
|---|---|
| API Key | Pipecat Cloud API key |
| Agent ID | Pipecat agent ID |
Optional Settings
| Field | Description | Default |
|---|---|---|
| Timeout | Maximum test duration | 2 minutes |
| Metadata | Custom metadata to pass to agent | None |
Configuration (LiveKit Transport)
To use LiveKit transport instead, you’ll need:| Field | Description |
|---|---|
| LiveKit URL | Your LiveKit server URL (wss://…) |
| LiveKit API Key | LiveKit API key |
| LiveKit API Secret | LiveKit API secret |
| Agent Name | Name of the Pipecat agent |
Setup Steps (Daily WebRTC)
Deploy to Pipecat Cloud
Deploy your Pipecat agent to Pipecat Cloud
Setup Steps (LiveKit Transport)
Features
Multi-Transport
Support for Daily and LiveKit transports
Open Source
Test agents built with open-source Pipecat
Cloud Hosted
Easy integration with Pipecat Cloud
Metrics
Connection and conversation metrics
Metrics Captured
| Metric | Description |
|---|---|
| Connection time | Time to establish connection |
| Session ID | Pipecat session identifier |
| Turn count | Number of conversation turns |
| Total duration | Full conversation time |
Error Handling
Common Errors
| Error | Cause | Resolution |
|---|---|---|
| 401 Unauthorized | Invalid API key | Check Pipecat Cloud API key |
| 404 Not Found | Invalid agent ID | Verify agent is deployed |
| Connection timeout | Agent not responding | Check agent health |
| Transport error | WebRTC issues | Verify network connectivity |
Troubleshooting
Agent not responding
Agent not responding
- Verify agent is deployed on Pipecat Cloud
- Check agent logs in Pipecat Cloud dashboard
- Test agent manually via Pipecat playground
Connection issues (Daily)
Connection issues (Daily)
- Verify Pipecat Cloud API key
- Check agent ID is correct
- Ensure agent is running
Connection issues (LiveKit)
Connection issues (LiveKit)
- Verify LiveKit credentials
- Check agent is registered correctly
- See LiveKit troubleshooting
Choosing a Transport
| Factor | Daily WebRTC | LiveKit Transport |
|---|---|---|
| Setup complexity | Simpler | More setup required |
| Infrastructure | Pipecat Cloud managed | Self-managed or LiveKit Cloud |
| Existing LiveKit | N/A | Reuses existing setup |
| Flexibility | Standard | More control |