Skip to main content

ChronicleLabs Python Library

fern shield pypi

The ChronicleLabs Python library provides convenient access to the ChronicleLabs APIs from Python.

Table of Contents

Installation

pip install chroniclelabs

Reference

A full reference for this library is available here.

Usage

Instantiate and use the client with the following:

from chroniclelabs import Chronicle

client = Chronicle(
    token="<token>",
)

client.events.ingest_event(
    source="my-agent",
    topic="conversations",
    event_type="message.sent",
)

Environments

This SDK allows you to configure different environments for API requests.

from chroniclelabs import Chronicle
from chroniclelabs.environment import ChronicleEnvironment

client = Chronicle(
    environment=ChronicleEnvironment.PRODUCTION,
)

Async Client

The SDK also exports an async client so that you can make non-blocking calls to our API. Note that if you are constructing an Async httpx client class to pass into this client, use httpx.AsyncClient() instead of httpx.Client() (e.g. for the httpx_client parameter of this client).

import asyncio

from chroniclelabs import AsyncChronicle

client = AsyncChronicle(
    token="<token>",
)


async def main() -> None:
    await client.events.ingest_event(
        source="my-agent",
        topic="conversations",
        event_type="message.sent",
    )


asyncio.run(main())

Exception Handling

When the API returns a non-success status code (4xx or 5xx response), a subclass of the following error will be thrown.

from chroniclelabs.core.api_error import ApiError

try:
    client.events.ingest_event(...)
except ApiError as e:
    print(e.status_code)
    print(e.body)

Streaming

The SDK supports streaming responses, as well, the response will be a generator that you can loop over.

from chroniclelabs import Chronicle

client = Chronicle(
    token="<token>",
)

client.events.stream_events()

Advanced

Access Raw Response Data

The SDK provides access to raw response data, including headers, through the .with_raw_response property. The .with_raw_response property returns a "raw" client that can be used to access the .headers and .data attributes.

from chroniclelabs import Chronicle

client = Chronicle(...)
response = client.events.with_raw_response.ingest_event(...)
print(response.headers)  # access the response headers
print(response.status_code)  # access the response status code
print(response.data)  # access the underlying object

Retries

The SDK is instrumented with automatic retries with exponential backoff. A request will be retried as long as the request is deemed retryable and the number of retry attempts has not grown larger than the configured retry limit (default: 2).

Which status codes are retried depends on the retryStatusCodes generator configuration:

legacy (current default): retries on

  • 408 (Timeout)
  • 409 (Conflict)
  • 429 (Too Many Requests)
  • 5XX (All server errors, including 500)

recommended: retries on

  • 408 (Timeout)
  • 409 (Conflict)
  • 429 (Too Many Requests)
  • 502 (Bad Gateway)
  • 503 (Service Unavailable)
  • 504 (Gateway Timeout)

Use the max_retries request option to configure this behavior.

client.events.ingest_event(..., request_options={
    "max_retries": 1
})

Timeouts

The SDK defaults to a 60 second timeout. You can configure this with a timeout option at the client or request level.

from chroniclelabs import Chronicle

client = Chronicle(..., timeout=20.0)

# Override timeout for a specific method
client.events.ingest_event(..., request_options={
    "timeout": 1
})

Custom Client

You can override the httpx client to customize it for your use-case. Some common use-cases include support for proxies and transports.

import httpx
from chroniclelabs import Chronicle

client = Chronicle(
    ...,
    httpx_client=httpx.Client(
        proxy="http://my.test.proxy.example.com",
        transport=httpx.HTTPTransport(local_address="0.0.0.0"),
    ),
)

Contributing

While we value open-source contributions to this SDK, this library is generated programmatically. Additions made directly to this library would have to be moved over to our generation code, otherwise they would be overwritten upon the next generated release. Feel free to open a PR as a proof of concept, but know that we will not be able to merge it as-is. We suggest opening an issue first to discuss with us!

On the other hand, contributions to the README are always very welcome!

Release files for chroniclelabs 0.0.8

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

Source distribution (sdist)

Source distribution for chroniclelabs 0.0.8
File Size Uploaded
chroniclelabs-0.0.8.tar.gz 56.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for chroniclelabs 0.0.8
File Interpreter ABI Platform
chroniclelabs-0.0.8-py3-none-any.whl Python 3 none any Details

Total release size: 149.4 kB

Release files / chroniclelabs-0.0.8.tar.gz

Download URL chroniclelabs-0.0.8.tar.gz
Size 56.9 kB
Tags Source
SHA-256 checksum
How to use checksums
955c946f82b5a0f59833993408ffa8d0094522c87c242cf54212d4886c4c0d99
BLAKE2b-256 checksum
How to use checksums
c6a411d614dde28f1fb2c44030d0d8eba5f32253b8ef8068ddb999409121781e
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 15, 2026.

Transparency log

Release files / chroniclelabs-0.0.8-py3-none-any.whl

Download URL chroniclelabs-0.0.8-py3-none-any.whl
Size 92.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d0431cf9ecd901aa3246099297cc2e283ee4f235bbcbebcc68d13f5cf97e9d3b
BLAKE2b-256 checksum
How to use checksums
afc0b32dba3926a61253341824b9ae237ea401c8277ddce8112c3a0b166769ac
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 15, 2026.

Transparency log

Release history Release notifications | RSS feed

0.0.11

2 release files

0.0.10

2 release files

0.0.9

2 release files

This release

0.0.8 This release

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