google/gemma-4-31b-turbo

google/gemma-4-31b-turbo is a efficient-tier language model from Chutes. google/gemma-4-31b-turbo is an open-weights model, meaning the weights are publicly available for self-hosting, fine-tuning, and deployment on your own infrastructure — not just through Chutes's API. Gemma 4 is Google's newest open-weights family, featuring a 26B model with vision support and a 256K context window — competitive with much larger proprietary models on many benchmarks.

google/gemma-4-31b-turbo is priced at $0.12/1M input tokens and $0.37/1M output tokens. Output tokens are 3.1× more expensive than input tokens — this ratio reflects the sequential nature of autoregressive generation, which requires a separate forward pass per output token versus parallel processing of all input tokens simultaneously. At a typical usage pattern of 1,000 input tokens and 500 output tokens per call, google/gemma-4-31b-turbo costs approximately $0.30 per 1,000 API calls. Chutes does not publish a prompt caching rate for this model, so repeated long contexts are billed at the standard $0.12/1M input rate.

Its 131K-token context window handles most long-document tasks — roughly 75,000 words or a full novel — without requiring chunking or retrieval augmentation.

google/gemma-4-31b-turbo is best suited to cost, chat, open-weights. Supported capabilities include function calling / tool use for agentic workflows, streaming token output for real-time UIs. Function calling support makes it suitable for building AI agents, structured data extraction pipelines, and any workflow requiring the model to invoke external APIs or return typed JSON. When evaluating this model for a specific workload, the most important factors are: context window (does your input fit?), output price (how long are your generations?), and latency (is this interactive or batch?). The pricing table above shows how google/gemma-4-31b-turbo compares to similar models across these dimensions.

google/gemma-4-31b-turbo sits in the efficient tier — optimized for speed and cost while maintaining solid quality, ideal for high-volume or latency-sensitive workloads. As an open-weights model, google/gemma-4-31b-turbo can be self-hosted on GPU compute (see the GPU rental comparison on this site) to eliminate per-token API costs entirely — the break-even point versus API pricing depends on your volume and the GPU hourly rate. When comparing google/gemma-4-31b-turbo to alternatives, use the similar models section on this page to find models at comparable price points with different capability tradeoffs. The intelligence score (N/A/100) reflects aggregate benchmark performance — a useful proxy for general capability, though real-world performance varies significantly by task type. Always test with your specific prompts and use case before committing to a model for production.