Repository navigation
fix(cost-map): restore later azure Models API retirement dates and date gpt-6.1-sol #44072
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -5516,7 +5516,7 @@ | |
| "supports_web_search": false | ||
| }, | ||
| "azure/gpt-4.1-nano": { | ||
| "deprecation_date": "2026-10-14", | ||
| "deprecation_date": "2027-04-14", | ||
| "cache_read_input_token_cost": 2.5e-08, | ||
| "input_cost_per_token": 1e-07, | ||
| "input_cost_per_token_batches": 5e-08, | ||
|
|
@@ -5550,7 +5550,7 @@ | |
| "supports_vision": true | ||
| }, | ||
| "azure/gpt-4.1-nano-2025-04-14": { | ||
| "deprecation_date": "2026-10-14", | ||
| "deprecation_date": "2027-04-14", | ||
| "cache_read_input_token_cost": 2.5e-08, | ||
| "input_cost_per_token": 1e-07, | ||
| "input_cost_per_token_batches": 5e-08, | ||
|
|
@@ -6133,7 +6133,7 @@ | |
| "cache_creation_input_audio_token_cost": 4e-07, | ||
| "cache_read_input_audio_token_cost": 4e-07, | ||
| "cache_read_input_token_cost": 4e-07, | ||
| "deprecation_date": "2027-06-25", | ||
| "deprecation_date": "2027-07-31", | ||
| "input_cost_per_audio_token": 3.2e-05, | ||
| "input_cost_per_image_token": 5e-06, | ||
| "input_cost_per_token": 4e-06, | ||
|
|
@@ -6168,7 +6168,7 @@ | |
| "cache_creation_input_audio_token_cost": 3e-07, | ||
| "cache_read_input_audio_token_cost": 3e-07, | ||
| "cache_read_input_token_cost": 6e-08, | ||
| "deprecation_date": "2027-06-25", | ||
| "deprecation_date": "2027-07-31", | ||
| "input_cost_per_audio_token": 1e-05, | ||
| "input_cost_per_image_token": 8e-07, | ||
| "input_cost_per_token": 6e-07, | ||
|
|
@@ -6346,14 +6346,15 @@ | |
| "supports_tool_choice": true | ||
| }, | ||
| "azure/gpt-4o-transcribe": { | ||
| "deprecation_date": "2026-10-15", | ||
| "deprecation_date": "2026-12-31", | ||
| "input_cost_per_audio_token": 2.5e-06, | ||
| "input_cost_per_token": 2.5e-06, | ||
| "litellm_provider": "azure", | ||
| "max_input_tokens": 16000, | ||
| "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", | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
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!
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 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. |
||
| "supported_endpoints": [ | ||
| "/v1/audio/transcriptions" | ||
| ] | ||
|
|
@@ -8571,6 +8572,7 @@ | |
| "cache_creation_input_token_cost_above_272k_tokens": 5e-06, | ||
| "cache_read_input_token_cost": 1e-07, | ||
| "cache_read_input_token_cost_above_272k_tokens": 2e-07, | ||
| "deprecation_date": "2028-03-11", | ||
| "input_cost_per_token": 2e-06, | ||
| "input_cost_per_token_above_272k_tokens": 4e-06, | ||
| "litellm_provider": "azure", | ||
|
|
@@ -8619,6 +8621,7 @@ | |
| "cache_creation_input_token_cost_above_272k_tokens": 5e-06, | ||
| "cache_read_input_token_cost": 1e-07, | ||
| "cache_read_input_token_cost_above_272k_tokens": 2e-07, | ||
| "deprecation_date": "2028-03-11", | ||
| "input_cost_per_token": 2e-06, | ||
| "input_cost_per_token_above_272k_tokens": 4e-06, | ||
| "litellm_provider": "azure", | ||
|
|
@@ -10972,7 +10975,7 @@ | |
| "supports_web_search": false | ||
| }, | ||
| "azure/us/gpt-4.1-nano-2025-04-14": { | ||
| "deprecation_date": "2026-10-14", | ||
| "deprecation_date": "2027-04-14", | ||
| "cache_read_input_token_cost": 2.8e-08, | ||
| "input_cost_per_token": 1.1e-07, | ||
| "input_cost_per_token_batches": 5.5e-08, | ||
|
|
@@ -70653,7 +70656,7 @@ | |
| "source": "https://prices.azure.com/api/retail/prices?$filter=serviceName%20eq%20'Foundry%20Models'%20and%20armRegionName%20eq%20'eastus'%20and%20priceType%20eq%20'Consumption'" | ||
| }, | ||
| "azure/eu/gpt-4.1-nano": { | ||
| "deprecation_date": "2026-10-14", | ||
| "deprecation_date": "2027-04-14", | ||
| "cache_read_input_token_cost": 2.8e-08, | ||
| "input_cost_per_token": 1.1e-07, | ||
| "input_cost_per_token_batches": 5.5e-08, | ||
|
|
@@ -71102,7 +71105,7 @@ | |
| "source": "https://prices.azure.com/api/retail/prices?$filter=serviceName%20eq%20'Foundry%20Models'%20and%20armRegionName%20eq%20'eastus'%20and%20priceType%20eq%20'Consumption'" | ||
| }, | ||
| "azure/us/gpt-4.1-nano": { | ||
| "deprecation_date": "2026-10-14", | ||
| "deprecation_date": "2027-04-14", | ||
| "cache_read_input_token_cost": 2.8e-08, | ||
| "input_cost_per_token": 1.1e-07, | ||
| "input_cost_per_token_batches": 5.5e-08, | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.