The Kernel Python library provides convenient access to the Kernel REST API from any Python 3.9+ application. The library includes type definitions for all request params and response fields, and offers both synchronous and asynchronous clients powered by httpx.

It is generated with Stainless.

The REST API documentation can be found on kernel.sh. The full API of this library can be found in api.md.

The full API of this library can be found in api.md.

While you can provide an api_key keyword argument, we recommend using python-dotenv to add KERNEL_API_KEY="My API Key" to your .env file so that your API Key is not stored in source control.

Simply import AsyncKernel instead of Kernel and use await with each API call:

Functionality between the synchronous and asynchronous clients is otherwise identical.

By default, the async client uses httpx for HTTP requests. However, for improved concurrency performance you may also use aiohttp as the HTTP backend.

You can enable this by installing aiohttp:

Then you can enable it by instantiating the client with http_client=DefaultAioHttpClient():

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.

List methods in the Kernel API are paginated.

This library provides auto-paginating iterators with each list response, so you do not have to request successive pages manually:

Or, asynchronously:

Alternatively, you can use the .has_next_page(), .next_page_info(), or .get_next_page() methods for more granular control working with pages:

Or just work directly with the returned data:

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

Request parameters that correspond to file uploads can be passed as bytes, or a PathLike instance or a tuple of (filename, contents, media type).

The async client uses the exact same interface. If you pass a PathLike instance, the file contents will be read asynchronously automatically.

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

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

All errors inherit from kernel.APIError.

Error codes are as follows:

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:

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:

On timeout, an APITimeoutError is thrown.

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

We use the standard library logging module.

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

Or to debug for more verbose logging.

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:

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

These methods return an APIResponse object.

The async client returns an AsyncAPIResponse with the same structure, the only difference being awaitable methods for reading the response content.

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.

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

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.

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.

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

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.

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

• Support for proxies
• Custom transports
• Additional advanced functionality

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

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.

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.

We are keen for your feedback; please open an issue with questions, bugs, or suggestions.

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:

Python 3.9 or higher.

See the contributing documentation.