Overview - Cekura

One package, two interfaces. pip install cekura ships both the CLI for terminal workflows and a Python SDK for programmatic access. Same auth, same API surface, same data.

When to use which

CLI

Best for one-off commands, shell scripts, CI pipelines, and quickly inspecting your workspace. Tab-complete, table output, JSON mode for piping.

Python SDK

Best for application code, custom automation, batch jobs, and integrating Cekura into existing Python workflows. Sync and async clients available.

Installation

Install the package with the extras you need:

Both (recommended)
CLI only
SDK only

pip install cekura

Includes both CLI and SDK plus integrations for LiveKit and Pipecat.

pip install "cekura[cli]"

The cekura command is now on your PATH. Verify:

cekura version

pip install "cekura[sdk]"

Import in Python:

from cekura import Cekura, AsyncCekura

Requirements: Python 3.9+. Linux, macOS, and Windows supported.

Authentication

The CLI and SDK accept either OAuth (browser sign-in) or an API key. OAuth is recommended for individual use.

OAuth (recommended)
API key

One-time browser sign-in. Tokens are stored locally and refreshed automatically.

cekura auth login

Verify:

cekura auth whoami

Sign out:

cekura auth logout

The same OAuth session is used by the SDK when no API key is set.

Generate a key in the dashboard under Settings → API Keys, then either store it via the CLI or set it in the environment.Via CLI (writes to the config file):

cekura auth login --api-key YOUR_API_KEY

Via environment variable (preferred for CI):

export CEKURA_API_KEY=YOUR_API_KEY

The SDK picks up CEKURA_API_KEY automatically when no key is passed:

from cekura import Cekura

# Reads CEKURA_API_KEY from env
client = Cekura()

# Or pass explicitly
client = Cekura(api_key="YOUR_API_KEY")

Configuration precedence

Both the CLI and SDK resolve configuration in this order (first match wins):

Explicit argument — Cekura(api_key=...) or --api-key flag
Environment variable — CEKURA_API_KEY, CEKURA_API_URL
Config file — ~/.cekura/config.toml (managed by cekura config set / cekura auth login)
Defaults — https://api.cekura.ai

Inspect the active config:

cekura config get        # all values
cekura config path       # config file location

On first sign-in (cekura auth login), the first organization and project the CLI sees on your account are saved as defaults automatically. You only need to override these when you want a different default — typically because you belong to multiple organizations or projects.

Next steps

CLI guide

Command groups, JSON output, scripting patterns, and common workflows.

Python SDK guide

Sync and async clients, resource map, and end-to-end examples.

API Reference

Full endpoint documentation for every resource the CLI and SDK expose.

Model Context Protocol

Use the same Cekura API surface from your AI assistant (Claude, Cursor, etc.).

CLI & SDK

Documentation Index

​When to use which

CLI

Python SDK

​Installation

​Authentication

​Configuration precedence

​Next steps

CLI guide

Python SDK guide

API Reference

Model Context Protocol

When to use which

Installation

Authentication

Configuration precedence

Next steps