Krutrim Core Infrastructure & Sandbox Python SDK (krutrim-client)

The Python SDK for Krutrim Cloud Core Infrastructure — VPCs, VMs, volumes, SSH keys, security groups, floating IPs, AI Pods — and Sandbox.

Note: Looking for model inference, image generation, speech, or fine-tuning? Those are AI Studio APIs and live in a different SDK, krutrim-cloud. See Which Python SDK should I use? below.

Which Python SDK should I use?

The two packages are separate, actively maintained SDKs for different Krutrim Cloud products, and they can be installed side by side. Neither replaces the other.

This package (krutrim-client) is the only Python SDK with Sandbox support.

Terms of Use

By downloading or using this SDK, you agree to the terms as mentioned in Krutrim SDK License.

Documentation

The full API of this library can be found in api_examples.ipynb.

Requirements

Python >=3.9

Supported regions

All regional services support both In-Bangalore-1 and In-Hyderabad-1.

Installation

pip install krutrim-client

Getting Started

See examples/getting-started.md for an end-to-end workflow covering:

• Authentication
• VPC Creation
• SSH Keys
• VM Provisioning
• VM Access

Usage

The full API of this library can be found in api_examples.ipynb.

import os
from krutrim_client import KrutrimClient

client = KrutrimClient(
    api_key=os.environ.get("KRUTRIMCLIENT_API_KEY"),  # This is the default and can be omitted
)

success_response = client.highlvlvpc.create_vpc(
    k_customer_id="k-customer-id",
    x_account_id="acc-1234567890",
)
print(success_response.task_id)

While you can provide an api_key keyword argument, we recommend using python-dotenv to add KRUTRIMCLIENT_API_KEY="My API Key" to your .env file. Create a key at the Krutrim Cloud console under Administration → API keys → Create API Key; one key covers Sandbox, MCP, Models, CLI and the SDK so that your API Key is not stored in source control.

Async usage

Simply import AsyncKrutrimClient instead of KrutrimClient and use await with each API call:

import os
import asyncio
from krutrim_client import AsyncKrutrimClient

client = AsyncKrutrimClient(
    api_key=os.environ.get("KRUTRIMCLIENT_API_KEY"),  # This is the default and can be omitted
)


async def main() -> None:
    success_response = await client.highlvlvpc.create_vpc(
        k_customer_id="k-customer-id",
        x_account_id="acc-1234567890",
    )
    print(success_response.task_id)


asyncio.run(main())

Functionality between the synchronous and asynchronous clients is otherwise identical.

Sandbox

The SDK includes an E2B-style, client-owned sandbox API with automatic readiness polling and context-manager cleanup:

from krutrim_client import KrutrimClient

with KrutrimClient() as client:
    with client.sandbox.create(
        flavor_name="sandbox-nano",
        region="In-Bangalore-1",
        timeout=900,
    ) as sandbox:
        sandbox.files.make_dir("/app/work")
        sandbox.files.write("/app/work/hello.py", 'print("hello")')
        result = sandbox.run_command("python3 hello.py", cwd="/app/work")
        print(result.stdout)

See the Sandbox guide for sync/async examples, timeout semantics, low-level API access, filesystem, port, proxy, retry, and cleanup behavior, and the Sandbox SDK reference for a description of all user-facing sandbox functions.

Custom Sandbox Runtime Images

Build a runtime image with your own dependencies and the sandbox agent. See the Custom Image Cookbook for an end-to-end walkthrough including:

• Building a linux/amd64 image with the Go agent (sandbox-agent) and custom Python dependencies
• Testing command execution and file operations locally
• Publishing to a public registry and verifying anonymous pull access
• Using image_uri with client.sandbox.create() in sync and async workflows

The image must include the agent's health, command, and file endpoints; an arbitrary application image is not sufficient. Managed creation waits for readiness, and context-manager exit requests sandbox deletion.

Using types

Nested request parameters are TypedDicts. Responses are Pydantic models which also provide helper methods for things like:

• Serializing back into JSON, model.to_json()
• Converting to a dictionary, model.to_dict()

Typed requests and responses provide autocomplete and documentation within your editor. If you would like to see type errors in VS Code to help catch bugs earlier, set python.analysis.typeCheckingMode to basic.

Nested params

Nested parameters are dictionaries, typed using TypedDict, for example:

from krutrim_client import KrutrimClient

client = KrutrimClient()

success_response = client.highlvlvpc.create_vpc(
    k_customer_id="k-customer-id",
    x_account_id="acc-1234567890",
    network={
        "admin_state_up": True,
        "name": "name",
    },
)
print(success_response.network)

Handling errors

When the library is unable to connect to the API (for example, due to network connection problems or a timeout), a subclass of krutrim_client.APIConnectionError is raised.

When the API returns a non-success status code (that is, 4xx or 5xx response), a subclass of krutrim_client.APIStatusError is raised, containing status_code and response properties.

All errors inherit from krutrim_client.APIError.

import krutrim_client
from krutrim_client import KrutrimClient

client = KrutrimClient()

try:
    client.highlvlvpc.create_vpc(
        k_customer_id="k-customer-id",
        x_account_id="acc-1234567890",
    )
except krutrim_client.APIConnectionError as e:
    print("The server could not be reached")
    print(e.__cause__)  # an underlying Exception, likely raised within httpx.
except krutrim_client.RateLimitError as e:
    print("A 429 status code was received; we should back off a bit.")
except krutrim_client.APIStatusError as e:
    print("Another non-200-range status code was received")
    print(e.status_code)
    print(e.response)

Error codes are as follows:

Retries

Certain errors are automatically retried 2 times by default, with a short exponential backoff. Connection errors (for example, due to a network connectivity problem), 408 Request Timeout, 409 Conflict, 429 Rate Limit, and >=500 Internal errors are all retried by default.

You can use the max_retries option to configure or disable retry settings:

from krutrim_client import KrutrimClient

# Configure the default for all requests:
client = KrutrimClient(
    # default is 2
    max_retries=0,
)

# Or, configure per-request:
client.with_options(max_retries=5).highlvlvpc.create_vpc(
    k_customer_id="k-customer-id",
    x_account_id="acc-1234567890",
)

Timeouts

By default requests time out after 1 minute. You can configure this with a timeout option, which accepts a float or an httpx.Timeout object:

from krutrim_client import KrutrimClient

# Configure the default for all requests:
client = KrutrimClient(
    # 20 seconds (default is 1 minute)
    timeout=20.0,
)

# More granular control:
client = KrutrimClient(
    timeout=httpx.Timeout(60.0, read=5.0, write=10.0, connect=2.0),
)

# Override per-request:
client.with_options(timeout=5.0).highlvlvpc.create_vpc(
    k_customer_id="k-customer-id",
    x_account_id="acc-1234567890",
)

On timeout, an APITimeoutError is thrown.

Note that requests that time out are retried twice by default.

Advanced

Logging

We use the standard library logging module.

You can enable logging by setting the environment variable krutrim_client_LOG to info.

$ export krutrim_client_LOG=info

Or to debug for more verbose logging.

How to tell whether None means null or missing

In an API response, a field may be explicitly null, or missing entirely; in either case, its value is None in this library. You can differentiate the two cases with .model_fields_set:

if response.my_field is None:
  if 'my_field' not in response.model_fields_set:
    print('Got json like {}, without a "my_field" key present at all.')
  else:
    print('Got json like {"my_field": null}.')

Accessing raw response data (e.g. headers)

The "raw" Response object can be accessed by prefixing .with_raw_response. to any HTTP method call, e.g.,

from krutrim_client import KrutrimClient

client = KrutrimClient()
response = client.highlvlvpc.with_raw_response.create_vpc(
    k_customer_id="k-customer-id",
    x_account_id="acc-1234567890",
)
print(response.headers.get('X-My-Header'))

highlvlvpc = response.parse()  # get the object that `highlvlvpc.create_vpc()` would have returned
print(highlvlvpc.task_id)

.with_streaming_response

The above interface eagerly reads the full response body when you make the request, which may not always be what you want.

To stream the response body, use .with_streaming_response instead, which requires a context manager and only reads the response body once you call .read(), .text(), .json(), .iter_bytes(), .iter_text(), .iter_lines() or .parse(). In the async client, these are async methods.

with client.highlvlvpc.with_streaming_response.create_vpc(
    k_customer_id="k-customer-id",
    x_account_id="acc-1234567890",
) as response:
    print(response.headers.get("X-My-Header"))

    for line in response.iter_lines():
        print(line)

The context manager is required so that the response will reliably be closed.

Making custom/undocumented requests

This library is typed for convenient access to the documented API.

If you need to access undocumented endpoints, params, or response properties, the library can still be used.

Undocumented endpoints

To make requests to undocumented endpoints, you can make requests using client.get, client.post, and other http verbs. Options on the client will be respected (such as retries) when making this request.

import httpx

response = client.post(
    "/foo",
    cast_to=httpx.Response,
    body={"my_param": True},
)

print(response.headers.get("x-foo"))

Undocumented request params

If you want to explicitly send an extra param, you can do so with the extra_query, extra_body, and extra_headers request options.

Undocumented response properties

To access undocumented response properties, you can access the extra fields like response.unknown_prop. You can also get all the extra fields on the Pydantic model as a dict with response.model_extra.

Configuring the HTTP client

You can directly override the httpx client to customize it for your use case, including:

• Support for proxies
• Custom transports
• Additional advanced functionality

import httpx
from krutrim_client import KrutrimClient, DefaultHttpxClient

client = KrutrimClient(
    # Or use the `krutrim_client_BASE_URL` env var
    base_url="http://my.test.server.example.com:8083",
    http_client=DefaultHttpxClient(
        proxy="http://my.test.proxy.example.com",
        transport=httpx.HTTPTransport(local_address="0.0.0.0"),
    ),
)

You can also customize the client on a per-request basis by using with_options():

client.with_options(http_client=DefaultHttpxClient(...))

Managing HTTP resources

By default the library closes underlying HTTP connections whenever the client is garbage collected. You can manually close the client using the .close() method if desired, or with a context manager that closes when exiting.

from krutrim_client import KrutrimClient

with KrutrimClient() as client:
  # make requests here
  ...

# HTTP client is now closed

Versioning

This package generally follows SemVer conventions, though certain backwards-incompatible changes may be released as minor versions:

1. Changes that only affect static types, without breaking runtime behavior.
2. Changes to library internals which are technically public but not intended or documented for external use. (Please open a GitHub issue to let us know if you are relying on such internals.)
3. Changes that we do not expect to impact the vast majority of users in practice.

We take backwards-compatibility seriously and work hard to ensure you can rely on a smooth upgrade experience.

Determining the installed version

If you've upgraded to the latest version but aren't seeing any new features you were expecting then your python environment is likely still using an older version.

You can determine the version that is being used at runtime with:

import krutrim_client
print(krutrim_client.__version__)

Requirements

Python 3.9 or higher.

Contributing

See the contributing documentation.