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

Hy3 vs Qwen3.5-4B

Hy3 scores 62.6 (B) on agent readiness against Qwen3.5-4B's 61.2 (C), and leads in 4 of 5 scored categories. Qwen3.5-4B leads on reach. 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

Hy3 B

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

Ahead on

  • Risk, 60 against 55
  • Agent interface, 75 against 70
  • Documentation and upkeep, 56 against 34

Watch for

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

Qwen3.5-4B C

Best for Agents that want a cheap local helper for tool calls, short reasoning and reading images on a laptop or small GPU

Ahead on

  • Reach, 85 against 70

Watch for

No quantised build from Alibaba for this size

Score by category

CategoryWeight this runHy3Qwen3.5-4BEdge
Capability35%355753Hy3 +4
Reach25%257085Qwen3.5-4B +15
Risk20%206055Hy3 +5
Agent interface10%107570Hy3 +5
Documentation and upkeep10%105634Hy3 +22
Negative events≤1500
TotalB 62.6/100C 61.2/100

Facts side by side

FactHy3Qwen3.5-4B
KindOpen-weight modelOpen-weight model
VendorTencent (Hy team)Alibaba (Qwen team)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-07-202026-03-02
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 reviews2.8/5 (4)3/5 (4)

Verdicts

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.

Qwen3.5-4B

A small vision-language cousin for tool calls, light agent steps and image or video reading on almost any machine, with switchable thinking. Ollama's 3.3 GB build or the 9.3 GB BF16 files run in every major runtime under plain Apache 2.0. The main risks are no safety results, no structured-output guarantee and no answers from Alibaba since March.

Before you call either

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

Qwen3.5-4B

  1. Smallest start is ollama run qwen3.5:4b (Q4_K_M, about 4 GB with context)
  2. Full precision vllm serve Qwen/Qwen3.5-4B --port 8000 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder
  3. Turn thinking off with "chat_template_kwargs": {"enable_thinking": false} in the request body, since it's on by default and /think and /nothink aren't supported
  4. There's no generation_config.json, so pass the card's sampling yourself, for example temperature=0.7, top_p=0.8, top_k=20, presence_penalty=1.5 without thinking
  5. Keep the context at 128K or more if you rely on thinking, and turn on YaRN only past 262,144 tokens
  6. Validate any JSON it returns, since structured output isn't documented

Questions

Which is better for AI agents, Hy3 or Qwen3.5-4B?

Hy3 scores 62.6 (B) on agent readiness against Qwen3.5-4B's 61.2 (C), and leads in 4 of 5 scored categories. Qwen3.5-4B leads on reach.

Other comparisons with Hy3 or Qwen3.5-4B

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.