Cloudglue Python SDK

Cloudglue makes it easy to turn video into LLM ready data. Official Python SDK for the Cloudglue API.

📖 Resources

• Cloudglue API Docs
• Terms of Service
• Privacy Policy
• Pricing

By using this SDK, you agree to the Cloudglue Terms of Service and acknowledge our Privacy Policy.

Installation

You can install the Cloudglue Python SDK using pip:

pip install cloudglue

Quick Start

fromcloudglueimportCloudglue# Initialize the clientclient=Cloudglue(api_key="your_api_key") # Or use CLOUDGLUE_API_KEY env variable# Define your messagesmessages= [
{"role": "user", "content": "What are aligned video captions?"}
]
# Make an API requestresponse=client.chat.completions.create(
messages=messages,
model="nimbus-001",
collections=["abc123"], # Assumes collection already exists, otherwise create one first then reference here by collection id 
)
# Get the generated textgenerated_text=response.choices[0].message.contentprint(generated_text)

Development

Prerequisites

• Python 3.10+
• Make (for build tasks)
• Git

Setup

Clone the repository and set up the development environment:

git clone https://github.com/cloudglue/cloudglue-python.git
cd cloudglue-python
brew install openapi-generator
make setup # This will set up the virtual environment# Initialize the API spec Git submodule
make submodule-init

API Specification

The OpenAPI specification is maintained in a separate repository and included as a Git submodule:

# Update the API spec to the latest version
make submodule-update
# After updating the spec, regenerate the SDK
make generate

Building

make generate # Generate SDK from OpenAPI spec
make build # Build the package

Releasing

Releases are published to PyPI automatically by the Publish to PyPI GitHub Actions workflow whenever a v* tag is pushed. It uses OIDC trusted publishing — no API tokens are stored anywhere.

To cut a release:

# 1. Bump the version in pyproject.toml (e.g. 0.7.15 -> 0.7.16) and commit it.# 2. Tag the commit. The tag MUST match the pyproject.toml version, prefixed# with "v" — the workflow fails fast if they differ.
git tag v0.7.16
git push origin v0.7.16

Pushing the tag triggers, in order:

1. build — verifies the tag matches pyproject.toml, builds the sdist + wheel, runs twine check.
2. publish — uploads the artifacts to PyPI via OIDC.
3. github-release — creates a GitHub Release for the tag with auto-generated notes and the .tar.gz + .whl attached.

One-time setup

This is already configured for the cloudglue project, but for reference the workflow depends on:

• A PyPI trusted publisher for repo cloudglue/cloudglue-python, workflow publish.yml, environment pypi.
• A GitHub Environment named pypi (repo Settings → Environments).

Manual publishing (fallback)

The legacy token-based path still works if you need to publish outside CI. It requires a PyPI API token scoped to the cloudglue project, in ~/.pypirc or via env vars:

make build
TWINE_USERNAME=__token__ TWINE_PASSWORD='pypi-...' make publish

Project Structure

Project directory structure described below:

cloudglue/
├── __init__.py # Main package initialization
├── client/ # Custom client wrapper code
│ └── main.py # Cloudglue class implementation └── sdk/ # Auto-generated API code
dist/ # Pre-built package dist
spec/ # Git submodule with OpenAPI specification
└── spec/ # Nested spec directory
└── openapi.json # OpenAPI spec file

Contact

• Open an Issue
• Email