Skip to main content

kc-sdk-python — Kvindo Cloud Python SDK

PyPI version Python versions License: MIT

Official Python SDK / client for the Kvindo Cloud API — manage cloud infrastructure as code from Python: VMs, volumes, S3 object storage, Kubernetes, load balancers, VPCs, VPNs, and managed PostgreSQL.

A thin, typed client over the REST API: one resource client per resource type, all sharing the same create / read / update / delete / list contract.

Using Claude Code? This repo ships a Claude Code skill that teaches Claude how to script Kvindo Cloud with this SDK — clone this repo (or otherwise have it on disk) and open Claude Code there to pick it up automatically.

Install

pip install kc-sdk-python

Dependencies: requests, marshmallow-dataclass, py-ulid.

Usage

from kc_api import KcClient

client = KcClient("YOUR_API_TOKEN")  # api_url defaults to https://cloud-api.kvindo.ru
# TLS certificate verification is on by default (verify_ssl=True). Pass
# verify_ssl=False only to point this SDK at a genuinely self-hosted instance
# with a self-signed cert.

# List (label-filtered, paginated)
resp = client.vms.get_by_labels({"env": "prod"}, max_page_size=50)
for vm in resp.resources:
    print(vm["metadata"]["name"])

# Read one
vm = client.vms.read("01H...")
print(vm.resource)

# Create / update (async) then wait for it to reconcile
created = client.vms.create_or_update({
    "metadata": {"name": "my-vm", "folderId": "01H..."},
    "spec": {"offerId": "g3-1c2-100", "state": "running", ...},
})
status = client.vms.wait_request_satisfied(created.requestId, timeout_seconds=300)
assert status.succeeded

# Delete (optionally block until reconciled)
client.vms.delete("01H...", wait=True)

Create / update / delete are asynchronous: they return a requestId; poll read_request(requestId) or use wait_request_satisfied(...). Every response object carries errorMessage / errorCode (a typed KcApi*ErrorCode) which are None on success.

Available resources

KcClient exposes one KcResourceClient per type, e.g. client.vms, client.volumes, client.s3_buckets, client.kubernetes, client.load_balancers, client.vpcs, client.postgresqls, client.folders, client.transactions, … (the surface mirrors the official Kvindo Cloud API).

Part of the Kvindo Cloud developer toolchain:

License

MIT

Metadata

Release files for kc-sdk-python 5.3.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for kc-sdk-python 5.3.2
File Size Uploaded
kc_sdk_python-5.3.2.tar.gz 16.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for kc-sdk-python 5.3.2
File Interpreter ABI Platform
kc_sdk_python-5.3.2-py3-none-any.whl Python 3 none any Details

Total release size: 31.6 kB

Release files / kc_sdk_python-5.3.2.tar.gz

Download URL kc_sdk_python-5.3.2.tar.gz
Size 16.6 kB
Tags Source
SHA-256 checksum
How to use checksums
2f92e2c128b33afb2d721c9ad10ad2869128327e705c6c3c337fe0dd24e19515
BLAKE2b-256 checksum
How to use checksums
02d92f74192f642fe8c2bbad6efc56681e244590fdbc37794f50bd7d45b721dd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.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 Sep 22, 2026.

Transparency log

Release files / kc_sdk_python-5.3.2-py3-none-any.whl

Download URL kc_sdk_python-5.3.2-py3-none-any.whl
Size 15.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f2fc1a22cb233a21c4458584d1ba88ab7b6330106198a37e01683adcd1cfb53e
BLAKE2b-256 checksum
How to use checksums
59bed752fc57fa0c3b6a6330c79ac35c017aa541ed1aa0b9a8cf6b3b1e03ef13
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.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 Sep 22, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

5.3.2 This release

2 release files

5.3.1

2 release files

5.3.0

2 release files

5.2.0

2 release files

5.1.0

2 release files

5.0.0

2 release files

4.3.0

2 release files

4.2.0

2 release files

4.1.0

2 release files

4.0.0

2 release files

3.1.0

2 release files

3.0.0

2 release files

2.0.0

2 release files

1.0.0

2 release files

0.2.0

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page