This model is deprecated. We only continue performance benchmarking for the default 10k input token workload. Results for other workloads are historical and no longer updated.

MiniMax has launched a newer model, MiniMax-M3. We suggest considering it instead.

For more information, see comparison of MiniMax-M3 to other models and API provider benchmarks for MiniMax-M3.

MiniMax logo
MiniMax
•

Open weights model

•

Released March 2026

MiniMax-M2.7 API Provider Benchmarking & Analysis

Model Comparison

This analysis is intended to support you in choosing the best API provider of MiniMax-M2.7 for your use-case.

Fastest

#1
SambaNovaSambaNova
395.8 t/s
#2
FireworksFireworks
205.9 t/s
#3
Novita (FP8)Novita (FP8)
63.9 t/s
#4
MiniMaxMiniMax
61.2 t/s

Output speed

Total 5 providers

Lowest Latency

#1
SambaNovaSambaNova
8.69 s
#2
FireworksFireworks
12.59 s
#3
Novita (FP8)Novita (FP8)
40.20 s
#4
MiniMaxMiniMax
41.81 s

Time to first answer token

Total 5 providers

Lowest Price

#1
GMI (FP8)GMI (FP8)
$0.22
#2
FireworksFireworks
$0.22
#3
MiniMaxMiniMax
$0.22
#4
Novita (FP8)Novita (FP8)
$0.22
#5
SambaNovaSambaNova
$0.78

Blended price (per 1M tokens)

Total 5 providers

MiniMax-M2.7 is available through 5 API providers, each offering different performance characteristics and pricing. Below is a comparison of the key metrics across providers.

  • For output speed, the top providers are SambaNova (395.8 t/s), Fireworks (205.9 t/s), and Novita (FP8) (63.9 t/s). Speed varies significantly across providers, with a 547% difference between the fastest and slowest.
  • For latency, SambaNova (8.69s), Fireworks (12.59s), and Novita (FP8) (40.20s) offer the lowest time to first answer token.
  • For pricing, GMI (FP8) (0.22), Fireworks (0.22), and MiniMax (0.22) offer the lowest blended prices per 1M tokens. Prices vary up to 3.5x across providers.
  • SambaNova offers the best performance with both the highest speed and lowest latency. For cost optimization, GMI (FP8) provides the most competitive pricing.

Highlights

Speed

Output tokens per second · Higher is better

End-to-End Response Time

Seconds · Lower is better

Price

USD per 1M tokens (blended) · Lower is better

Pricing

Pricing: Cache Hit, Input, and Output

Price (USD per M Tokens) · Lower is better · 10,000 input tokens

Price per token for cached prompts (previously processed), typically offering a significant discount compared to regular input price, represented as USD per million tokens. The values shown here are the cache hit price; cache write and cache storage are billed separately and vary by provider — see "Cache pricing by provider" for detail.

Pricing: Blended Price

Blended at 7:2:1 (cache-input-output) · USD per 1M tokens (blended) · Lower is better

Price per token, shown in USD per million tokens. Price is a blend of cache hit, input, and output token prices using the selected ratio (default 7:2:1 cache-input-output).

Pricing: Cache Discount

1 - (cache hit price / input price) · Higher is better

Reduction in input token cost due to cache hit relative to input price. Formula: 1 - (Cache Hit Price per Token / Input Token Price), where cache hit price is the first-party cache hit price or the median provider cache hit price. Note that this discount figure does not account for all costs associated with cache hits, such as cache write and storage costs.

Output Speed vs. Price

Blended at 7:2:1 (cache-input-output) · Output speed: output tokens per second · USD per 1M tokens (blended)
Most attractive quadrant
Pareto line

Tokens per second received while the model is generating tokens (ie. after first chunk has been received from the API for models which support streaming).

Speed

Measured by Output Speed (tokens per second)

Output Speed: MiniMax-M2.7

Output speed: output tokens per second · 10,000 input tokens

Tokens per second received while the model is generating tokens (ie. after first chunk has been received from the API for models which support streaming).

Figures represent performance of the model's first-party API (e.g. OpenAI for o1) or the median across providers where a first-party API is not available (e.g. Meta's Llama models).

Latency vs. Output Speed

Latency: seconds to first token received · Output speed: output tokens per second · 10,000 input tokens
Most attractive quadrant
Pareto line

Tokens per second received while the model is generating tokens (ie. after first chunk has been received from the API for models which support streaming).

Latency

Measured by Time (seconds) to First Token

Time to First Answer Token

Seconds to first token received · Lower is better · 10,000 input tokens

Time to first answer token received, in seconds, after API request sent. For reasoning models, this includes the 'thinking' time of the model before providing an answer. For models which do not support streaming, this represents time to receive the completion.

Figures represent median (P50) measurement over the past 72 hours to reflect sustained changes in performance.

End-to-End Response Time

Seconds to output 500 tokens, calculated based on time to first token, 'thinking' time for reasoning models, and output speed

End-to-End Response Time

Seconds to output 500 tokens, including reasoning model 'thinking' time · Lower is better · 10,000 input tokens

Seconds to receive a 500 token response. Key components:

  • Input time: Time to receive the first response token
  • Thinking time (only for reasoning models): Time reasoning models spend outputting tokens to reason prior to providing an answer. Amount of tokens based on the average reasoning tokens across a diverse set of 60 prompts (methodology details).
  • Answer time: Time to generate 500 output tokens, based on output speed

Key Comparison Metrics & API Features

GMI logoGMI
197k
Open
--
--
--
--
--
Fireworks logoFireworks
197k
Open
$0.09
199
0.63
15.55
12.40
MiniMax logoMiniMax
205k
Open
$0.08
62
1.60
49.22
39.58
Novita logoNovita
205k
Open
$0.06
66
1.63
46.31
37.14
SambaNova logoSambaNova
197k
Open
$0.35
397
2.47
9.94
6.21

Frequently Asked Questions

Common questions about MiniMax-M2.7 providers

MiniMax-M2.7 is available through 5 API providers: GMI (FP8), Fireworks, MiniMax, Novita (FP8), and SambaNova. Each provider offers different performance characteristics and pricing.

MiniMax-M2.7 is currently available through 5 API providers that we benchmark and track.

The fastest providers for MiniMax-M2.7 by output speed are SambaNova (395.8 t/s), Fireworks (205.9 t/s), and Novita (FP8) (63.9 t/s). Output speed measures how quickly tokens are generated after the model starts responding.

The providers with the lowest time to first answer token for MiniMax-M2.7 are SambaNova (8.69s), Fireworks (12.59s), and Novita (FP8) (40.20s). Lower latency means faster initial response time.

The most affordable providers for MiniMax-M2.7 by blended price are GMI (FP8) ($0.22 per 1M tokens), Fireworks ($0.22 per 1M tokens), and MiniMax ($0.22 per 1M tokens). Blended price uses a 7:2:1 cache hit/input/output token ratio.

The providers with the lowest input token pricing for MiniMax-M2.7 are GMI (FP8) ($0.30 per 1M input tokens), Fireworks ($0.30 per 1M input tokens), and MiniMax ($0.30 per 1M input tokens).

The providers with the lowest output token pricing for MiniMax-M2.7 are GMI (FP8) ($1.20 per 1M output tokens), Fireworks ($1.20 per 1M output tokens), and MiniMax ($1.20 per 1M output tokens).

Prices for MiniMax-M2.7 vary up to 3.5x across providers. The most affordable is GMI (FP8) at $0.22 per 1M tokens, while SambaNova charges $0.78 per 1M tokens.

Output speed for MiniMax-M2.7 varies significantly across providers. SambaNova is the fastest at 395.8 t/s, which is 6.5x faster than MiniMax at 61.2 t/s.

All 5 providers of MiniMax-M2.7 support JSON mode for structured output.

All 5 providers of MiniMax-M2.7 support function calling (tool use).

For MiniMax-M2.7, SambaNova offers the best performance with highest speed and lowest latency. For cost optimization, GMI (FP8) provides the most competitive pricing.

When choosing a provider for MiniMax-M2.7, consider: output speed (for throughput-intensive tasks), latency (for interactive applications requiring quick first responses), pricing (for cost-sensitive workloads), and API features like JSON mode or function calling.

Yes, provider performance can vary over time due to infrastructure changes, load balancing, and updates. We continuously benchmark all providers and display historical performance trends in the "Over Time" charts.

For information about MiniMax-M2.7's intelligence, capabilities, modalities, and how it compares to other models, see the model overview page. View model overview