Feature request: Oracle Cloud Infrastructure (OCI) Generative AI client support

[fede-kamel]

Problem

Oracle Cloud Infrastructure offers Cohere models through its Generative AI service. Currently, the SDK supports AWS Bedrock as a cloud provider integration, but there is no equivalent support for OCI.

Enterprise customers using OCI need to build custom wrappers to use Cohere models through OCI endpoints, which is error-prone and difficult to maintain across SDK versions.

Proposed Solution

Add OciClient (V1) and OciClientV2 (V2) classes following the same architectural pattern as the existing BedrockClient:

from cohere import OciClient

client = OciClient(
    compartment_id="ocid1.compartment...",
    region="us-chicago-1"
)

# Works like the standard Cohere client
response = client.chat(
    model="command-r-plus",
    messages=[{"role": "user", "content": "Hello"}]
)

Capabilities

• Full authentication support (config file, instance principal, resource principal, direct credentials)
• Embed support (all v3 models)
• Chat with streaming (Command R, Command A models)
• V2 API support
• Region-independent — uses display names instead of region-specific OCIDs
• oci SDK as optional dependency (pip install cohere[oci])

Context

We work with Cohere models at Oracle through the OCI Generative AI service. Having official SDK support would benefit all OCI customers using Cohere models and bring parity with the existing Bedrock integration.

Implementation available in PR #718, with 14 integration tests passing.

[fern-support]

Hi @fede-kamel,

We saw your comment on the other PR. Sorry for the confusion here. We at Fern are partner maintainers of this and the other cohere sdks because our sdk generators are used to generate them.

We met with @mkozakov last week, and we liked your original proposal, but we wanted to make a few changes. Since your proposal was incoming from a branch, we just grafted it onto a new branch so we could make edits. The main change we made is limiting the scope of the OCI Client to the V2 api, since v1 is considered legacy and we want to move usage away from that model. Plus we made some additional safety checks and test modifications.

We believe the new PR is ready to merge now, so if you have feedback on our changes, we would love to hear it.

Thanks!

[fede-kamel]

For maintainers' visibility, I want to restate the current state clearly: the official Oracle PR for the OCI integration is #718:
#718

Why #718 should remain the canonical integration thread:

• It is the original Oracle-authored contribution for OCI support in cohere-python.
• It preserves the existing provider pattern in this repo by covering both OciClient and OciClientV2, rather than changing product scope to V2-only by default.
• It now incorporates the substantive review feedback that was raised during the parallel discussion, so the technical concerns are addressed on the Oracle PR itself.
• The branch has been cleaned up and validated directly against the OCI integration path, which keeps authorship, reviewability, and implementation history in one place.
• Keeping the OCI work unified in #718 avoids splitting design decisions, code review, and merge discussion across parallel PRs for the same integration.

So from the Oracle side, #718 is the proposal that should be reviewed and advanced as the official OCI integration for Cohere users on Oracle Cloud.