Pipecat Cloud
Python module and CLI for interacting with Pipecat Cloud.
Requirements
- Python 3.11+
- Docker and a Docker repository (e.g. Docker Hub)
- Active Pipecat Cloud account
Documentation
Documentation for Pipecat Cloud is available here.
Installation
The Pipecat Cloud CLI ships as part of the Pipecat CLI — its commands are available under pipecat cloud. Install the Pipecat CLI:
uv tool install pipecat-ai-cli
pipecat cloud --help
pipecat cloud auth login
! All CLI commands have a --help flag that will display the command usage and options.
To use Pipecat Cloud programmatically (without the CLI), install the package directly with uv add pipecatcloud and see Usage in Python scripts.
Usage
-
Create an account at Pipecat Cloud
-
Login to your account
pipecat cloud auth login -
Generate secrets
pipecat cloud secrets set -
Build and deploy your agent
pipecat cloud deploy
Seeing your secret keys
pipecat cloud secrets keys --region <region> shows your organization's secret keys in a region: each key's fingerprint, state, created and retired times, and how many secrets it holds. The fingerprint is the one a security notice names and, in a self-hosted region, the one your cluster shows for the key, so you can compare them. Add --output json before secrets for a single JSON document. Key material is never shown.
Usage in Python scripts
If want to programmatically start an agent within a Python script, you can use the pipecatcloud.session module.
from pipecatcloud.session import Session
from pipecatcloud.exception import AgentStartError
import asyncio
async def main():
session = Session(
agent_name="your-agent-name",
api_key="pk_...",
)
try:
await session.start()
except AgentStartError as e:
print(e)
except Exception as e:
raise (e)
if __name__ == "__main__":
asyncio.run(main())
Troubleshooting
SSL certificate errors on macOS
If pipecat cloud auth login fails with an SSL certificate verification error, your Python
installation may not have access to the macOS system certificate store. This is
common with Python installed via pyenv, conda, or the python.org installer.
To diagnose:
import ssl, sys, os
print(ssl.get_default_verify_paths())
print(os.path.realpath(sys.executable))
To fix, install certifi and point Python to its certificates:
pip install certifi
export SSL_CERT_FILE=$(python -c "import certifi; print(certifi.where())")
For the python.org installer, you can also run the bundled
Install Certificates.command script found in /Applications/Python X.Y/.
🛠️ Contributing
Setup Steps
-
Clone the repository and navigate to it:
git clone https://github.com/daily-co/pipecat-cloud.git cd pipecat-cloud
-
Install development and testing dependencies:
uv sync --group dev
-
Install the git pre-commit hooks:
uv run pre-commit install
Running tests
To run all tests, from the root directory:
uv run pytest
Run a specific test suite:
uv run pytest tests/test_name.py
Metadata
Release files for pipecatcloud 1.6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pipecatcloud-1.6.0.tar.gz | 432.0 kB | With provenance | Details for pipecatcloud-1.6.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pipecatcloud-1.6.0-py3-none-any.whl | Python 3 | none | any | Details for pipecatcloud-1.6.0-py3-none-any.whl |
Total release size: 576.3 kB
Release files / pipecatcloud-1.6.0.tar.gz
| Download URL | pipecatcloud-1.6.0.tar.gz |
|---|---|
| Size | 432.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cf349f5c502b84663f135e10dd999e84a92fa3baa19cecf38ec47b435d9ab17a
|
|
BLAKE2b-256 checksum How to use checksums |
d77381db740007a4f149210cfe124d335a239169b6dd708e610244c04087654b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logRelease files / pipecatcloud-1.6.0-py3-none-any.whl
| Download URL | pipecatcloud-1.6.0-py3-none-any.whl |
|---|---|
| Size | 144.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ad630465a602b7fbbd9aa4e9f271ffeb5495debfc3924aafeb0518a3f2849e19
|
|
BLAKE2b-256 checksum How to use checksums |
3a215c29450b8103b448082dfbe0a2388721f415720e2917d0b208bb5674bb8d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logSecurity for pipecatcloud 1.6.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for pipecatcloud-1.6.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 12, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.