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

Claude Sonnet 5 vs Gemini 3.6 Flash

vs

Which one, when — curated verdict, not a benchmark table

Pick claude-sonnet-5 when you need explicit thinking and reasoning that you can also switch off, plus room for long answers at up to 128,000 output tokens, and you can accept text and image input only at $2 per million input and $10 per million output. Pick gemini-3.6-flash for video and audio input on a similar ~1,048,576-token context at $1.5 input, $7.5 output and $0.15 cache reads, with audio metered separately at $5 per million audio tokens; note its thinking cannot be disabled and max output is 65,536. Roughly, Sonnet 5 costs about 1.33x more per token in both directions.

Pricing

Claude Sonnet 5 Gemini 3.6 Flash Δ
Input / 1M tokens $2 $1.5 1.3×
Output / 1M tokens $10 $7.5 1.3×
Cache read / 1M tokens $0.2 $0.15 1.3×
Cache write 1.25x (5m) / 2x (1h)

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 63 chat models on this billing unit (log scale)

Capabilities

Claude Sonnet 5 Gemini 3.6 Flash
Tool use yes yes
Thinking control configurable always on
Structured output yes yes
Prompt caching explicit (you mark the prefix) implicit + explicit
Cache lifetime 5m default, 1h option not published
Minimum cached prefix 1024 tokens 4096 tokens

Specs

Claude Sonnet 5 Gemini 3.6 Flash
Input modalities text image text image audio video
Output modalities text text
Released 2026-06-30
Knowledge cutoff 2026-01 2026-03
Context window 1M 1M
Max output 128K 66K
Thinking parameter
  • thinking.type "adaptive"
  • output_config.effort
thinkingLevel
Accepted values
thinking.type
  • adaptive
  • disabled
effort
  • low
  • medium
  • high
  • xhigh
  • max

"enabled" returns 400

  • minimal
  • low
  • medium
  • high
Default

thinking on (adaptive)

effort
  • high
medium

Specs are transcribed from each vendor’s documentation; a row a vendor does not publish is left out rather than inferred. Full sources: Claude Sonnet 5 · Gemini 3.6 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

Claude Sonnet 5 passed · 3 sentences

Reasoning mode works by having the model generate extended internal "thinking" steps before producing its final answer, and since we're billed on total tokens, that hidden reasoning text adds significantly to what we pay for—even though you never see it in the output. This is different from simply getting longer visible responses; the model is essentially "showing its work" behind the scenes, and complex prompts can trigger thousands of extra reasoning tokens per request. The upside is improved accuracy on complex tasks, but if we want to control costs, we should selectively enable reasoning only for queries that truly need it, rather than applying it universally.

out 194 tok latency 4.3 s

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

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

Claude Sonnet 5 passed · 8/8 cases

## The Bug The function has two related off-by-one issues rooted in the same cause: `cur` and `best` are initialized to `0` instead of `1`, treating run lengths as the number of *matches* between adjacent elements rather than the number of *elements* in the run. This means a single-element input never enters the loop (since `range(1, 1)` is empty) and returns `0` instead of the correct answer of `1`. It also means that for any input, the run length is undercounted by exactly one — a run of 3 equal elements only produces 2 "match" increments, so `best` ends up as 2 instead of 3. The claim that it "misses runs that end at the last index" is actually a symptom of this same undercount: the logic does update `best` correctly on every iteration (including the last), but because it's counting matches instead of elements, the final reported value is always one less than the true longest run. […]

out 536 tok latency 7.1 s

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

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

Claude Sonnet 5 passed · 5/5 fields, guidance null

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

out 348 tok latency 5.3 s

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

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

Claude Sonnet 5 passed · 123 words, 0 banned, 1 question

## Introducing Cross-Provider Prompt Caching We're rolling out a new caching layer for our API gateway that works across every major LLM provider you connect through it. Instead of resending identical prompts and paying full price each time, the gateway recognizes repeated requests and serves cached responses in milliseconds—regardless of whether you're routing to OpenAI, Anthropic, or Google. What does this mean for your bill and your latency? Both drop, often significantly, especially for teams running high-volume, repetitive workloads like customer support bots or batch content generation. The cache is configurable per route, with adjustable TTLs and invalidation rules, so you stay in control of freshness versus cost. Available now for all Pro and Enterprise plans. Check your dashboard to enable it today.

out 259 tok latency 4.8 s

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

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="claude-sonnet-5",
    # model="gemini-3.6-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 an API key →

FAQ

Which is cheaper, Claude Sonnet 5 or Gemini 3.6 Flash?

Gemini 3.6 Flash is cheaper on input / 1m tokens ($1.5 vs $2, 1.3× 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 Claude Sonnet 5 against Gemini 3.6 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 Claude Sonnet 5 and Gemini 3.6 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