Support Matrix

A model in the registry, or a protocol in a module, is not a promise that it works against the provider's live API. This page says, for every model row and every protocol 2.3 added, which of three levels of verification it has reached. The levels are kept apart on purpose: a documented rule that is tested offline is still not live-verified.

The test files below are named without their .test.ts suffix and live in packages/core/test.

Models

Every row here is new in 2.3 or got new rules in 2.3. The request rules each row applies are on Model profiles; prices are on Pricing. A model without a bundled price still runs: under a USD budget it reports an unpriced-model warning, or is refused with unknownPrice: 'reject' (Models without a price).

"Research-dated" means the facts come from the dated research behind the 2.3 plan and were not checked against the source again at release. Every profile names its sourceUrl and checkedAt where it has them. gemini-3-pro, shut down on 2026-03-09, keeps its row; its profile reports it deprecated, resolving to gemini-3.1-pro-preview, with no dated source.

DeepSeek V4's always-on reasoning, and its refusal of response_format: json_schema and of a forced tool choice, were observed by the opt-in DeepSeek live test when it was added (August 2026, before 2.3). 2.3 states the forced tool choice in the row and sends it as auto; it did not run the live test again.

Protocols

Deuz reads a stop explanation from Anthropic (stop_details, with a refusal's category) and from OpenAI (the refusal text, without a category). It reads none from Gemini: a Gemini candidate's finishMessage is not read, so a Gemini stop has no stopDetails.

• Streams, Gemini. The streaming adapter behind generateText, streamChat, the object calls and native runs maps every FinishReason value of @google/genai 2.28, each with a fixture (2.3). The filters SAFETY, RECITATION, BLOCKLIST, PROHIBITED_CONTENT, SPII, IMAGE_SAFETY, IMAGE_PROHIBITED_CONTENT and IMAGE_RECITATION, and a blocked prompt, end a turn with content_filter; before 2.3, SPII and the last two ended it with 'stop'. MAX_TOKENS and CONTINUATION end it with length (Deuz sends no continuation token; CONTINUATION ended it with 'stop' before 2.3), STOP and FINISH_REASON_UNSPECIFIED with stop, and so do the stops that leave no usable answer (LANGUAGE, OTHER, MALFORMED_FUNCTION_CALL, UNEXPECTED_TOOL_CALL, TOO_MANY_TOOL_CALLS, NO_IMAGE, IMAGE_OTHER), as before 2.3. A value 2.28 does not list ends it with stop. The finish part keeps Gemini's own value as providerMetadata.google.finishReason (2.3), which tells those stops from STOP. A turn that streamed a call ends with tool_calls unless a filter or a limit stopped it; before 2.3 the call won over every reason.
• Streams, OpenAI. Chat Completions' finish_reason maps one to one, with the deprecated function_call as tool_calls. A Responses turn ends with length when incomplete_details.reason is max_output_tokens and with content_filter when it is content_filter; before 2.3 the latter ended with 'stop', or 'tool_calls' when the turn streamed a call. max_messages and steered, which openai 7.32 does not document beyond the name, end it as a complete response does. A refusal on either wire ends the turn with content_filter unless the provider reported length or content_filter itself, also when the stream closed before its last event (Chat Completions without a finish_reason, Responses without response.completed or response.incomplete). Before 2.3 the refusal was dropped, so a refused turn ended with 'stop' (or 'tool_calls') like an empty answer. The refusal never becomes answer text.
• Batch results. The batch parsers share the streaming adapters' mapping, so a batch result ends as the same reply does when streamed: the same finish reason, for an OpenAI refusal the same stopDetails and providerMetadata.openai.refusal, and for Gemini the same providerMetadata.google.finishReason.
• Tool calls. Whatever the provider, a turn that ends with content_filter or length dispatches none of its tool calls (2.3; finish-gate replays the Anthropic wire, finish-gate-providers the Gemini, Responses and Chat Completions wires). That covers a Gemini filter or limit after a call, an OpenAI turn its content filter stopped, and an OpenAI refusal. A turn that ends with any other reason is not held back: a Gemini stop without a usable answer after a call ends with tool_calls, and its call runs, as before 2.3.

2.4

2.4 adds no model row and no provider protocol, and nothing in it was run against a live provider: every model call its features make (memory LLM and embedder callbacks, native runs under the goal supervisor, verifiers, skill proposals) is tested against scripted models. What 2.4 adds is verified against the backends it runs on.

Golden fixtures recorded with 2.3.0 (179 scenarios across the provider factories) check in every run that, with the 2.4 features off, the provider requests (method, URL, headers and body bytes) are the ones 2.3.0 sent. See What is new in 2.4 for the release's known limits.

Related

• Model profiles: what resolveModelProfile reports for each model, with its source and check date.
• Provider conformance: the contract every adapter's stream, usage, finish and errors must satisfy.
• Compatibility: runtimes, subpaths and optional peers.