Skip to content
ProviderBench home

Microsoft: MAI-Image-2.5 provider comparison

microsoft/mai-image-2.5

Microsoft's MAI-Image-2.5 is a high-quality image generation model available via Azure AI Foundry. It produces photorealistic and artistic images from text prompts with support for various aspect ratios.

Endpoints:
1
Context:
4.1K
Input:
text, image
Output:
image

Visual comparison

Endpoint pricing chart

Compare published endpoint pricing visually.

Effective price by endpoint

USD per token for input text. Lower is better.

Only directly comparable published units are charted.

Server-rendered comparison

Provider endpoints

Image prices use OpenRouter’s dedicated endpoint billing records and retain their published units. Missing speed data never removes an endpoint.

Endpoint comparison for Microsoft: MAI-Image-2.5
Provider / routeCurrent pricingSpeed measurementsEndpoint details
Provider / route
Azureazure
Current pricing
  • $0.000005 per token (input text)
  • $0.000008 per token (input image)
  • $0.000047 per token (output image)
Speed measurements
500-token response
Not applicable
Response starts
Insufficient recent data
Output speed
Insufficient recent data
Endpoint details
Uptime (30 min)
Insufficient recent data
Context
4.1K
Model format
N/a
Max output
N/a
3 parameters

aspect_ratio, input_references, n

Endpoint data fetched .

MAI-Image-2.5 deployment guide

How to choose a MAI-Image-2.5 inference provider

MAI-Image-2.5 is indexed here as a image model by Microsoft, with 1 provider endpoint from Azure. The comparison preserves each exact OpenRouter routing tag so pricing and performance observations can be connected to the route an application would actually request.

Match the endpoint to the workload

The model publishes a 4.1K-token context window. It accepts text, image input and returns image output. 3 distinct supported parameters appear across the listed routes. Confirm limits on the specific endpoint rather than assuming every host exposes the same configuration.

Compare image billing units directly

At least one token is published consistently across the listed endpoints, allowing a direct price chart for input text. Other charges remain in the table using OpenRouter’s exact billing labels.

Verify route format and availability

No model-format or quantization labels are currently published. Availability, rate limits, and regional support can change independently of catalog pricing, so confirm the selected routing tag before production deployment.