ocai-anthropic
The Anthropic plugin distribution for ocai.
Distribution name: ocai-anthropic; pip install ocai[anthropic] resolves
to the same wheel. Requires Python 3.13+ and ocai>=0.1,<0.2.
It ships only ocai/anthropic/ into the shared ocai PEP 420 namespace,
organized one subpackage per wire interface. Today that is one:
ocai.anthropic.messages— the/v1/messagesinterface: typed wire structs, the codec, contract-censused conversion edges, the capability profile, and the chat component. Unary and streaming calls are implemented and certified against recorded fixtures.
What installing it does
Exactly one structural thing: the frozen ocai.anthropic.FRAGMENT
(a CatalogFragment) becomes discoverable through the ocai.fragments
entry-point group, so ocai.chat.model("anthropic/<model>", ...) can resolve
the provider and the conversion graph gains Anthropic's nodes and edges.
Importing ocai.anthropic is inert; there is no import-time registration.
Applications that want an explicit catalog compose it themselves with
Catalog.of(ocai.anthropic.FRAGMENT).
from ocai.anthropic import chat_model
from ocai.core import ApiKey
model = chat_model(
"claude-sonnet-4-5",
credentials=ApiKey.from_env("ANTHROPIC_API_KEY", header="x-api-key", scheme=""),
)
result = model.chat(...) # needs ocai[http] and a real key
Anthropic authenticates with the x-api-key header, hence the explicit
header=/scheme=; the required anthropic-version header is injected by
the interface's declared traits. chat_model is sugar over
ocai.chat.model("anthropic/<model>", ...) on a catalog built from this
fragment, never a separate code path.
Boundaries
- No
anthropicSDK: ocai owns the wire throughocai.wire. This plugin depends onocai.core+ocai.convert+ocai.chatonly, never onocai.wireorhttpx, so archived traffic can be re-converted by tooling with no ability to make network calls. msgspecis used only at the wire-decode boundary.- Every conversion edge declares an
EdgeContractand ships golden fixtures in the repository'sspec/.
License
Source-available under FSL-1.1-ALv2 (converting to Apache-2.0 two years after each release). ocai is not open source.
Metadata
Release files for ocai-anthropic 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ocai_anthropic-0.1.1.tar.gz | 52.6 kB | With provenance | Details for ocai_anthropic-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ocai_anthropic-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for ocai_anthropic-0.1.1-py3-none-any.whl |
Total release size: 100.7 kB
Release files / ocai_anthropic-0.1.1.tar.gz
| Download URL | ocai_anthropic-0.1.1.tar.gz |
|---|---|
| Size | 52.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
302b44103e4bb575fd13d9a4828ddaf68ce6609bbfada058293397abe9f1da4e
|
|
BLAKE2b-256 checksum How to use checksums |
d4ce99343894cba184149addf5aed8a4029c413469491247caf8b955625de5f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 11, 2026.
Transparency logRelease files / ocai_anthropic-0.1.1-py3-none-any.whl
| Download URL | ocai_anthropic-0.1.1-py3-none-any.whl |
|---|---|
| Size | 48.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7843f00f5a308dd600334d5a7997b7936e8edabf2234b2d622ccb761416cc8fc
|
|
BLAKE2b-256 checksum How to use checksums |
b35d6a7b2f6f02b9bdca4e8807df5e04a0ddab83843c55332e614e3fb67785f9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 11, 2026.
Transparency logSecurity for ocai-anthropic 0.1.1
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for ocai_anthropic-0.1.1.tar.gz
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 Nov 11, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.