Repository navigation
fix(cost-map): restore later azure Models API retirement dates and date gpt-6.1-sol - #44072
Conversation
…te gpt-6.1-sol Price-Sync: litellm-providers
|
|
 |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| "max_output_tokens": 2000, | ||
| "mode": "audio_transcription", | ||
| "output_cost_per_token": 1e-05, | ||
| "source": "https://management.azure.com/subscriptions/c873328e-b572-4770-8dff-aaeb6f1f0e79/providers/Microsoft.CognitiveServices/locations/eastus2/models?api-version=2024-10-01", |
There was a problem hiding this comment.
source for azure/gpt-4o-transcribe is a subscription-scoped Azure management API URL, not a public provider model page. Readers without access to that subscription cannot use it to verify the revised retirement date. Please use a publicly verifiable source or make the provenance accessible.
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
There was a problem hiding this comment.
That context resolves my concern. The Azure Models API is the authoritative input for this registry sync, while the public retirement schedule documents the conflicting date and explains why the later API value wins. Since the PR body records the endpoint, field, region, and fetch date, the subscription-scoped URL is reasonable provenance for this metadata field. No change is needed.
| }, | ||
| "azure/gpt-4.1-nano": { | ||
| "deprecation_date": "2026-10-14", | ||
| "deprecation_date": "2027-04-14", |
There was a problem hiding this comment.
There was a problem hiding this comment.
Understood. Given this is intentionally an isolated catalog-data sync, I won’t require individual-date regression tests in this PR. The existing schema/catalog checks still validate structure rather than these exact values, so a follow-up test or generated catalog validation would be useful to prevent a later registry sync from reverting the dates.
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 2388307. Configure here.
Merging this PR will not alter performance
Comparing 
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
1 participant
TLDR
Problem this solves:
deprecation_datevalues back to the earlier retirement schedule date, undoing fix(cost-map): take the later azure deprecation date for gpt-4.1-nano, gpt-4o-transcribe and gpt-realtime-2.1 #42986 and chore(cost-map): move azure gpt-realtime-2.1-mini deprecation date to the later Models API date #43058azure-conflicting-dates-latest-winssays the latest of the Models API and schedule dates wins for Azureazure/gpt-6.1-solandazure/gpt-6.1-sol-2026-09-29carry nodeprecation_datealthough the Models API states oneHow it solves it:
deprecation_dateonly, merge mode keeps every other fieldRows
All rows are kind api, from the Azure Models API (the list source of
GET /api/cli/list/azure): https://management.azure.com/subscriptions/c873328e-b572-4770-8dff-aaeb6f1f0e79/providers/Microsoft.CognitiveServices/locations/eastus2/models?api-version=2024-10-01, fieldmodel.deprecation.inference, fetched 2026-10-01. Schedule page: https://learn.microsoft.com/en-us/azure/foundry/openai/concepts/model-retirement-schedule (updated 2026-09-23), fetched rawazure/gpt-4.1-nano2027-04-14T00:00:00Zgpt-4.1-nano | 2025-04-14 | Deprecated | 2026-10-14azure/gpt-4.1-nano-2025-04-14azure/us/gpt-4.1-nanoazure/us/gpt-4.1-nano-2025-04-14azure/eu/gpt-4.1-nanoazure/gpt-4o-transcribe2026-12-31T00:00:00Zgpt-4o-transcribe | 2025-03-20 | GA | 2026-10-15azure/gpt-realtime-2.12027-07-31T00:00:00Zgpt-realtime-2.1 | 2026-07-07 | GA | 2027-06-25azure/gpt-realtime-2.1-mini2027-07-31T00:00:00Zgpt-realtime-2.1-mini | 2026-07-07 | GA | 2027-06-25azure/gpt-6.1-sol2028-03-11T00:00:00Zazure/gpt-6.1-sol-2026-09-29The gpt-4.1-nano date is the case ruling
azure-conflicting-dates-latest-winswas decided on.azure/gpt-4o-transcribehad nosource, so it now points at the Models API URL; every other row keeps its existingsource.azure_ai/gpt-6.1-solstays undated like its siblingazure_ai/gpt-6-solMapping
The list API emits
OpenAI.<model>.<version>ids (for exampleOpenAI.gpt-4.1-nano.2025-04-14), mapped toazure/<model>andazure/<model>-<version>. That naming mismatch is why the dispatcher reported mostazure/*OpenAI rows as delisted; they are still listedDelisted by the provider
Absent from the eastus2 Models API under any name and left undated (no retirement date stated on the schedule or retired models pages):
azure/chat-latest,azure/computer-use-preview,azure/container,azure/gpt-3.5-turbo,azure/gpt-3.5-turbo-instruct-0914,azure/gpt-35-turbo,azure/gpt-35-turbo-instruct,azure/gpt-35-turbo-instruct-0914,azure/gpt-4-0125-preview,azure/gpt-4-1106-preview,azure/gpt-4-turbo,azure/gpt-4-turbo-vision-preview,azure/gpt-5.2-pro,azure/gpt-5.5-pro,azure/gpt-5.6,azure/o1-mini,azure/o3-proAbsent and already dated:
azure/ada,azure/command-r-plus,azure/gpt-35-turbo-16k,azure/gpt-35-turbo-16k-0613,azure/gpt-4,azure/gpt-4-0613,azure/gpt-4-32k,azure/gpt-4-32k-0613,azure/gpt-4.5-preview,azure/gpt-5-chat,azure/gpt-5.1-chat,azure/gpt-5.2-chat,azure/gpt-5.3-chat,azure/o3-deep-research,azure/tts-1,azure/tts-1-hd,azure/whisper-1azure/mistral-large-2402andazure/mistral-large-lateststay undated perazure-mistral-large-conflicting-retirement-stay-undated. Coverage gap rather than delisting:azure/sora-2-pro,azure/sora-2-pro-high-res(video)Changed pages
The Cohere pricing page matches the catalog (Command A $2.50/$10.00, Command A Plus $0.80/$3.20, embed-v4 $0.12, Rerank v4 Fast $2.00 and Pro $2.50 per 1K searches). The AOAI pricing page serves no static prices. The whats-new page has no entry after May 2026. The Claude models page only adds the gated Mythos preview, left out per
azure-claude-mythos-leave-out-until-priced. models-sold-directly limits match the azure rows already reconciled in #43759Pre-Submission checklist
Note
Low Risk
Metadata-only cost-map JSON changes; no runtime logic, pricing fields, or auth paths are modified.
Overview
Updates Azure model deprecation_date metadata in
model_prices_and_context_window.jsonand its backup so retirement reflects the later Azure Models API inference date when it disagrees with the public schedule—undoing a recent registry sync that had reverted eight rows to earlier schedule dates.gpt-4.1-nano variants (global, US, EU) move from 2026-10-14 to 2027-04-14; gpt-realtime-2.1 and mini from 2027-06-25 to 2027-07-31; gpt-4o-transcribe from 2026-10-15 to 2026-12-31, with a new
sourcepointing at the eastus2 Models API. gpt-6.1-sol and gpt-6.1-sol-2026-09-29 gaindeprecation_date: 2028-03-11 where they were previously undated.Reviewed by Cursor Bugbot for commit a490838. Bugbot is set up for automated code reviews on this repo. Configure here.