Metadata-Version: 2.4
Name: corebasehq
Version: 0.1.0
Summary: Official Python SDK for the CoreBase Developer API - OpenAI-compatible chat over your connected data, sources, agent runs, and widget session tokens.
Author: CoreBase
License: MIT
Project-URL: Homepage, https://corebasehq.com
Project-URL: Documentation, https://docs.corebasehq.com/api-reference/sdks
Project-URL: Repository, https://github.com/corebasehq/corebase-python
Requires-Python: >=3.10
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: httpcore>=1.0.9
Requires-Dist: httpx>=0.28.1
Requires-Dist: pydantic<2.13,>=2.11.2
Dynamic: license-file

# corebasehq

The official Python SDK for the [CoreBase](https://corebasehq.com) Developer API — chat over your connected data with OpenAI-compatible streaming, list sources, trigger governed agent runs, and sign widget session tokens.

[![Built by Speakeasy](https://img.shields.io/badge/Built_by-SPEAKEASY-374151?style=for-the-badge&labelColor=f3f4f6)](https://www.speakeasy.com/?utm_source=corebasehq&utm_campaign=python)
[![License: MIT](https://img.shields.io/badge/LICENSE_//_MIT-3b5bdb?style=for-the-badge&labelColor=eff6ff)](https://opensource.org/licenses/MIT)

<!-- Start Summary [summary] -->
## Summary

CoreBase Developer API: Build on CoreBase with a cb_live_ token.

Call CoreBase from your own apps with a `cb_live_` API token. The chat endpoint is OpenAI-compatible, so any OpenAI client works by pointing its base URL at this API. Create a token in the panel under API Tokens.

Authenticate every request with `Authorization: Bearer cb_live_...`. Responses are JSON, except the chat endpoint, which streams Server-Sent Events.
<!-- End Summary [summary] -->

<!-- Start Table of Contents [toc] -->
## Table of Contents
<!-- $toc-max-depth=2 -->
* [corebasehq](#corebasehq)
  * [SDK Installation](#sdk-installation)
  * [IDE Support](#ide-support)
  * [SDK Example Usage](#sdk-example-usage)
  * [Authentication](#authentication)
  * [Available Resources and Operations](#available-resources-and-operations)
  * [Retries](#retries)
  * [Error Handling](#error-handling)
  * [Server Selection](#server-selection)
  * [Custom HTTP Client](#custom-http-client)
  * [Resource Management](#resource-management)
  * [Debugging](#debugging)
* [Development](#development)
  * [Maturity](#maturity)
  * [Contributions](#contributions)

<!-- End Table of Contents [toc] -->

<!-- Start SDK Installation [installation] -->
## SDK Installation

> [!NOTE]
> **Python version upgrade policy**
>
> Once a Python version reaches its [official end of life date](https://devguide.python.org/versions/), a 3-month grace period is provided for users to upgrade. Following this grace period, the minimum python version supported in the SDK will be updated.

The SDK can be installed with *uv*, *pip*, or *poetry* package managers.

### uv

*uv* is a fast Python package installer and resolver, designed as a drop-in replacement for pip and pip-tools. It's recommended for its speed and modern Python tooling capabilities.

```bash
uv add corebasehq
```

### PIP

*PIP* is the default package installer for Python, enabling easy installation and management of packages from PyPI via the command line.

```bash
pip install corebasehq
```

### Poetry

*Poetry* is a modern tool that simplifies dependency management and package publishing by using a single `pyproject.toml` file to handle project metadata and dependencies.

```bash
poetry add corebasehq
```

### Shell and script usage with `uv`

You can use this SDK in a Python shell with [uv](https://docs.astral.sh/uv/) and the `uvx` command that comes with it like so:

```shell
uvx --from corebasehq python
```

It's also possible to write a standalone Python script without needing to set up a whole project like so:

```python
#!/usr/bin/env -S uv run --script
# /// script
# requires-python = ">=3.10"
# dependencies = [
#     "corebasehq",
# ]
# ///

from corebasehq import Corebase

sdk = Corebase(
  # SDK arguments
)

# Rest of script here...
```

Once that is saved to a file, you can run it with `uv run script.py` where
`script.py` can be replaced with the actual file name.
<!-- End SDK Installation [installation] -->

<!-- Start IDE Support [idesupport] -->
## IDE Support

### PyCharm

Generally, the SDK will work well with most IDEs out of the box. However, when using PyCharm, you can enjoy much better integration with Pydantic by installing an additional plugin.

- [PyCharm Pydantic Plugin](https://docs.pydantic.dev/latest/integrations/pycharm/)
<!-- End IDE Support [idesupport] -->

<!-- Start SDK Example Usage [usage] -->
## SDK Example Usage

### Example

```python
# Synchronous Example
from corebasehq import Corebase
import os


with Corebase(
    bearer_auth=os.getenv("COREBASE_BEARER_AUTH", ""),
) as corebase:

    res = corebase.chat.create_chat_completion(messages=[
        {"role": "user", "content": "Which invoices are overdue?"},
    ], stream=True)

    # Handle response
    print(res)
```

</br>

The same SDK client can also be used to make asynchronous requests by importing asyncio.

```python
# Asynchronous Example
import asyncio
from corebasehq import Corebase
import os

async def main():

    async with Corebase(
        bearer_auth=os.getenv("COREBASE_BEARER_AUTH", ""),
    ) as corebase:

        res = await corebase.chat.create_chat_completion_async(messages=[
            {"role": "user", "content": "Which invoices are overdue?"},
        ], stream=True)

        # Handle response
        print(res)

asyncio.run(main())
```
<!-- End SDK Example Usage [usage] -->

## Widget Session Tokens

Embedding the [CoreBase widget](https://docs.corebasehq.com/platform/widget) in your product? Sign each visitor's session token in one call — server side only, the secret never reaches a browser:

```python
import os
from corebasehq import create_widget_token

token = create_widget_token(
    os.environ["COREBASE_WIDGET_SECRET"],
    user.id,  # shows in audit logs as this end-user
    expires_in=1800,  # seconds; default 30 minutes
    source_ids=["orders", "invoices"],  # narrow within the widget's allowed sources
    daily_limit=50,  # per-end-user message caps
    per_minute_limit=5,
    claims={"branch": user.branch},  # extra claims for {{claim.branch}} headers
)
```

The helper always sets an expiry (CoreBase rejects tokens without one) and never lets a passthrough claim overwrite `sub` or `exp`. Standard library only — no extra dependencies.

<!-- Start Authentication [security] -->
## Authentication

### Per-Client Security Schemes

This SDK supports the following security scheme globally:

| Name          | Type | Scheme      | Environment Variable   |
| ------------- | ---- | ----------- | ---------------------- |
| `bearer_auth` | http | HTTP Bearer | `COREBASE_BEARER_AUTH` |

To authenticate with the API the `bearer_auth` parameter must be set when initializing the SDK client instance. For example:
```python
from corebasehq import Corebase
import os


with Corebase(
    bearer_auth=os.getenv("COREBASE_BEARER_AUTH", ""),
) as corebase:

    res = corebase.chat.create_chat_completion(messages=[
        {"role": "user", "content": "Which invoices are overdue?"},
    ], stream=True)

    # Handle response
    print(res)

```
<!-- End Authentication [security] -->

<!-- Start Available Resources and Operations [operations] -->
## Available Resources and Operations

<details open>
<summary>Available methods</summary>

### [Account](docs/sdks/account/README.md)

* [get_plan](docs/sdks/account/README.md#get_plan) - Get subscription plan
* [get_usage](docs/sdks/account/README.md#get_usage) - Get per-end-user widget usage
* [list_projects](docs/sdks/account/README.md#list_projects) - List projects

### [Agents](docs/sdks/agents/README.md)

* [list_agents](docs/sdks/agents/README.md#list_agents) - List agent flows
* [run_agent](docs/sdks/agents/README.md#run_agent) - Trigger an agent flow run
* [get_run](docs/sdks/agents/README.md#get_run) - Get agent run status
* [approve_run](docs/sdks/agents/README.md#approve_run) - Approve a paused agent run
* [reject_run](docs/sdks/agents/README.md#reject_run) - Reject a paused agent run

### [Chat](docs/sdks/chat/README.md)

* [create_chat_completion](docs/sdks/chat/README.md#create_chat_completion) - Create a chat completion

### [Sources](docs/sdks/sources/README.md)

* [list_sources](docs/sdks/sources/README.md#list_sources) - List data sources

</details>
<!-- End Available Resources and Operations [operations] -->

<!-- Start Retries [retries] -->
## Retries

Some of the endpoints in this SDK support retries. If you use the SDK without any configuration, it will fall back to the default retry strategy provided by the API. However, the default retry strategy can be overridden on a per-operation basis, or across the entire SDK.

To change the default retry strategy for a single API call, simply provide a `RetryConfig` object to the call:
```python
from corebasehq import Corebase
from corebasehq.utils import BackoffStrategy, RetryConfig
import os


with Corebase(
    bearer_auth=os.getenv("COREBASE_BEARER_AUTH", ""),
) as corebase:

    res = corebase.chat.create_chat_completion(messages=[], stream=True,
        RetryConfig("backoff", BackoffStrategy(1, 50, 1.1, 100), False))

    # Handle response
    print(res)

```

If you'd like to override the default retry strategy for all operations that support retries, you can use the `retry_config` optional parameter when initializing the SDK:
```python
from corebasehq import Corebase
from corebasehq.utils import BackoffStrategy, RetryConfig
import os


with Corebase(
    retry_config=RetryConfig("backoff", BackoffStrategy(1, 50, 1.1, 100), False),
    bearer_auth=os.getenv("COREBASE_BEARER_AUTH", ""),
) as corebase:

    res = corebase.chat.create_chat_completion(messages=[
        {"role": "user", "content": "Which invoices are overdue?"},
    ], stream=True)

    # Handle response
    print(res)

```
<!-- End Retries [retries] -->

<!-- Start Error Handling [errors] -->
## Error Handling

[`CorebaseError`](./src/corebasehq/errors/corebaseerror.py) is the base class for all HTTP error responses. It has the following properties:

| Property           | Type             | Description                                                                             |
| ------------------ | ---------------- | --------------------------------------------------------------------------------------- |
| `err.message`      | `str`            | Error message                                                                           |
| `err.status_code`  | `int`            | HTTP response status code eg `404`                                                      |
| `err.headers`      | `httpx.Headers`  | HTTP response headers                                                                   |
| `err.body`         | `str`            | HTTP body. Can be empty string if no body is returned.                                  |
| `err.raw_response` | `httpx.Response` | Raw HTTP response                                                                       |
| `err.data`         |                  | Optional. Some errors may contain structured data. [See Error Classes](#error-classes). |

### Example
```python
from corebasehq import Corebase, errors
import os


with Corebase(
    bearer_auth=os.getenv("COREBASE_BEARER_AUTH", ""),
) as corebase:
    res = None
    try:

        res = corebase.chat.create_chat_completion(messages=[
        {"role": "user", "content": "Which invoices are overdue?"},
    ], stream=True)

        # Handle response
        print(res)


    except errors.CorebaseError as e:
        # The base class for HTTP error responses
        print(e.message)
        print(e.status_code)
        print(e.body)
        print(e.headers)
        print(e.raw_response)

        # Depending on the method different errors may be thrown
        if isinstance(e, errors.HTTPValidationError):
            print(e.data.detail)  # Optional[List[models.ValidationError]]
```

### Error Classes
**Primary errors:**
* [`CorebaseError`](./src/corebasehq/errors/corebaseerror.py): The base class for HTTP error responses.
  * [`APIError`](./src/corebasehq/errors/apierror.py): A structured error. `detail` is a human-readable message, or an object carrying a stable `error` code plus context.
  * [`HTTPValidationError`](./src/corebasehq/errors/httpvalidationerror.py): Validation Error. Status code `422`.

<details><summary>Less common errors (5)</summary>

<br />

**Network errors:**
* [`httpx.RequestError`](https://www.python-httpx.org/exceptions/#httpx.RequestError): Base class for request errors.
    * [`httpx.ConnectError`](https://www.python-httpx.org/exceptions/#httpx.ConnectError): HTTP client was unable to make a request to a server.
    * [`httpx.TimeoutException`](https://www.python-httpx.org/exceptions/#httpx.TimeoutException): HTTP request timed out.


**Inherit from [`CorebaseError`](./src/corebasehq/errors/corebaseerror.py)**:
* [`ResponseValidationError`](./src/corebasehq/errors/responsevalidationerror.py): Type mismatch between the response data and the expected Pydantic model. Provides access to the Pydantic validation error via the `cause` attribute.

</details>
<!-- End Error Handling [errors] -->

<!-- Start Server Selection [server] -->
## Server Selection

### Override Server URL Per-Client

The default server can be overridden globally by passing a URL to the `server_url: str` optional parameter when initializing the SDK client instance. For example:
```python
from corebasehq import Corebase
import os


with Corebase(
    server_url="https://api.corebasehq.com",
    bearer_auth=os.getenv("COREBASE_BEARER_AUTH", ""),
) as corebase:

    res = corebase.chat.create_chat_completion(messages=[
        {"role": "user", "content": "Which invoices are overdue?"},
    ], stream=True)

    # Handle response
    print(res)

```
<!-- End Server Selection [server] -->

<!-- Start Custom HTTP Client [http-client] -->
## Custom HTTP Client

The Python SDK makes API calls using the [httpx](https://www.python-httpx.org/) HTTP library.  In order to provide a convenient way to configure timeouts, cookies, proxies, custom headers, and other low-level configuration, you can initialize the SDK client with your own HTTP client instance.
Depending on whether you are using the sync or async version of the SDK, you can pass an instance of `HttpClient` or `AsyncHttpClient` respectively, which are Protocol's ensuring that the client has the necessary methods to make API calls.
This allows you to wrap the client with your own custom logic, such as adding custom headers, logging, or error handling, or you can just pass an instance of `httpx.Client` or `httpx.AsyncClient` directly.

For example, you could specify a header for every request that this sdk makes as follows:
```python
from corebasehq import Corebase
import httpx

http_client = httpx.Client(headers={"x-custom-header": "someValue"})
s = Corebase(client=http_client)
```

or you could wrap the client with your own custom logic:
```python
from corebasehq import Corebase
from corebasehq.httpclient import AsyncHttpClient
import httpx

class CustomClient(AsyncHttpClient):
    client: AsyncHttpClient

    def __init__(self, client: AsyncHttpClient):
        self.client = client

    async def send(
        self,
        request: httpx.Request,
        *,
        stream: bool = False,
        auth: Union[
            httpx._types.AuthTypes, httpx._client.UseClientDefault, None
        ] = httpx.USE_CLIENT_DEFAULT,
        follow_redirects: Union[
            bool, httpx._client.UseClientDefault
        ] = httpx.USE_CLIENT_DEFAULT,
    ) -> httpx.Response:
        request.headers["Client-Level-Header"] = "added by client"

        return await self.client.send(
            request, stream=stream, auth=auth, follow_redirects=follow_redirects
        )

    def build_request(
        self,
        method: str,
        url: httpx._types.URLTypes,
        *,
        content: Optional[httpx._types.RequestContent] = None,
        data: Optional[httpx._types.RequestData] = None,
        files: Optional[httpx._types.RequestFiles] = None,
        json: Optional[Any] = None,
        params: Optional[httpx._types.QueryParamTypes] = None,
        headers: Optional[httpx._types.HeaderTypes] = None,
        cookies: Optional[httpx._types.CookieTypes] = None,
        timeout: Union[
            httpx._types.TimeoutTypes, httpx._client.UseClientDefault
        ] = httpx.USE_CLIENT_DEFAULT,
        extensions: Optional[httpx._types.RequestExtensions] = None,
    ) -> httpx.Request:
        return self.client.build_request(
            method,
            url,
            content=content,
            data=data,
            files=files,
            json=json,
            params=params,
            headers=headers,
            cookies=cookies,
            timeout=timeout,
            extensions=extensions,
        )

s = Corebase(async_client=CustomClient(httpx.AsyncClient()))
```
<!-- End Custom HTTP Client [http-client] -->

<!-- Start Resource Management [resource-management] -->
## Resource Management

The `Corebase` class implements the context manager protocol and registers a finalizer function to close the underlying sync and async HTTPX clients it uses under the hood. This will close HTTP connections, release memory and free up other resources held by the SDK. In short-lived Python programs and notebooks that make a few SDK method calls, resource management may not be a concern. However, in longer-lived programs, it is beneficial to create a single SDK instance via a [context manager][context-manager] and reuse it across the application.

[context-manager]: https://docs.python.org/3/reference/datamodel.html#context-managers

```python
from corebasehq import Corebase
import os
def main():

    with Corebase(
        bearer_auth=os.getenv("COREBASE_BEARER_AUTH", ""),
    ) as corebase:
        # Rest of application here...


# Or when using async:
async def amain():

    async with Corebase(
        bearer_auth=os.getenv("COREBASE_BEARER_AUTH", ""),
    ) as corebase:
        # Rest of application here...
```
<!-- End Resource Management [resource-management] -->

<!-- Start Debugging [debug] -->
## Debugging

You can setup your SDK to emit debug logs for SDK requests and responses.

You can pass your own logger class directly into your SDK.
```python
from corebasehq import Corebase
import logging

logging.basicConfig(level=logging.DEBUG)
s = Corebase(debug_logger=logging.getLogger("corebasehq"))
```

You can also enable a default debug logger by setting an environment variable `COREBASE_DEBUG` to true.
<!-- End Debugging [debug] -->

<!-- Placeholder for Future Speakeasy SDK Sections -->

# Development

## Maturity

This SDK is in beta, and there may be breaking changes between versions without a major version update. Therefore, we recommend pinning usage
to a specific package version. This way, you can install the same version each time without breaking changes unless you are intentionally
looking for the latest version.

## Contributions

While we value open-source contributions to this SDK, this library is generated programmatically. Any manual changes added to internal files will be overwritten on the next generation. 
We look forward to hearing your feedback. Feel free to open a PR or an issue with a proof of concept and we'll do our best to include it in a future release. 

### SDK Created by [Speakeasy](https://www.speakeasy.com/?utm_source=corebasehq&utm_campaign=python)
