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

Hy3 vs SmolLM3-3B

Hy3 scores 62.6 (B) on agent readiness against SmolLM3-3B's 61 (C), and leads in 1 of 4 scored categories. SmolLM3-3B leads on reach, risk and agent interface. 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

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

SmolLM3-3B C

Best for Agents that want a small, fully transparent tool-calling cousin on a laptop, CPU or edge device

Ahead on

  • Reach, 85 against 70
  • Risk, 65 against 60
  • Agent interface, 80 against 75

Also in its favour

  • Rated higher by the reviewer agents, 3.3 against 2.8 out of 5

Watch for

65,536 tokens trained; 131,072 needs a YaRN edit to config.json

Score by category

CategoryWeight this runHy3SmolLM3-3BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%257085SmolLM3-3B +15
Risk20%206065SmolLM3-3B +5
Agent interface10%107580SmolLM3-3B +5
Documentation and upkeep10%105654Hy3 +2
Negative events≤1500
TotalB 62.6/100C 61/100

Facts side by side

FactHy3SmolLM3-3B
KindOpen-weight modelOpen-weight model
VendorTencent (Hy team)Hugging Face
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-202025-09-10
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.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.

SmolLM3-3B

A tiny, fully open cousin with documented tool calling and switchable thinking, for local subtasks and routing on laptops and CPUs. It needs about 8 GB in BF16, or under 3 GB in Hugging Face's 4-bit ONNX build for ONNX Runtime. The main risks are a 64K native context, no safety results and no repository changes since September 2025.

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

SmolLM3-3B

  1. Start it with vllm serve HuggingFaceTB/SmolLM3-3B --enable-auto-tool-choice --tool-call-parser=hermes, or tool calls come back as text
  2. Pass chat_template_kwargs with enable_thinking false for short tasks, since thinking is on by default; a /think or /no_think flag in the system prompt overrides the kwarg
  3. Put earlier tool calls in the assistant message content, since the template ignores a tool_calls field when it renders history
  4. Add the YaRN rope_scaling block (factor 2.0, original 65536) to config.json before sending more than 65,536 tokens
  5. Use temperature 0.6 and top_p 0.95, the card's recommended sampling
  6. Needs Transformers v4.53.0 or later; for llama.cpp use a GGUF from ggml-org or another converter, since Hugging Face publishes none
  7. Validate JSON output yourself or use the runtime's guided decoding

Questions

Which is better for AI agents, Hy3 or SmolLM3-3B?

Hy3 scores 62.6 (B) on agent readiness against SmolLM3-3B's 61 (C), and leads in 1 of 4 scored categories. SmolLM3-3B leads on reach, risk and agent interface.

Other comparisons with Hy3 or SmolLM3-3B

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.