open-responses.responses
Package
Section titled “Package”@ai-sdk/open-responses
Factories
Section titled “Factories”AIProviders.openResponses
Capabilities
Section titled “Capabilities”- Language
Custom URL factory mirrors upstream open-responses 2.0.39: provider ID is derived from the caller supplied name, optional API key and custom headers receive the versioned user-agent suffix, request building covers file URL/data inputs, rich tool-result content, function tools, tool choice, structured text formats, top-level reasoning effort mapping, providerOptions reasoningSummary, precise denied-tool fallback text, finish reasons, usage, and response metadata. Manual replay retains output order, item IDs, URL annotations, structured/encrypted reasoning, and provider-native effort precedence; unsupported provider tools warn explicitly, and stream reasoning keeps its original IDs through EOF closure. The 2.0.36 pass streams reasoning summaries, preserves error finishes for failed/error events, and surfaces validation failures for malformed known events. The experimental extension item/tool/event codec registry and lossless custom-event replay remain deferred until Swift has a public extension design. ProviderV4 type names, ESM-only packaging, Node 22 engines, optional JS headers config, and workflow serialization helpers are JS-only upstream concerns. The 2.0.39 pass adds strictResponseInput: ID-less assistant history becomes simple input text while ID-bearing history remains completed output content.
Factory argument requirements are defined by the public Swift factory signatures. Use Public symbols when you need the exact initializer or factory declaration.
Return to the provider matrix.