[KongchangAI]
ProductAI SDK OpenAI provider

@ai-sdk/openai

A provider package in the Vercel AI SDK for connecting to OpenAI services. It depends on @ai-sdk/provider and @ai-sdk/provider-utils to handle integration with the OpenAI API.

Core Facts

Timeline (last 90 days)

Oct 15

All concrete provider packages (such as @ai-sdk/openai, @ai-sdk/anthropic, @ai-sdk/xai) must implement the interfaces declared by @ai-sdk/provider, and any enum extension, field addition or removal, or type narrowing in that package propagates to all downstream providers

Unverified50%
Sep 30

@ai-sdk/openai@3.0.121 was released as a patch version, with the core change being the addition of support for the GPT-6.1 Sol model.

Verified90%
Sep 29

This fix detects and unwraps redundant allOf wrappers in the conversion layer, making the generated JSON Schema compliant with OpenAI's strict mode requirements.

Unverified50%
Sep 29

The core fix in this update is the rewriting of recursive Zod schemas that use allOf wrappers, with commit record 4e94782.

Unverified50%
Sep 29

The @ai-sdk/openai package is responsible for integration with OpenAI models.

Unverified50%
Sep 27

Within the AI SDK ecosystem, there exists an adapter package @ai-sdk/zod similar to @ai-sdk/valibot, with both providing the same public interface.

Verified80%
Sep 26

The article recommends that when upgrading @ai-sdk/azure to 4.0.82, users should simultaneously confirm that @ai-sdk/openai is at version 4.0.78 or a compatible version, and verify Azure OpenAI calls in a test environment.

Unverified50%
Sep 26

The fact that @ai-sdk/amazon-bedrock depends on @ai-sdk/openai does not mean an OpenAI account or key is required, because @ai-sdk/openai encapsulates general-purpose capabilities such as HTTP request handling, streaming response parsing, and tool-calling protocols that are shared across multiple provider packages.

Verified75%
Sep 26

The SDK validates update requests against the effort levels actually supported by the model, issues warnings for unsupported updates at the request level, and automatically ignores them.

Unverified50%
Sep 26

This patch version adds support for reasoningEffortUpdate: 'none'.

Unverified50%

12 more timeline events

All Facts (18)

Verified

The upgrade method is to run npm install @ai-sdk/openai@4.0.60.

90%
Verified

Within the AI SDK ecosystem, there exists an adapter package @ai-sdk/zod similar to @ai-sdk/valibot, with both providing the same public interface.

80%
Verified

The fact that @ai-sdk/amazon-bedrock depends on @ai-sdk/openai does not mean an OpenAI account or key is required, because @ai-sdk/openai encapsulates general-purpose capabilities such as HTTP request handling, streaming response parsing, and tool-calling protocols that are shared across multiple provider packages.

75%
Verified

Patch versions are typically backward compatible and do not introduce breaking changes.

75%
Verified

@ai-sdk/openai@3.0.121 was released as a patch version, with the core change being the addition of support for the GPT-6.1 Sol model.

90%
Unverified

All concrete provider packages (such as @ai-sdk/openai, @ai-sdk/anthropic, @ai-sdk/xai) must implement the interfaces declared by @ai-sdk/provider, and any enum extension, field addition or removal, or type narrowing in that package propagates to all downstream providers

50%
Unverified

The @ai-sdk/openai package is responsible for integration with OpenAI models.

50%
Unverified

This fix detects and unwraps redundant allOf wrappers in the conversion layer, making the generated JSON Schema compliant with OpenAI's strict mode requirements.

50%
Unverified

The core fix in this update is the rewriting of recursive Zod schemas that use allOf wrappers, with commit record 4e94782.

50%
Unverified

The article recommends that when upgrading @ai-sdk/azure to 4.0.82, users should simultaneously confirm that @ai-sdk/openai is at version 4.0.78 or a compatible version, and verify Azure OpenAI calls in a test environment.

50%
Unverified

The strategy of directly rejecting at the history level while issuing warnings and ignoring at the request level balances runtime robustness with data reliability and is a deliberate trade-off design.

50%
Unverified

The SDK validates update requests against the effort levels actually supported by the model, issues warnings for unsupported updates at the request level, and automatically ignores them.

50%
Unverified

For unsupported effort updates in historical messages, the SDK rejects them directly.

50%
Unverified

When using @ai-sdk/openai at the same time, it is recommended to keep both at matching versions to avoid potential behavioral inconsistencies.

50%
Unverified

@ai-sdk/azure reuses a large amount of the underlying logic from @ai-sdk/openai, with differentiated handling only at the levels of authentication method, endpoint configuration, and deployment name.

50%
Unverified

When encountering anomalous Azure-related behavior, in addition to reviewing the Azure package update log, one should also pay attention to the change records of its underlying OpenAI package dependency.

50%
Unverified

This patch version adds support for reasoningEffortUpdate: 'none'.

50%
Unverified

The key change in version 4.0.60 comes from commit 17e489e, titled "feat(openai): add GPT-6 reasoning configuration updates".

50%

Source Articles