GPT-5.6 vs MiniMax M3
MiniMax M3 has been retired from our catalogue. Its figures below are the last published rates; calls to it are no longer served, while the other model in this comparison is.
Which one, when
Both take text and image in and return text, both let you turn thinking off, and their context windows are close at 1050000 for gpt-5.6 versus 1000000 for minimax-m3 - the real gap is cost and output room. minimax-m3 is about 13.3x cheaper on input, 16.7x cheaper on output and 6.7x cheaper on cache reads ($0.3/$1.2/$0.06 against $4/$20/$0.4), it also accepts video, and its 524288 max output dwarfs the 128000 cap on gpt-5.6. Pick gpt-5.6 when you want the newer 2026-07-09 model with an explicit vision flag and a 2026-02 cutoff; pick minimax-m3 for bulk long-context and very long generations.
Benchmarks
MiniMax M3: the vendor has not published benchmark scores.
Vendor-published: Alibaba (Qwen) Alibaba (Qwen) Alibaba (Qwen) Alibaba (Qwen) Alibaba (Qwen) Alibaba (Qwen) Alibaba (Qwen) Anthropic Anthropic Anthropic Anthropic Anthropic ByteDance DeepSeek DeepSeek DeepSeek Google Google Google Google MiniMax Moonshot Moonshot OpenAI OpenAI OpenAI OpenAI OpenAI OpenAI OpenAI Tencent Z.ai Z.ai Z.ai Z.ai
Pricing
| GPT-5.6 | MiniMax M3 | Δ | |
|---|---|---|---|
| Input / 1M tokens | $4 | $0.3 | 13× |
| Output / 1M tokens | $20 | $1.2 | 17× |
| Cache read / 1M tokens | $0.4 | $0.06 | 6.7× |
| Cache write | 1.25x (30m) / 2.5x (12h) | no separate charge | - |
Rates from the live catalogue at build time; each model page carries the current rate card. The main table shows base rates. Prompt length can change the rate for the entire request. See each model’s full rate card.
GPT-5.6 · Rates by prompt length
The whole request uses the rate for its input-length tier. Prices are USD per million tokens.
| Input tokens | Input | Output | Thinking input |
|---|---|---|---|
| 0 - 272,000 | $4 | $20 | - |
| 272,001 - 1,050,000 | $8 | $30 | - |
Where they sit · input price per 1M tokens across all 91 chat models on this billing unit (log scale)
Capabilities
| GPT-5.6 | MiniMax M3 | |
|---|---|---|
| Tool calling | yes | yes |
| Thinking control | configurable | configurable |
| Structured output | yes | - |
| Prompt caching | implicit + explicit | implicit (automatic) |
| Cache lifetime | at least 30m by default, 12h option on the Responses API | not published |
| Minimum cached prefix | 1,024 tokens | 512 tokens |
Specs
| GPT-5.6 | MiniMax M3 | |
|---|---|---|
| Input modalities | text image | text image video |
| Output modalities | text | text |
| Released | 2026-07-09 | 2026-06-01 |
| Knowledge cutoff | 2026-02 | - |
| Context window | 1,050,000 | 1,000,000 |
| Max output | 128,000 | 524,288 |
| Thinking parameter | reasoning.effort |
|
| Accepted values | reasoning.effort
| thinking.type
reasoning_split
|
| Default | medium | adaptive: thinking on, with the model deciding when extra reasoning helps |
Specs are transcribed from each vendor’s documentation; a row a vendor does not publish is left out rather than inferred. Full sources: GPT-5.6 · MiniMax M3
One prompt, both models, measured through the gateway
GPT-5.6 passed · 3 sentences
Enabling reasoning makes the model generate many additional internal tokens before producing an answer, so each request consumes substantially more compute. Those reasoning tokens are billed even though they are not visible to users, and longer processing can also increase tool calls, retries, and output length. The bill doubled because our cost per request rose, not necessarily because usage volume increased; we can control it by limiting reasoning effort and routing simpler tasks to cheaper models.
out 126 tok (+30 thinking) latency 3.0 s
MiniMax M3 passed · 3 sentences
Reasoning models don't just answer — they first generate extensive internal "thinking" tokens to work through the problem step-by-step, and you're billed for all of those tokens even though users never see them. A query that previously cost ~200 tokens may now cost 2,000–10,000 once reasoning is enabled, multiplying per-query spend by roughly 5–50x while the visible output stayed the same size — that's the doubling. The lever is tuning: cap reasoning effort on simple queries, cache the reasoning traces, and reserve the full reasoning model for only your hardest 10–20% of requests, which typically restores 60–80% of the savings.
out 764 tok (+629 thinking) latency 3.5 s
Instruction following (exactly three sentences, so countable), audience shaping (CFO register), and the hidden-thinking billing gap the token meters below expose.
GPT-5.6 passed · 8/8 cases
```python def longest_run(xs): if not xs: return 0 best = cur = 1 for i in range(1, len(xs)): if xs[i] == xs[i - 1]: cur += 1 else: best = max(best, cur) cur = 1 return max(best, cur) ``` The original code counted equal *transitions* rather than items, so a run of one had length `0`, a run of three had length `2`, and tracking from zero caused the off-by-one error. The corrected version starts each run at length `1`, resets to `1` when the value changes, and performs a final `max` after the loop so a run ending at the last element is included; an empty input still returns `0`.
out 277 tok (+93 thinking) latency 4.2 s
MiniMax M3 passed · 8/8 cases
The bug is that the loop starts at index 1 and treats `cur` as the number of *equal transitions* rather than the run length, so a run of *k* consecutive equal items is reported as `k − 1`, and a single-element list (where the loop body never executes) returns 0 instead of 1. A correct version tracks the actual run length by seeding `cur = 1` and resetting it to 1 (not 0) on a mismatch: ```python def longest_run(xs): if not xs: return 0 best = cur = 1 for i in range(1, len(xs)): if xs[i] == xs[i - 1]: cur += 1 else: cur = 1 if cur > best: best = cur return best ``` Now `[5]` returns `1`, `[1,1,1]` returns `3`, and a run like `[1,2,2,2]` that ends at the last index is correctly captured as `3` because `cur` is updated before `best` is compared on every iteration, including the final one.
out 845 tok (+596 thinking) latency 3.5 s
Whether the fix is actually correct (runnable), explanation density, and token efficiency on a bounded task.
GPT-5.6 passed · 5/5 fields, guidance "withheld pending the Q4 close"
{ "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": 412, "growth_pct": null, "guidance": "withheld pending the Q4 close" }
out 179 tok (+118 thinking) latency 3.7 s
MiniMax M3 passed · 5/5 fields, guidance null
```json { "company": null, "quarter": "Q3", "revenue_usd_m": 412, "growth_pct": null, "guidance": null } ```
out 1002 tok (+955 thinking) latency 3.6 s
Schema obedience (no invented fields), hallucination pressure (guidance is explicitly withheld), and structured-output path differences.
GPT-5.6 passed · 120 words, 0 banned, 1 question
Today we are introducing Prompt Cache, a new API gateway feature that stores reusable prompt prefixes and serves them across supported model providers. By recognizing identical system instructions, tools, examples, and context blocks, Prompt Cache reduces repeated input processing, lowers latency, and helps control token costs without changing application code. Teams can configure retention windows, cache keys, provider routing, encryption, and regional storage policies from one dashboard or API. What happens when a preferred provider is unavailable? The gateway can route requests to another provider while reusing eligible cached content, preserving performance and consistency. Built-in metrics report hit rates, savings, latency, and provider usage, while audit logs support governance. Prompt Cache is available today in public preview for all customers.
out 628 tok (+473 thinking) latency 7.3 s
MiniMax M3 passed · 121 words, 0 banned, 1 question
Introducing PromptCache, our intelligent caching layer for the API gateway. Tired of paying twice for identical requests? The feature stores prompt-response pairs across every connected provider, returning cached results instead of hitting costly endpoints. Deployment requires only a single configuration flag, and semantic similarity detection happens automatically. Latency drops up to 70% on repeated traffic while costs follow the same downward curve. Developers access detailed cache hit metrics, eviction logs, and provider breakdowns through the dashboard. Whether routing to OpenAI, Anthropic, or local models, every cached token saves time and money. The cache respects TTL policies, supports manual purging, and encrypts stored content. Available today for Pro and Enterprise tiers—enable PromptCache on existing endpoints and watch inference bills shrink immediately.
out 2808 tok (+2656 thinking) latency 6.0 s
Constraint obedience (word budget, banned-word list, the single question), style fingerprint, and length control.
Switch between them with one line
Both ids are in every tab below; the highlighted pair of lines is the only edit. Same endpoint, same key, same request shape.
from openai import OpenAI
client = OpenAI(
base_url="https://synthorai.io/v1",
api_key="sk-syn-...",
)
resp = client.chat.completions.create(
model="gpt-5.6",
# model="minimax-m3", # uncomment this line, comment the one above
messages=[{"role": "user", "content": "Summarize this diff"}],
reasoning_effort="medium",
)
print(resp.choices[0].message.content)import OpenAI from "openai";
const client = new OpenAI({
baseURL: "https://synthorai.io/v1",
apiKey: "sk-syn-...",
});
const resp = await client.chat.completions.create({
model: "gpt-5.6",
// model: "minimax-m3", // uncomment this line, comment the one above
messages: [{ role: "user", content: "Summarize this diff" }],
reasoning_effort: "medium",
});
console.log(resp.choices[0].message.content);curl https://synthorai.io/v1/chat/completions \
-H "Authorization: Bearer sk-syn-..." \
-H "Content-Type: application/json" \
-d '{
"model": "gpt-5.6",
# "model": "minimax-m3", # uncomment this line, comment the one above
"messages": [{"role": "user", "content": "Hello"}],
"reasoning_effort": "medium"
}'package main
import (
"context"
"fmt"
"github.com/openai/openai-go/v3"
"github.com/openai/openai-go/v3/option"
)
func main() {
client := openai.NewClient(
option.WithBaseURL("https://synthorai.io/v1"),
option.WithAPIKey("sk-syn-..."),
)
resp, _ := client.Chat.Completions.New(context.TODO(), openai.ChatCompletionNewParams{
Model: "gpt-5.6",
// Model: "minimax-m3", // uncomment this line, comment the one above
Messages: []openai.ChatCompletionMessageParamUnion{
openai.UserMessage("Summarize this diff"),
},
ReasoningEffort: openai.ReasoningEffortMedium,
})
fmt.Println(resp.Choices[0].Message.Content)
}import com.openai.client.OpenAIClient;
import com.openai.client.okhttp.OpenAIOkHttpClient;
import com.openai.models.chat.completions.*;
import com.openai.models.ReasoningEffort;
OpenAIClient client = OpenAIOkHttpClient.builder()
.baseUrl("https://synthorai.io/v1")
.apiKey("sk-syn-...")
.build();
ChatCompletion resp = client.chat().completions().create(
ChatCompletionCreateParams.builder()
.model("gpt-5.6")
// .model("minimax-m3") // uncomment this line, comment the one above
.addUserMessage("Summarize this diff")
.reasoningEffort(ReasoningEffort.MEDIUM)
.build());
System.out.println(resp.choices().get(0).message().content().orElse(""));FAQ
Which is cheaper, GPT-5.6 or MiniMax M3?
The main table shows base rates. Prompt length can change the rate for the entire request. See each model’s full rate card.
Can I A/B test GPT-5.6 against MiniMax M3 without two integrations?
Yes. Both are served through the same OpenAI-compatible endpoint with one API key. Switching is a one-line change to the model id, so you can route a fraction of traffic to each and compare bills directly.
Do GPT-5.6 and MiniMax M3 support prompt caching?
Yes. Both bill cache reads below their input rate, so warm-prefix workloads cost less than the list rates suggest. The exact cache-read rows are in the pricing table above.