Python

pip install "hanzoai>=8"

Python 3.12 or newer. The >=8 is load-bearing: without it, pip on 3.9 to 3.11 resolves hanzoai to the 2.1 line, which has no hanzoai.cloud, and says nothing. With it, pip refuses rather than install a different client.

That is the client for every /v1 capability, generated from the API's own document. It exposes exactly one thing:

import hanzoai
hanzoai.cloud          # the client. Nothing else is re-exported at the top level.

Set the key once:

export HANZO_API_KEY="sk-..."   # from platform.hanzo.ai

The shape

One Configuration, one ApiClient, and one class per product:

import os
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import AiApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))

models = AiApi(client).get_models()

The class is the product and the method is the operation, so the reference is the index — each operation page prints this call beside the raw HTTP.

Chat completions

Use the openai client, pointed at Hanzo:

import os
from openai import OpenAI

client = OpenAI(
    api_key=os.environ["HANZO_API_KEY"],
    base_url="https://api.hanzo.ai/v1",
)

answer = client.chat.completions.create(
    model="zen6",
    messages=[{"role": "user", "content": "Explain quantum computing"}],
)
print(answer.choices[0].message.content)

This is the recommendation rather than a workaround, and it is worth saying why. api.hanzo.ai/v1 speaks the OpenAI and Anthropic wire formats on purpose, so streaming, tool calls and every helper that library already carries keep working — the edit is the base URL and the key, which is all Migrate from OpenAI asks for. Meanwhile hanzoai is generated from the document, and the document states the chat route's address without stating its body schema: AiApi.post_chat_completions() therefore takes no request body and decodes no response. A generated client cannot invent a shape nobody wrote down. Reach for hanzoai for the rest of /v1, which the OpenAI client does not describe at all.

The other distributions

The hanzo command is the native CLI, installed with curl -fsSL https://hanzo.sh | sh, not a Python package. hanzo on PyPI is the older Python CLI, installed as hanzo-py so the two never share a name on a PATH. The agent and tool packages are their own distributions, and pip install "hanzo[all]" is the convenience that pulls them:

Resources

• hanzoai on PyPI · hanzo on PyPI
• Source — hanzoai/python-sdk · hanzo-py
• Every /v1 operation →