OpenAI compatible API · Attested · Public status

Google: Gemma 4 31B vs Thinking Machines: Inkling

Google: Gemma 4 31B vs Thinking Machines: Inkling: 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 Thinking Machines: Inkling has the larger context window. Current TrustedRouter probes show Google: Gemma 4 31B with the lower p50 TTFT.

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

$5.275/1MThinking Machines: Inkling cheapest route

1094 msGoogle: Gemma 4 31B fastest measured p50 TTFT via friendli

1410 msThinking Machines: Inkling fastest measured p50 TTFT via together

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 31BThinking Machines: Inkling

Model idgoogle/gemma-4-31b-itthinkingmachines/inkling

Publisher Google AI Studio DeepInfra

AI IQ IQ 101#83 IQ 108#63

Context262,144 tokens524,288 tokens

Credits provider routes134

Cheapest route$0.4642/1M$5.275/1M

Cached input$0.02743/1M to $0.1477/1M$0.1688/1M to $0.17935/1M

Privacy posturehas provider E2EE routehas ZDR route

Fastest measured p50 TTFT1094 ms via friendli1410 ms via together

Highest measured throughput114 tok/s via tinfoilnot enough data

Recent route uptime range0.00% to 100.00%100.00%

Modes chat chat

Google: Gemma 4 31B routes

Overview13 Credits routes
PricingInput, cached input, and output rates
ProvidersAll serving providers

Thinking Machines: Inkling routes

Overview4 Credits routes
PricingInput, cached input, and output rates
ProvidersAll serving providers

Related comparisons

Browse every comparison

Google: Gemma 4 31B vs Z.ai: GLM 5.244 combined provider routes
Google: Gemma 4 31B vs MoonshotAI: Kimi K336 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs Google: Gemma 4 31B35 combined provider routes
Google: Gemma 4 31B vs Z.ai: GLM 5.335 combined provider routes
Thinking Machines: Inkling vs Z.ai: GLM 5.235 combined provider routes
Google: Gemma 4 31B vs Z.ai: GLM 5.3 Flash33 combined provider routes
Google: Gemma 4 31B vs MoonshotAI: Kimi K2.632 combined provider routes
Google: Gemma 4 31B vs OpenAI: gpt-oss-120b32 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 Thinking Machines: Inkling?

Is Google: Gemma 4 31B or Thinking Machines: Inkling cheaper?

The current cheapest TrustedRouter route is $0.4642/1M for Google: Gemma 4 31B and $5.275/1M for Thinking Machines: Inkling. The comparison uses current catalog prices and updates as provider pricing changes.

Is Google: Gemma 4 31B or Thinking Machines: Inkling faster?

Current measured p50 time to first token is 1094 ms for Google: Gemma 4 31B and 1410 ms for Thinking Machines: Inkling. These are routed probe measurements, not vendor-advertised speeds, and update as new samples arrive.

Can I test Google: Gemma 4 31B and Thinking Machines: Inkling 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 thinkingmachines/inkling. This makes side-by-side evals possible without maintaining two provider integrations.