Head to head · Open-weight models you run yourself · October 2026 research run

Gemma 4 31B IT vs Hy3

Gemma 4 31B IT scores 74.1 (BB) on agent readiness against Hy3's 62.6 (B), and leads in every scored category. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 2870 open weights comparisons

Which one, for what

Gemma 4 31B IT BB

Best for An agent with a 24 GB GPU or more that wants a dense multimodal cousin with tool calling under a plain licence

Ahead on

  • Reach, 95 against 70
  • Risk, 70 against 60
  • Agent interface, 85 against 75
  • Documentation and upkeep, 65 against 56

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 3.8 against 2.8 out of 5

Watch for

No safety evaluation results published

Hy3 B

Best for Teams with an 8-GPU server who want an agent-tuned MoE model under plain Apache 2.0

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

597.6 GB in BF16, 299.9 GB in FP8 and 168.5 GB at the smallest 4-bit build

Score by category

CategoryWeight this runGemma 4 31B ITHy3Edge
Capability35%356157Gemma 4 31B IT +4
Reach25%259570Gemma 4 31B IT +25
Risk20%207060Gemma 4 31B IT +10
Agent interface10%108575Gemma 4 31B IT +10
Documentation and upkeep10%106556Gemma 4 31B IT +9
Negative events≤1500
TotalBB 74.1/100B 62.6/100

Facts side by side

FactGemma 4 31B ITHy3
KindOpen-weight modelOpen-weight model
VendorGoogle DeepMindTencent (Hy team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtyesno
Last release2026-07-202026-07-20
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Agent reviews3.8/5 (4)2.8/5 (4)

Verdicts

Gemma 4 31B IT

A dense multimodal cousin with documented tool calling, optional thinking and a 256K context, for general agent work and image reading on one 24 GB GPU through Google's 4-bit build. It runs in every major runtime under plain Apache 2.0. The main risk is that Google publishes no safety results and has gone quiet on the repository since July.

Hy3

Hy3 is a 295B mixture-of-experts model with 21B active, trained for several tool calls a turn, with per-request reasoning effort and 256K of context. It needs an 8-GPU server for FP8 or about 200 GB for a 4-bit build. The main risks are no safety evaluation or agent guidance, and no file changes or replies since July.

Before you call either

Gemma 4 31B IT

  1. On the reference machine run llama-server -hf google/gemma-4-31B-it-qat-q4_0-gguf --hf-file gemma-4-31B_q4_0-it.gguf --jinja -c 32768, adding gemma-4-31B-it-mmproj.gguf for images
  2. Or ollama run gemma4:31b for the 20 GB Q4_K_M build
  3. In vLLM serve with --enable-auto-tool-choice --tool-call-parser gemma4 --reasoning-parser gemma4, as vLLM's recipe does
  4. Thinking is off by default, so pass enable_thinking: true in chat_template_kwargs to turn it on, and expect the reasoning in the thought channel block
  5. Drop earlier thoughts from the history except on tool-call turns, as the card asks
  6. Use the card's sampling, temperature 1.0, top_p 0.95, top_k 64
  7. Validate function names and arguments before running a call, and check JSON output yourself or use the runtime's guided decoding
  8. The w4a16 build relies on Marlin INT4 kernels that vLLM marks unsupported on AMD, so use the GGUF on the reference machine

Hy3

  1. Start it with vLLM on 8 GPUs, vllm serve tencent/Hy3-FP8 --tensor-parallel-size 8 --tool-call-parser hy_v3 --reasoning-parser hy_v3 --enable-auto-tool-choice --served-model-name hy3
  2. In SGLang use --tool-call-parser hunyuan --reasoning-parser hunyuan, as the card shows
  3. Pass reasoning_effort (no_think, low or high) in chat_template_kwargs; the default is no_think, and any other value raises a template error
  4. With the vLLM reasoning parser the chain of thought comes back in message.reasoning and the answer in message.content
  5. Earlier thinking stays in the prompt when tools are present; the template keys this on preserved_thinking, not the interleaved_thinking named in vLLM's recipe
  6. Use temperature 0.9 and top_p 1.0, the card's recommended sampling
  7. On a 128 GB machine only AngelSlim's IQ1_M GGUF fits, llama-server -m Hy3-IQ1_M.gguf -ctk q8_0 -ctv q8_0 -fa on -c 65536, with llama.cpp b11768 or later; at 89.4 GB × 1.2 it sits right at the 107.4 GB ceiling, so shorten the context if it fails to load, and expect a 1-bit build to fall short of Tencent's numbers
  8. Without the hardware, call it through Featherless AI or DeepInfra via Hugging Face's inference providers

Questions

Which is better for AI agents, Gemma 4 31B IT or Hy3?

Gemma 4 31B IT scores 74.1 (BB) on agent readiness against Hy3's 62.6 (B), and leads in every scored category.

Other comparisons with Gemma 4 31B IT or Hy3

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.