Free to start

Google: Gemma 4 26B A4B vs Tencent: Hy3

Try both on us. Starter credit covers your first requests, then one key routes Gemma 4 26B A4B and Hy3. 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, more Credits provider routes and the lower measured p50 time to first token. Their context windows are the same size.

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

$0.6963/1MTencent: Hy3 cheapest route

1379 msGoogle: Gemma 4 26B A4B fastest measured p50 TTFT via nextbit-eu

2382 msTencent: Hy3 fastest measured p50 TTFT via tencent

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 Tencent: Hy3

Model idgoogle/gemma-4-26b-a4b-ittencent/hy3

Publisher Google AI Studio Tencent Cloud TokenHub

AI IQ IQ 99#127 IQ 99#128

Context262,144 tokens262,144 tokens

Credits provider routes104

Cheapest route$0.41145/1M$0.6963/1M

Cached input$0.04853/1M to $0.05275/1M$0.034815/1M to $0.05275/1M

Privacy posturehas ZDR routeprovider posture varies

Fastest measured p50 TTFT1379 ms via nextbit-eu2382 ms via tencent

Highest measured throughputnot enough datanot enough data

Recent route uptime range100.00%100.00%

Modes chat decide chat

Google: Gemma 4 26B A4B routes

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

Tencent: Hy3 routes

Overview4 Credits routes
PricingInput, cached input, and output rates
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
Tencent: Hy3 vs Z.ai: GLM 5.337 combined provider routes
DeepSeek: DeepSeek V4 Flash 0731 vs Google: Gemma 4 26B A4B 36 combined provider routes
Tencent: Hy3 vs Z.ai: GLM 5.236 combined provider routes
Tencent: Hy3 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.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 Tencent: Hy3?

Google: Gemma 4 26B A4B has the lower published input-plus-output rate, more Credits provider routes and the lower measured p50 time to first token. Their context windows are the same size.

Is Google: Gemma 4 26B A4B or Tencent: Hy3 cheaper?

The current cheapest TrustedRouter route is $0.41145/1M for Google: Gemma 4 26B A4B and $0.6963/1M for Tencent: Hy3. The comparison uses current catalog prices and updates as provider pricing changes.

Is Google: Gemma 4 26B A4B or Tencent: Hy3 faster?

Current measured p50 time to first token is 1379 ms for Google: Gemma 4 26B A4B and 2382 ms for Tencent: Hy3. These are routed probe measurements, not vendor-advertised speeds, and update as new samples arrive.

Can I test Google: Gemma 4 26B A4B and Tencent: Hy3 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 tencent/hy3. This makes side-by-side evals possible without maintaining two provider integrations.