feat(microsoft-foundry/MAI-Image-2.5-Pro): add new models [bot]

[models-bot]

Auto-generated by model-addition-agent for microsoft-foundry/MAI-Image-2.5-Pro.

---

Note

Low Risk
Adds a static model metadata YAML with no runtime, auth, or API logic changes.

Overview
Adds a new microsoft-foundry provider definition for MAI-Image-2.5-Pro, registering it as a preview, serverless image model with text+image input and image output.

The entry sets a 32k context window, supportedModes/mode: image, and a retirementDate of 2026-10-01. It omits a costs block because official pricing is not published (placeholder "$-" in Microsoft’s table), and documents that in a comment.

removeParams strips chat/completion knobs that don’t apply to this image API (e.g. temperature, stream, tool_choice, reasoning_effort), matching how other Foundry image models are configured. Official Learn, catalog, and pricing URLs are listed under sources.

^{Reviewed by Cursor Bugbot for commit 3d76dcc. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

/test-models

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 3d76dcc. Configure here.}

[cursor]

Alias gets snapshot retirement date

Medium Severity

retirementDate 2026-10-01 is set on the floating alias MAI-Image-2.5-Pro. Official Foundry notices and the cited catalog do not retire this alias; that date is associated with version 2026-06-19 (and is also gpt-4o's retirement). Aliases and dated snapshots deprecate independently, so this can mark a still-serving alias as retiring.

 

^{Triggered by learned rule: Aliases and dated snapshots deprecate independently}

^{Reviewed by Cursor Bugbot for commit 3d76dcc. Configure here.}

[LordGameleo]

Approving: bot-generated model addition. Required check (Validate YAML files) is green; the gateway-test trigger failure is a CI infra issue, not a model validation failure.