Repository navigation
feat(openai): GPT-5.6 catalog, gpt-realtime-2.1, gpt-transcribe, gpt-5.6-luna default - #221
Open
fra-shipper wants to merge 1 commit into
Open
fra-shipper wants to merge 1 commit into
fra-shipper wants to merge 1 commit into
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
gpt-5.6-sol,gpt-5.6-terra,gpt-5.6-luna, plus a baregpt-5.6alias) and switchesOpenAILLM's default model fromgpt-4o-minitogpt-5.6-lunain bothSDKs — a behaviour change for any caller that omits
model=, including theeval
LLMJudgedefault, the pipelineStreamHandler/TestSessionrealtime-engine LLM fallback, and the
getpatter eval run --judge-modelCLI default.
gpt-realtime-2.1/gpt-realtime-2.1-minitoOpenAIRealtimeModeland the realtime pricing table — point releases of
gpt-realtime-2/gpt-realtime-miniat the same published per-token rates.gpt-realtime-2stays the
OpenAIRealtime2default; the new ids are opt-in only.gpt-transcribe($0.0045/min) andgpt-live-transcribe($0.017/min)to
OpenAITranscriptionModeland both theopenai_realtime(inlineWhisper-family) and
openai_transcribepricing tables. Note:OpenAITranscribeSTTdoesn't yet accept these as amodel=override(see Notes below) — route through
input_audio_transcription_modelon theRealtime engine instead.
PRICING_LAST_UPDATEDto2026-08-24in both SDKs; keepsgpt-4o-mini-realtime-preview's entry with a comment flagging it's nolonger listed on OpenAI's current pricing page but is retained unchanged
for existing callers.
OpenAIRealtimeModel/OpenAITranscriptionModelplus the one default-modelchange called out above.
docs/python-sdk/anddocs/typescript-sdk/(
engines.mdx,llm.mdx,stt.mdx,providers/openai-realtime.mdx,providers/openai-realtime-2.mdx) to list the new model ids and rates.Verification
test_pricing.pygains 13 new tests acrossTestGpt56ChatPricing(5),TestRealtime21Pricing(6),TestGptTranscribeFamilyPricing(2);test_evals.pygains 1(
LLMJudgedefault);test_llm_api.pygains 2(
TestOpenAILLMDefaultModel) — 16 new Python tests total.pricing.test.tsgains 13 new tests (GPT-5.6 chat pricing 6,gpt-realtime-2.1/-minipricing 5,gpt-transcribe/gpt-live-transcribepricing 2);
evals.test.tsgains 1;llm-api.test.tsgains 2 — 16 newTypeScript tests total.
Notes / follow-ups
OpenAITranscribeSTTdoes not yet acceptgpt-transcribe/gpt-live-transcribeas amodel=/model:override, even though bothrates are already in the pricing catalog under
openai_transcribe— thisgap is called out inline in
docs/{python-sdk,typescript-sdk}/stt.mdx.Today the only way to route through these models is
input_audio_transcription_modelon the Realtime engine.gpt-4o-mini-realtime-preview's pricing entry is flagged in a codecomment (
pricing.py/pricing.ts) as no longer listed on OpenAI'scurrent published pricing page as of 2026-08-24; rates are kept unchanged
from the last verified value since the SDK can't independently confirm
them, and new integrations shouldn't be routed to it.
preference on their own — all changes are additive entries inside existing
catalog/enum files.
🤖 Generated with Claude Code