Skip to content
No models found
OpenRouter
© 2026 OpenRouter, Inc

Product

  • Chat
  • Rankings
  • Apps
  • Models
  • Providers
  • Pricing
  • Enterprise
  • Labs

Company

  • About
  • Announcements
  • CareersHiring
  • Privacy
  • Terms of Service
  • Support
  • State of AI
  • Works With OR
  • Data

Developer

  • Documentation
  • API Reference
  • SDK
  • Status

Connect

  • Discord
  • GitHub
  • LinkedIn
  • X
  • YouTube
Favicon for google

Google: Gemma 4 26B A4B

google/gemma-4-26b-a4b-it

Compare

Gemma 4 26B A4B IT is an instruction-tuned Mixture-of-Experts (MoE) model from Google DeepMind. Despite 25.2B total parameters, only 3.8B activate per token during inference — delivering near-31B quality at a fraction of the compute cost. Supports multimodal input including text, images, and video (up to 60s at 1fps). Features a 256K token context window, native function calling, configurable thinking/reasoning mode, and structured output support. Released under Apache 2.0.

Modalities

Input Price

$0.06per 1M

Output Price

$0.33per 1M

Context

262K

Weekly Tokens

227B

Released

Apr 3, 2026

Overview
Providers
Performance
Pricing
Benchmarks
Apps
Activity
Uptime
API

Sample code and API for Gemma 4 26B A4B

OpenRouter normalizes requests and responses across providers for you.

1

Get your API key

Create an API key from your OpenRouter dashboard and set it as an environment variable:

2

Make your first request

Use google/gemma-4-26b-a4b-it with the OpenRouter API:

OpenRouter supports reasoning-enabled models that can show their step-by-step thinking process. Use the reasoning parameter in your request to enable reasoning, and access the reasoning_details array in the response to see the model's internal reasoning before the final answer. When continuing a conversation, preserve the complete reasoning_details when passing messages back to the model so it can continue reasoning from where it left off. Learn more about reasoning tokens.

In the examples below, the OpenRouter-specific headers are optional. Setting them allows your app to appear on the OpenRouter leaderboards.

Using third-party SDKs

For information about using third-party SDKs and frameworks with OpenRouter, please see our frameworks documentation.

3

Enable streaming

Add "stream": true to your request body to receive responses as server-sent events:

Endpoint

POSThttps://openrouter.ai/api/v1/chat/completions
AuthorizationBearer $OPENROUTER_API_KEY
Content-Typeapplication/json
HTTP-Refereroptional — your site URL, for rankings
X-Titleoptional — your site name, for rankings
Modelgoogle/gemma-4-26b-a4b-it

Parameters

NameTypeDefaultDescription
reasoningmap—Controls reasoning behavior for models that support thinking tokens, including whether reasoning is enabled, the reasoning effort, maximum reasoning tokens, and whether reasoning is excluded from the response.
include_reasoningboolean—Deprecated alias for reasoning.exclude.
frequency_penaltyfloat0This setting aims to control the repetition of tokens based on how often they appear in the input.
logit_biasmap—Accepts a JSON object that maps tokens (specified by their token ID in the tokenizer) to an associated bias value from -100 to 100.
max_tokensinteger—This sets the upper limit for the number of tokens the model can generate in response.
presence_penaltyfloat0Adjusts how often the model repeats specific tokens already used in the input.
seedinteger—If specified, the inferencing will sample deterministically, such that repeated requests with the same seed and parameters should return the same result.
stoparray—Stop generation immediately if the model encounter any token specified in the stop array.
temperaturefloat1This setting influences the variety in the model's responses.
top_pfloat1This setting limits the model's choices to a percentage of likely tokens: only the top tokens whose probabilities add up to P.
logprobsboolean—Whether to return log probabilities of the output tokens or not.
top_logprobsinteger—An integer between 0 and 20 specifying the number of most likely tokens to return at each token position, each with an associated log probability.