New Sign up free, 10 calls on us. Up to $1, no card needed.

Gemini 3.7 Flash vs Qwen3.8 Flash

vs

Which one, when

Pick gemini-3.7-flash when audio is part of the input mix: it accepts text, image, audio and video at $0.75 per million input tokens and $3.75 output, with a 1048576-token context. Pick qwen3.8-flash for text, image and video work at roughly 5x cheaper input and about 8x cheaper output ($0.15 and $0.47), with a 1000000-token context, double the max output at 131072 tokens, a long-context flag, and the option to turn thinking off. Both cover chat, vision, code, tools and reasoning, so the split is really audio input versus cheaper tokens and longer replies.

Benchmarks

Above averageNo peer higherGemini 3.7 Flash17 / 243 / 24Qwen3.8 Flash13 / 163 / 16
Gemini 3.7 Flash Qwen3.8 Flash other models measured peer average no peer scored higher
DeepSWE 1.1
65.3%
58.7%
BioMysteryBench hard
43.5%
N/A
OSWorld 2.0
47.9%
N/A
Finance Agent v2
59%
N/A
Harvey Lab-AA
90.7%
N/A
GPQA Diamond
N/A
91.7%
ERQA
N/A
no peer scored higher 72.3%
Agents' Last Exam Pass
26.3%
24.3%
LVBench
no peer scored higher 85.4%
76.6%

Vendor-published: Alibaba (Qwen) Anthropic ByteDance DeepSeek Google MiniMax Moonshot OpenAI Tencent Z.ai

Pricing

Gemini 3.7 Flash Qwen3.8 Flash Δ
Input / 1M tokens $0.75 $0.15
Output / 1M tokens $3.75 $0.47
Cache read / 1M tokens $0.075 $0.016 4.7×
Cache write - 1.25x -

Rates from the live catalog at build time; each model page carries the current card.

Where they sit - input price per 1M tokens across all 71 chat models on this billing unit (log scale)

Gemini 3.7 Flash · $0.75 Qwen3.8 Flash · $0.15
$0.05 · Qwen3 VL Flash $30 · GPT-5.4 Pro

Capabilities

Gemini 3.7 Flash Qwen3.8 Flash
Tool use yes yes
Thinking control yes - vendor dial not published configurable
Structured output yes yes
Prompt caching implicit + explicit implicit + explicit
Cache lifetime not published explicit: 5m, reset on hit
Minimum cached prefix 4096 tokens 1024 tokens

Specs

Gemini 3.7 Flash Qwen3.8 Flash
Input modalities text image audio video text image video
Output modalities text text
Released 2026-08-13 2026-08-27
Knowledge cutoff 2026-03 -
Context window 1M 1M
Max output 66K 131K
Thinking parameter -
  • enable_thinking
  • thinking_budget
  • preserve_thinking
Accepted values -
enable_thinking
  • true
  • false
thinking_budget
  • in tokens
preserve_thinking
  • true
  • false
Default -

on

qwen3.8-flash is hybrid thinking with thinking enabled by default, thinking_budget defaults to the 262,144-token chain maximum, and preserve_thinking is off

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.7 Flash · Qwen3.8 Flash

One prompt, both models - measured through the gateway

PROMPT Explain to a CFO, in exactly three sentences, why our LLM bill doubled after we enabled reasoning. CHECK exactly 3 sentences

Gemini 3.7 Flash passed · 3 sentences

Enabling reasoning causes the model to generate a high volume of invisible "thinking tokens" behind the scenes to deliberate and solve complex logic before delivering a final response. Because our vendor bills strictly on token volume, this additional internal computation effectively doubled our billable output per query. In short, our costs increased because we are now paying for the extra compute capacity required to produce significantly higher-accuracy answers.

out 878 tok (+799 thinking) latency 6.9 s

Qwen3.8 Flash passed · 3 sentences

Enabling reasoning makes the model spend additional output tokens to plan and validate answers before responding, and those tokens are billed. It also increases compute and latency per request, so each task consumes more capacity than a non-reasoning call. As a result, billable tokens and compute roughly doubled, directly driving the higher invoice.

out 330 tok (+262 thinking) latency 8.9 s

Instruction following (exactly three sentences - countable), audience shaping (CFO register), and the hidden-thinking billing gap the token meters below expose.

PROMPT This function is supposed to return the longest run of consecutive equal items, but callers report it is off by one on single-element inputs and misses runs that end at the last index. Fix it and explain the bug in one paragraph. CHECK fix passes tests

Gemini 3.7 Flash passed · 8/8 cases

Here is the corrected function: ```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 of the Bug The original function tracked equal adjacent transitions instead of the actual number of elements in a run, causing all non-empty run lengths to be undercounted by one (e.g., returning `0` instead of `1` for single-element lists because the loop never executes, and `1` instead of `2` for pairs). Initializing both `best` and `cur` to `1` (after handling empty inputs) and resetting `cur` to `1` on a mismatch ensures every individual element is counted as a valid run of at least length one.

out 1050 tok (+827 thinking) latency 6.4 s

Qwen3.8 Flash passed · 8/8 cases

```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 ``` The bug is that the original version counts adjacent equal pairs rather than items in a run, starting both `cur` and `best` at `0`, and it resets `cur` to `0` after a mismatch, thereby discarding the first element of the new run. That makes single-element inputs return `0`, and because every run is effectively measured in “steps” between equal elements, the last element is not counted—particularly noticeable when the longest run ends at the final index.

out 2123 tok (+1933 thinking) latency 43.8 s

Whether the fix is actually correct (runnable), explanation density, and token efficiency on a bounded task.

PROMPT Extract a JSON object with fields {company, quarter, revenue_usd_m, growth_pct, guidance} from this text. Use null for anything not stated; add no other fields. CHECK valid JSON, schema exact

Gemini 3.7 Flash passed · 5/5 fields, guidance "withheld"

```json { "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": 412, "growth_pct": null, "guidance": "withheld" } ```

out 918 tok (+858 thinking) latency 6.2 s

Qwen3.8 Flash passed · 5/5 fields, guidance null

{ "company": "Meridian Robotics", "quarter": "September quarter", "revenue_usd_m": 412, "growth_pct": 11, "guidance": null }

out 519 tok (+463 thinking) latency 10.5 s

Schema obedience (no invented fields), hallucination pressure (guidance is explicitly withheld), and structured-output path differences.

PROMPT Write a 120-word product announcement for an API gateway feature that caches prompts across providers. Forbidden words: "seamless", "unlock", "game-changer", "revolutionize", "empower". Exactly one sentence must be a question. CHECK 120 words, 0 banned words

Gemini 3.7 Flash passed · 120 words, 0 banned, 1 question

Why pay twice for identical AI queries simply because you routed them to different model vendors? Today, we introduce Universal Prompt Caching directly within our unified API gateway architecture. This capability stores repeated prompt contexts across OpenAI, Anthropic, and local models, instantly returning stored results to eliminate redundant computation fees. When your application sends an LLM request, the gateway inspects the payload, identifies semantic matches, and returns accurate cached responses in under ten milliseconds. Engineering teams can now slash inference latency by eighty percent while dramatically reducing monthly token expenditures across diverse production deployments. You retain complete privacy control, flexible cache eviction policies, and granular metrics through a single dashboard. Update your routing settings today to accelerate overall system performance.

out 2858 tok (+2718 thinking) latency 14.1 s

Qwen3.8 Flash passed · 120 words, 0 banned, 1 question

We are announcing prompt caching across providers in our API gateway. Store approved prompt outputs once and reuse them across supported model providers, cutting latency, cost, and duplicate token spend. The feature matches identical requests, checks validity, and returns cached results while preserving routing controls. Developers keep existing endpoints; the gateway manages storage, invalidation, and provider differences. This reduces noisy repeat calls, improves steady responses, and frees teams to focus on better agent workflows. OpenAI, Anthropic, Google, Mistral, and custom routes are supported. Cache hits appear in analytics with latency, token, and cost reductions visible. Check retention and privacy rules before enabling it. Ready to add cache controls to your gateway? Enable it in settings and watch spend drop now.

out 5958 tok (+5805 thinking) latency 88.8 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.7-flash",
    # model="qwen3.8-flash",  # uncomment this line, comment the one above
    messages=[{"role": "user", "content": "Summarize this diff"}],
    reasoning_effort="medium",
)
print(resp.choices[0].message.content)

Get your API key →

FAQ

Which is cheaper, Gemini 3.7 Flash or Qwen3.8 Flash?

Qwen3.8 Flash is cheaper on input / 1m tokens ($0.15 vs $0.75, 5.0× apart). Other rows may point the other way - the table above carries the full card, and real cost depends on your mix.

Can I A/B test Gemini 3.7 Flash against Qwen3.8 Flash without two integrations?

Yes. Both are served through the same OpenAI-compatible endpoint with one API key - switching is a one-line model-string change, so you can route a fraction of traffic to each and compare bills directly.

Do Gemini 3.7 Flash and Qwen3.8 Flash support prompt caching?

Yes - both bill cached 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.

Related comparisons

From our measured studies