Omium Python SDK
Python SDK and CLI for the Omium platform: tracing, checkpoints, and workflow management. Use the HTTP/remote API with api.omium.ai for the hosted platform, or the CLI for local runs and project push.
Documentation: docs.omium.ai — install, configure, CLI reference, configuration.
Installation
From PyPI (recommended)
python -m pip install --upgrade pip
python -m pip install omium
The package is published via PyPI Trusted Publisher. Verify with omium --version.
From source (development)
cd omium-platform/sdk/python
pip install -e ".[dev]"
Quick start (platform)
-
Get an API key from app.omium.ai and configure the CLI:
omium init --api-key omium_xxx --api-url https://api.omium.ai
-
Initialize the SDK in your code (or run with
omium runso the CLI injects config):import omium omium.init(api_key="omium_xxx", project="my-agent")
-
Use decorators for tracing and checkpoints:
from omium import trace, checkpoint @trace("my_step") def my_step(data): return process(data) @checkpoint("important_step") async def important_step(data): return await do_work(data)
-
Run with the CLI to send traces to the platform:
omium run your_script.py --project my-agent
-
Push a project to see it on the Automations dashboard:
omium project init --name my-agent omium project push
Checkpoint API (advanced / local)
For direct checkpoint-manager access (e.g. local gRPC), use OmiumClient and the @checkpoint decorator or Checkpoint context manager:
from omium import OmiumClient, checkpoint, Checkpoint
client = OmiumClient(checkpoint_manager_url="localhost:7001")
await client.connect()
client.set_execution_context(execution_id="exec_123", agent_id="agent_1")
@checkpoint("validate_data", preconditions=["data is not None"])
async def validate_data(data: dict) -> dict:
return {"validated": True, "data": data}
async with Checkpoint("important_state", client=client) as cp:
result = await do_critical_thing()
cp.update_state(step="complete")
See the package docstrings and docs.omium.ai for full API details.
Configuration
- API URL: Use
https://api.omium.aifor the hosted platform. Override withOMIUM_API_URLoromium configure --api-url <url>. Do not add/api/v1to the base URL. - API key: Set via
omium init(stored in~/.omium/config.json) orOMIUM_API_KEY. - Project config: Use
omium.tomlin your project root; see docs.omium.ai.
Requirements
- Python >= 3.9 (3.11+ recommended)
- grpcio >= 1.69.0, < 2.0
- protobuf >= 5.26.1, < 6.0
Testing
pip install -e ".[dev]"
pytest tests/
pytest tests/ --cov=omium --cov-report=html
Publishing (maintainers)
Before deploying via GitHub Actions:
- Bump version in both places (must match or the workflow will fail):
pyproject.toml→version = "X.Y.Z"omium/__init__.py→__version__ = "X.Y.Z"
- Commit and push, then run Actions → Publish Omium Python SDK → Run workflow.
- The workflow runs tests, builds, and publishes to PyPI (skips if version already exists).
License
Proprietary - Omium Platform
Metadata
Release files for omium 0.4.3
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 |
|---|---|---|---|---|
| omium-0.4.3.tar.gz | 132.1 kB | With provenance | Details for omium-0.4.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| omium-0.4.3-py3-none-any.whl | Python 3 | none | any | Details for omium-0.4.3-py3-none-any.whl |
Total release size: 273.4 kB
Release files / omium-0.4.3.tar.gz
| Download URL | omium-0.4.3.tar.gz |
|---|---|
| Size | 132.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3299f52d103eb32deb0056ebce78b766a699c264a0768b83569769a3867a7451
|
|
BLAKE2b-256 checksum How to use checksums |
a425e360e45b4c2bd6dc98ad5b386bf178dee3417c76be39291bf43843a0166a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Jul 20, 2026.
Transparency logRelease files / omium-0.4.3-py3-none-any.whl
| Download URL | omium-0.4.3-py3-none-any.whl |
|---|---|
| Size | 141.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
11156fd696e7dfbb04d04bb8ba626f71ed4087d57e360a0d805684da3967a489
|
|
BLAKE2b-256 checksum How to use checksums |
057115fafa39aff30c072116ca1fec61c5a8f366bb22c994c71005ab43bb02ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
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 Jul 20, 2026.
Transparency logSecurity for omium 0.4.3
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for omium-0.4.3.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 Jul 20, 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.