Free to start

Google: Gemma 4 26B A4B vs Xiaomi: MiMo-V2.5

Try both on us. Starter credit covers your first requests, then one key routes Gemma 4 26B A4B and MiMo-V2.5. Switch by changing the model name.

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 26B A4B has the lower published input-plus-output rate and more Credits provider routes. MiMo-V2.5 has the larger context window. There is not enough recent probe data to compare speed.

$0.41145/1MGoogle: Gemma 4 26B A4B cheapest route

$0.4431/1MXiaomi: MiMo-V2.5 cheapest route

not enough dataGoogle: Gemma 4 26B A4B fastest measured p50 TTFT

not enough dataXiaomi: MiMo-V2.5 fastest measured p50 TTFT

The price comparison adds each route's rate for one million input tokens and one million output tokens; your cost depends on your input/output mix. 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 26B A4B Xiaomi: MiMo-V2.5

Model idgoogle/gemma-4-26b-a4b-itxiaomi/mimo-v2.5

Publisher Google AI Studio Xiaomi MiMo

AI IQ IQ 99#127 IQ 108#84

Context262,144 tokens1,048,576 tokens

Credits provider routes104

Cheapest route$0.41145/1M$0.4431/1M

Cached input$0.04853/1M to $0.05275/1M$0.01/1M to $0.104973/1M

Privacy posturehas ZDR routeprovider posture varies

Fastest measured p50 TTFTnot enough datanot enough data

Highest measured throughputnot enough datanot enough data

Recent route uptime rangenot enough datanot enough data

Modes chat decide chat

Google: Gemma 4 26B A4B routes

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

Xiaomi: MiMo-V2.5 routes

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

Related comparisons

Browse every comparison

Google: Gemma 4 26B A4B vs Z.ai: GLM 5.343 combined provider routes
Google: Gemma 4 26B A4B vs Z.ai: GLM 5.242 combined provider routes
Google: Gemma 4 26B A4B vs Z.ai: GLM 5.3 Flash42 combined provider routes
Google: Gemma 4 26B A4B vs MoonshotAI: Kimi K338 combined provider routes
Xiaomi: MiMo-V2.5 vs Z.ai: GLM 5.337 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs Google: Gemma 4 26B A4B 36 combined provider routes
Xiaomi: MiMo-V2.5 vs Z.ai: GLM 5.236 combined provider routes
Xiaomi: MiMo-V2.5 vs Z.ai: GLM 5.3 Flash36 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-azure.trustedrouter.com/v1",
    api_key="sk-tr-v1-..."
)

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

Questions

Which should I use, Google: Gemma 4 26B A4B or Xiaomi: MiMo-V2.5?

Is Google: Gemma 4 26B A4B or Xiaomi: MiMo-V2.5 cheaper?

The current cheapest TrustedRouter route is $0.41145/1M for Google: Gemma 4 26B A4B and $0.4431/1M for Xiaomi: MiMo-V2.5. The comparison uses current catalog prices and updates as provider pricing changes.

Is Google: Gemma 4 26B A4B or Xiaomi: MiMo-V2.5 faster?

Current measured p50 time to first token is not enough data for Google: Gemma 4 26B A4B and not enough data for Xiaomi: MiMo-V2.5. These are routed probe measurements, not vendor-advertised speeds, and update as new samples arrive.

Can I test Google: Gemma 4 26B A4B and Xiaomi: MiMo-V2.5 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-26b-a4b-it and xiaomi/mimo-v2.5. This makes side-by-side evals possible without maintaining two provider integrations.