v2.0.2 — install-path guardrails and a corrected Getting Started example

Unofficial, community-maintained SDK for Venice.ai. Not affiliated with or endorsed by Venice AI.
Requires Python 3.13+.

pip install --upgrade 'venice-ai>=2'

Documentation and packaging fixes. No API changes.

Fixed

The first code example on the documentation site raised TypeError. The Getting
Started sample constructed a message positionally — UserMessage("Hello, Venice!") —
which Pydantic rejects, since the message models are keyword-only. It now reads
UserMessage(content="Hello, Venice!").

Getting Started gave an installation sequence that could not work. The Claude Code
skills section told readers to run venice skills install after a plain
pip install venice-ai. The venice CLI ships behind the optional [cli] extra, so
that sequence failed on the install command.

Changed

Documented install commands now carry a >=2 floor, and are quoted. On Python 3.12
and below, a bare pip install venice-ai resolves to v1.3.x silently — pip backtracks
to the newest release whose Requires-Python matches, with no warning — so anyone
following v2 documentation on an older interpreter installed v1 and hit confusing import
errors far from the cause. pip install 'venice-ai>=2' produces an explicit failure
naming the reason instead:

$ pip install 'venice-ai>=2'
ERROR: Ignored the following versions that require a different python version:
       2.0.2 Requires-Python <4.0,>=3.13
ERROR: No matching distribution found for venice-ai>=2

The specifiers are also quoted throughout, because [...] is a glob in zsh — the macOS
default shell — where an unquoted pip install venice-ai[cli] fails with
no matches found. This applies to the runtime error hints and docstrings as well.

Requires-Python metadata is unchanged and remains honest. To stay on v1, pin
venice-ai<2.

The migration guide now covers dependency files. A >=2 floor only helps someone
who copies an install command; a bare venice-ai in requirements.txt or
pyproject.toml still resolves to v1.3.x silently on an older interpreter. That is the
common way to land back on v1 when adding the dependency to a project rather than typing
an install.

The Python 3.13 requirement is stated at the point of installation rather than
several hundred lines below it.

Links

Documentation ·
Migration Guide ·
CHANGELOG ·
Full diff