OpenAI compatible API · Attested · Public status

Google: Gemma 4 31B vs @cf/qwen/qwen2.5-coder-32b-instruct

Google: Gemma 4 31B vs @cf/qwen/qwen2.5-coder-32b-instruct: compare current API pricing, context, provider routes, privacy, p50 latency, and OpenAI-compatible access.

Verify gateway

Onebase URL to migrate

100sof models and routes

0prompt or output logs. Always.

Compare routesProviders, price, context, and policy posture in one view.

Use auto when uptime mattersKeep a primary model and let fallback handle provider failures.

Same API shapeUse the OpenAI client and set the model you want.

Practical read

Monthly evidence

Google: Gemma 4 31B has the lower cheapest prompt+completion route on TrustedRouter. Google: Gemma 4 31B has more provider fallback routes, while Google: Gemma 4 31B has the larger context window. Probe-backed speed data is shown when enough recent samples exist.

$0.5064/1MGoogle: Gemma 4 31B cheapest route

$1.7513/1M@cf/qwen/qwen2.5-coder-32b-instruct cheapest route

1033 msGoogle: Gemma 4 31B fastest measured p50 TTFT via digitalocean

not enough data@cf/qwen/qwen2.5-coder-32b-instruct fastest measured p50 TTFT

Prices and live route measurements can change. Use the monthly reports when you need a stable evidence window, then run a small task-specific eval before choosing a production default.

Google: Gemma 4 31B@cf/qwen/qwen2.5-coder-32b-instruct

Model idgoogle/gemma-4-31b-itqwen/qwen2.5-coder-32b-instruct

Publisher Google AI Studio Cloudflare Workers AI

AI IQ IQ 101#75 —

Context262,144 tokens32,768 tokens

Provider routes271

Cheapest route$0.5064/1M$1.7513/1M

Privacy posturehas provider E2EE routeprovider posture varies

Fastest measured p50 TTFT1033 ms via digitaloceannot enough data

Highest measured throughput332 tok/s via cerebrasnot enough data

Recent route uptime range100.00%100.00%

Modes chat chat

Google: Gemma 4 31B routes

Overview27 endpoints
PricingPrompt and completion rates
ProvidersAll serving providers

@cf/qwen/qwen2.5-coder-32b-instruct routes

Overview1 endpoints

Related comparisons

Browse every comparison

Google: Gemma 4 31B vs Z.ai: GLM 5.279 combined provider routes
Google: Gemma 4 31B vs MoonshotAI: Kimi K364 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs Google: Gemma 4 31B60 combined provider routes
Google: Gemma 4 31B vs MoonshotAI: Kimi K2.658 combined provider routes
Google: Gemma 4 31B vs OpenAI: gpt-oss-120b58 combined provider routes
DeepSeek: DeepSeek V4 Flash 0423 vs Google: Gemma 4 31B56 combined provider routes
DeepSeek: DeepSeek V4 Pro 0423 vs Google: Gemma 4 31B55 combined provider routes
Google: Gemma 4 31B vs Z.ai: GLM 5.150 combined provider routes

Production choice

Pick a default model. Keep fallback enabled.

TrustedRouter is useful when you know the model you want, but still need provider rollover, budget limits, usage records, and a prompt path you can verify.

OpenAI clientPython

client = OpenAI(
    base_url="https://api.trustedrouter.com/v1",
    api_key="sk-tr-v1-..."
)

response = client.chat.completions.create(
    model="google/gemma-4-31b-it",
    messages=messages,
)

Questions

Which should I use, Google: Gemma 4 31B or @cf/qwen/qwen2.5-coder-32b-instruct?

Is Google: Gemma 4 31B or @cf/qwen/qwen2.5-coder-32b-instruct cheaper?

The current cheapest TrustedRouter route is $0.5064/1M for Google: Gemma 4 31B and $1.7513/1M for @cf/qwen/qwen2.5-coder-32b-instruct. The comparison uses current catalog prices and updates as provider pricing changes.

Is Google: Gemma 4 31B or @cf/qwen/qwen2.5-coder-32b-instruct faster?

Current measured p50 time to first token is 1033 ms for Google: Gemma 4 31B and not enough data for @cf/qwen/qwen2.5-coder-32b-instruct. These are routed probe measurements, not vendor-advertised speeds, and update as new samples arrive.

Can I test Google: Gemma 4 31B and @cf/qwen/qwen2.5-coder-32b-instruct with the same API?

Yes. Use the same OpenAI-compatible TrustedRouter base URL and API key, then change only the model id between google/gemma-4-31b-it and qwen/qwen2.5-coder-32b-instruct. This makes side-by-side evals possible without maintaining two provider integrations.