Gemini 3.6 Flash vs GPT-5.6
Which one, when
gemini-3.6-flash costs about 5.3x less than gpt-5.6 on input ($0.75 against $4), output ($3.75 against $20) and cache reads ($0.075 against $0.4), and it accepts video and audio as well as text and image. Pick it for high-volume or multimodal work. Pick gpt-5.6 for its reasoning capability, the option to disable thinking (gemini-3.6-flash cannot), or up to 128000 output tokens against 65536; the contexts of 1048576 and 1050000 tokens are effectively the same.
Benchmarks
14 measured on both.
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
| Gemini 3.6 Flash | GPT-5.6 | Δ | |
|---|---|---|---|
| Input / 1M tokens | $0.75 | $4 | 0.19× |
| Output / 1M tokens | $3.75 | $20 | 0.19× |
| Cache read / 1M tokens | $0.075 | $0.4 | 0.19× |
| Cache write | - | 1.25x (30m) / 2.5x (12h) | - |
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
| Gemini 3.6 Flash | GPT-5.6 | |
|---|---|---|
| Tool calling | yes | yes |
| Thinking control | always on | configurable |
| Structured output | yes | yes |
| Prompt caching | implicit + explicit | implicit + explicit |
| Cache lifetime | not published | at least 30m by default, 12h option on the Responses API |
| Minimum cached prefix | 4,096 tokens | 1,024 tokens |
Specs
| Gemini 3.6 Flash | GPT-5.6 | |
|---|---|---|
| Input modalities | text image audio video | text image |
| Output modalities | text | text |
| Released | 2026-07-21 | 2026-07-09 |
| Knowledge cutoff | 2026-03 | 2026-02 |
| Context window | 1,048,576 | 1,050,000 |
| Max output | 65,536 | 128,000 |
| Thinking parameter | thinkingLevel | reasoning.effort |
| Accepted values |
| reasoning.effort
|
| Default | medium | medium |
Specs are transcribed from each vendor’s documentation; a row a vendor does not publish is left out rather than inferred. Full sources: Gemini 3.6 Flash · GPT-5.6
One prompt, both models, measured through the gateway
Gemini 3.6 Flash passed · 3 sentences
Enabling reasoning causes the model to generate thousands of internal "thinking" tokens behind the scenes to process logic before delivering the final response. Because our vendor bills us for every token generated—including these intermediate processing steps—our billable output volume per query surged significantly. Since output tokens carry a much higher unit cost than input tokens, this jump in processing volume directly doubled our overall spend.
out 893 tok (+816 thinking) latency 4.7 s
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
Instruction following (exactly three sentences, so countable), audience shaping (CFO register), and the hidden-thinking billing gap the token meters below expose.
Gemini 3.6 Flash passed · 8/8 cases
Here is the fixed function along with an explanation of the bugs: ```python def longest_run(xs): if not xs: return 0 best = 1 cur = 1 for i in range(1, len(xs)): if xs[i] == xs[i - 1]: cur += 1 else: cur = 1 best = max(best, cur) return best ``` ### Explanation The original function initialized `cur` and `best` to `0` and incremented `cur` on matching adjacent items, which meant it was counting identical adjacent *pairs* rather than the total number of *elements* in a run. This caused single-element inputs to skip the loop and return `0` instead of `1`, and undercounted all run lengths by 1 (for example, a run of two items at the end of the list resulted in `cur = 1`). […]
out 2034 tok (+1768 thinking) latency 10.0 s
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
Whether the fix is actually correct (runnable), explanation density, and token efficiency on a bounded task.
Gemini 3.6 Flash passed · 5/5 fields, guidance "withheld"
```json { "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": 412, "growth_pct": null, "guidance": "withheld" } ```
out 2843 tok (+2783 thinking) latency 13.1 s
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
Schema obedience (no invented fields), hallucination pressure (guidance is explicitly withheld), and structured-output path differences.
Gemini 3.6 Flash missed · 60 words, 0 banned, 0 questions
72: reducing 73: your 74: monthly 75: token 76: spend. S6 (21): 77: You 78: can 79: easily 80: set 81: custom 82: expiration 83: rules, 84: configure 85: TTL 86: settings, 87: and 88: manage 89: cache 90: invalidation 91: across 92: all 93: vendors 94: from 95: one 96: centralized 97: dashboard. S7 (23): 98: Start 99: optimizing […]
out 4092 tok (+3929 thinking) latency 16.3 s
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
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="gemini-3.6-flash",
# model="gpt-5.6", # uncomment this line, comment the one above
messages=[{"role": "user", "content": "Summarize this diff"}],
)
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: "gemini-3.6-flash",
// model: "gpt-5.6", // uncomment this line, comment the one above
messages: [{ role: "user", content: "Summarize this diff" }],
});
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": "gemini-3.6-flash",
# "model": "gpt-5.6", # uncomment this line, comment the one above
"messages": [{"role": "user", "content": "Hello"}]
}'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: "gemini-3.6-flash",
// Model: "gpt-5.6", // uncomment this line, comment the one above
Messages: []openai.ChatCompletionMessageParamUnion{
openai.UserMessage("Summarize this diff"),
},
})
fmt.Println(resp.Choices[0].Message.Content)
}import com.openai.client.OpenAIClient;
import com.openai.client.okhttp.OpenAIOkHttpClient;
import com.openai.models.chat.completions.*;
OpenAIClient client = OpenAIOkHttpClient.builder()
.baseUrl("https://synthorai.io/v1")
.apiKey("sk-syn-...")
.build();
ChatCompletion resp = client.chat().completions().create(
ChatCompletionCreateParams.builder()
.model("gemini-3.6-flash")
// .model("gpt-5.6") // uncomment this line, comment the one above
.addUserMessage("Summarize this diff")
.build());
System.out.println(resp.choices().get(0).message().content().orElse(""));FAQ
Which is cheaper, Gemini 3.6 Flash or GPT-5.6?
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 Gemini 3.6 Flash against GPT-5.6 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 Gemini 3.6 Flash and GPT-5.6 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.