Auto-generated comparison

Google: Gemma 3 27B vs Inception: Mercury Coder

Google: Gemma 3 27B wins on 4 of 6 axes — pricing and capability skew in its favour for most workloads.

Side-by-side comparison

CapabilityGoogle: Gemma 3 27BInception: Mercury CoderWinner
Context window
Maximum number of input tokens the model can attend to in a single request.
131K128K🏆 Google: Gemma 3 27B
Input price (per 1M)
Cost per million input tokens billed by the provider.
$0.08$0.25🏆 Google: Gemma 3 27B
Output price (per 1M)
Cost per million output tokens billed by the provider.
$0.45$0.75🏆 Google: Gemma 3 27B
Tool / function calling
First-class support for emitting structured tool calls.
YesYesTie
Vision input
Accepts image inputs alongside text.
Yes🏆 Google: Gemma 3 27B
Reasoning mode
Internal chain-of-thought / extended-thinking support.
Tie

Frequently asked questions

Is Google: Gemma 3 27B better than Inception: Mercury Coder?

Google: Gemma 3 27B wins on 4 of 6 axes — pricing and capability skew in its favour for most workloads.

What's the price difference between Google: Gemma 3 27B and Inception: Mercury Coder?

Input: $0.08 vs $0.25 per 1M tokens. Output: $0.45 vs $0.75 per 1M tokens.

What context windows do Google: Gemma 3 27B and Inception: Mercury Coder support?

Google: Gemma 3 27B supports up to 131K tokens. Inception: Mercury Coder supports up to 128K tokens.

Do both Google: Gemma 3 27B and Inception: Mercury Coder support tool calling?

Google: Gemma 3 27B: yes. Inception: Mercury Coder: yes.

Compare Google: Gemma 3 27B with other models

Compare Inception: Mercury Coder with other models