feat(model_catalog): add Azure AI Foundry GPT-5.4 model metadata#28030
Conversation
Register azure_ai GPT-5.4 variants with pricing, context limits from Foundry catalog, and capability flags for cost routing and tooling. Co-authored-by: Cursor <cursoragent@cursor.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Greptile SummaryThis PR adds metadata for the Azure AI Foundry GPT-5.4 model family — eight entries covering base, pro, mini, and nano variants along with their dated snapshots — to both the primary and backup price/context-window JSON files.
Confidence Score: 5/5Additive-only JSON metadata change with no runtime logic modifications; both files are in sync and all previously identified gaps have been filled. The change is purely additive — new model entries in two JSON catalog files. All capability flags, tiered pricing fields, and cross-file consistency issues surfaced in prior review rounds have been corrected in this commit. No existing entries are modified, and no code paths are touched. No files require special attention.
|
| Filename | Overview |
|---|---|
| model_prices_and_context_window.json | Adds 8 new Azure AI Foundry GPT-5.4 family entries with pricing, token limits, and capability flags; all previously raised issues are now addressed |
| litellm/model_prices_and_context_window_backup.json | Backup file receives the same 8 GPT-5.4 model entries as the primary file; both files are now in sync |
Reviews (3): Last reviewed commit: "fix(model_catalog): sync web_search flag..." | Re-trigger Greptile
…data Add supports_web_search for base GPT-5.4 aliases, priority-tier Pro rates, and mini/nano above-272k plus priority pricing for correct spend math. Co-authored-by: Cursor <cursoragent@cursor.com>
|
@greptile review again with new commit that resolves the issues raised |
…ckup row Mirror supports_web_search for azure_ai/gpt-5.4-2026-03-05 in the backup catalog so it matches model_prices_and_context_window.json. Co-authored-by: Cursor <cursoragent@cursor.com>
|
@greptile review again with new commit that resolves the raised issue |
Adding gpt-5.4 azure_ai support