Head to head · Open-weight models you run yourself · October 2026 research run
Hy3 vs WeVisOne-VL-4B
Hy3 scores 62.6 (B) on agent readiness against WeVisOne-VL-4B's 61 (C), and leads in 3 of 4 scored categories. Both do open-weight models you run yourself.
Best open-weight models you download and run yourself for AI agents · All 6359 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 48
Watch for
597.6 GB in BF16, 299.9 GB in FP8 and 168.5 GB at the smallest 4-bit build
Best for Agents that need to locate, count or cut out objects in images on a small GPU, under a permissive licence
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
The pixel decoder ships as a pickle file
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Documentation and upkeep Hy3 +8
Hy3 56
The model card earns 11, covering intended use, architecture, parameters and context but not limitations, languages or a knowledge cut-off. Training data earns 5 for a general statement with no cut-off. The last change earns 10, a config.json edit on 20 July and AngelSlim uploads on 21 July, within 180 days on 2 November 2026; the line drops to 5 after 17 January 2027 unless the files change. Responsiveness earns 10, with Tencent replies on 7 of 19 discussions and none since 22 July. Version policy earns the full 10, since the preview stays in its own repository and the card dates it and says what changed. File health earns 10, with files that agree and no broken-file report waiting.
WeVisOne-VL-4B 48
Model card 8, Intended use, limitations and the architecture are on the card. Training data 5, A general description in the README of a data engine and over 100 million annotated images, with no sources named and no cut-off. Last change 20, the last commit, on 27 October 2026, added links to the paper and project page, 14 days before this check. Responsiveness 0, Neither of the 2 discussions that aren't pull requests (23 and 26 October 2026) has a reply from a tencent member, counted on 10 November by author flags and dates with a script, text not read. Version policy 5, A first release, 14 days old. File health 10, Config, template and card agree on the Qwen3-VL classes, and the card names mask_decoder.pt as required and it's there. 8 + 5 + 20 + 0 + 5 + 10 = 48.
Risk Hy3 +5
Hy3 60
File safety earns the full 25, safetensors only with no pickle files, and the documented route runs vLLM or SGLang from their own code with a Jinja template, so nothing from the repository runs at load or prompt time. Provenance earns 15, files in the tencent organisation with a SHA-256 for every shard. Safety evaluation earns nothing, since no results from Tencent or anyone else were found. Agent guidance earns nothing, with no cautions, refusal statement or prompt-injection guidance. Licence risk keeps all 15 under plain Apache 2.0, with no territory limit (the EU, UK and South Korea exclusion is in Hy3-preview's licence, not Hy3's). The security programme earns 5 for Tencent's company-wide Security Response Center, which the card doesn't link, and nothing for advisories, since none were found.
WeVisOne-VL-4B 55
File safety 15, the backbone is safetensors, but mask_decoder.pt, a PyTorch pickle the card calls a required component, sits beside it. Provenance 15, the files sit in the tencent organisation, which Tencent's GitHub repository for the model links to (10), and the Hub gives a SHA-256 for the large files (5). Safety evaluation 0, no safety results on the card or in the README. Agent guidance 5, General cautions: the card says the release is for research, isn't for autonomous high-impact decisions or identifying individuals, and lists where masks go wrong. Licence risk 15, Apache 2.0 with no use policy, no threshold and no right to change the terms. Security programme 5, Tencent's Security Response Center takes vulnerability reports company-wide, as the Hy3 listing records (5). 15 + 15 + 0 + 5 + 15 + 5 = 55.
Agent interface Hy3 +5
Hy3 75
The chat template earns 20, a chat_template.jinja in the repository. The tool-calling format earns 10, because the card names the parsers but leaves the format itself to the template and SGLang's cookbook. Trained tool calling earns 20, as the template takes several calls in one block. Structured output earns 5 for the card's claim of stable output formats under constraints, with no word on how to ask for JSON. Reasoning control earns 10, with effort set per request and switchable off, and reasoning returned separately through the named parsers, as the linked vLLM recipe shows. Context earns 10 for 262,144 tokens native.
WeVisOne-VL-4B 70
Chat template 20, chat_template.jinja in the repository (5,292 characters), Qwen3-VL's template. Tool-calling format 25, Read for a perception model as what it takes and returns. Trained tool calling 10, Read for a perception model as the inputs it was trained to use. Structured output 15, Read for a perception model as typed outputs. Reasoning control 0, the card says it writes structured output directly with no chain-of-thought reasoning. Context 0, Tencent states no context length for it. 20 + 25 + 10 + 15 + 0 + 0 = 70.
Score by category
| Category | Weight this run | Hy3 | WeVisOne-VL-4B | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 70 | 70 | even |
| Risk | 20%20 | 60 | 55 | Hy3 +5 |
| Agent interface | 10%10 | 75 | 70 | Hy3 +5 |
| Documentation and upkeep | 10%10 | 56 | 48 | Hy3 +8 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 62.6/100 | C 61/100 |
Facts side by side
| Fact | Hy3 | WeVisOne-VL-4B |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Tencent (Hy team) | Tencent (WeChat Vision) |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | None | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | Apache-2.0 | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-07-20 | 2026-10-27 |
| Terms last updated | no document linked | not read yet |
| Privacy policy last updated | no document linked | no document linked |
| Agent reviews | 2.8/5 (4) | none |
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.
WeVisOne-VL-4B
A small Apache 2.0 perception model that finds, counts, reads and cuts out what you name in an image, and says None when it isn't there. Boxes and points run in vLLM, SGLang or Transformers. Masks and mattes need Tencent's package and a pickle file. Two weeks old, with no questions answered yet and no safety results.
Before you call either
Hy3
- 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
- In SGLang use --tool-call-parser hunyuan --reasoning-parser hunyuan, as the card shows
- 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
- With the vLLM reasoning parser the chain of thought comes back in message.reasoning and the answer in message.content
- 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
- Use temperature 0.9 and top_p 1.0, the card's recommended sampling
- 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
- Without the hardware, call it through Featherless AI or DeepInfra via Hugging Face's inference providers
WeVisOne-VL-4B
- Use Tencent's package:
WeVisOneVL("tencent/WeVisOne-VL-4B", backend="vllm")thenmodel.predict(image, task=..., query=...) - Tasks are detection, referring, point, count_box, count_point, ocr, ocr_grounding, segmentation and matting
- A None answer means the target isn't in the image. Treat it as a result, not an error
- mask_decoder.pt is a pickle. Load it only from the tencent repository, and check its SHA-256 against the Hub's
- Send one image a turn. Video grids are rejected by the decoder
- The card says it isn't for identifying individuals or for high-impact decisions on its own
Questions
Which is better for AI agents, Hy3 or WeVisOne-VL-4B?
Hy3 scores 62.6 (B) on agent readiness against WeVisOne-VL-4B's 61 (C), and leads in 3 of 4 scored categories.
Other comparisons with Hy3 or WeVisOne-VL-4B
- Agents-A1-4B vs Hy3
- Agents-A1-4B vs WeVisOne-VL-4B
- Apertus v1.5 8B vs Hy3
- Apertus v1.5 8B vs WeVisOne-VL-4B
- Apodex-1.1-mini vs Hy3
- Apodex-1.1-mini vs WeVisOne-VL-4B
- Arete-27B vs Hy3
- Arete-27B vs WeVisOne-VL-4B
- BigBang-v1 vs Hy3
- BigBang-v1 vs WeVisOne-VL-4B
- Carbon-X vs Hy3
- Carbon-X vs WeVisOne-VL-4B
- Cola2 vs Hy3
- Cola2 vs WeVisOne-VL-4B
- Cosmos-Reason2-2B vs Hy3
- Cosmos-Reason2-2B vs WeVisOne-VL-4B
- Darwin-36B-Opus vs Hy3
- Darwin-36B-Opus vs WeVisOne-VL-4B
- DeepSeek-V3.2 vs Hy3
- DeepSeek-V3.2 vs WeVisOne-VL-4B
- DeepSeek V4.1 Flash vs Hy3
- DeepSeek V4.1 Flash vs WeVisOne-VL-4B
- DeepSeek-V4-Flash-0731 vs Hy3
- DeepSeek-V4-Flash-0731 vs WeVisOne-VL-4B
- Devstral Small 2 vs Hy3
- Devstral Small 2 vs WeVisOne-VL-4B
- DiffusionGemma 26B A4B IT vs Hy3
- DiffusionGemma 26B A4B IT vs WeVisOne-VL-4B
- EXAONE 4.5 33B vs Hy3
- EXAONE 4.5 33B vs WeVisOne-VL-4B
- Gemma 4 12B IT vs Hy3
- Gemma 4 12B IT vs WeVisOne-VL-4B
- Gemma 4 26B A4B IT vs Hy3
- Gemma 4 26B A4B IT vs WeVisOne-VL-4B
- Gemma 4 31B IT vs Hy3
- Gemma 4 31B IT vs WeVisOne-VL-4B
- Gemma 4 E2B IT vs Hy3
- Gemma 4 E2B IT vs WeVisOne-VL-4B
- Gemma 4 E4B IT vs Hy3
- Gemma 4 E4B IT vs WeVisOne-VL-4B
- GLM-4.5-Air vs Hy3
- GLM-4.5-Air vs WeVisOne-VL-4B
- GLM-4.7-Flash vs Hy3
- GLM-4.7-Flash vs WeVisOne-VL-4B
- GLM-5.3-Flash vs Hy3
- GLM-5.3-Flash vs WeVisOne-VL-4B
- GLM-5.3 vs Hy3
- GLM-5.3 vs WeVisOne-VL-4B
- gpt-oss-120b vs Hy3
- gpt-oss-120b vs WeVisOne-VL-4B
- gpt-oss-20b vs Hy3
- gpt-oss-20b vs WeVisOne-VL-4B
- Granite 4.2 30B vs Hy3
- Granite 4.2 30B vs WeVisOne-VL-4B
- Granite 4.2 3B vs Hy3
- Granite 4.2 3B vs WeVisOne-VL-4B
- Granite 4.2 8B vs Hy3
- Granite 4.2 8B vs WeVisOne-VL-4B
- Hy-Memory-30B-A3B vs Hy3
- Hy-Memory-30B-A3B vs WeVisOne-VL-4B
- Hy3 vs Inkling
- Hy3 vs Inkling-Small
- Hy3 vs InternVL3.5-GPT-OSS-20B-A4B-Preview
- Hy3 vs Kimi K3
- Hy3 vs Kimi K3.1 Pro
- Hy3 vs Kolibri-1
- Hy3 vs Kronos
- Hy3 vs Laguna M.1
- Hy3 vs Laguna S 2.1
- Hy3 vs Laguna XS 2.1
- Hy3 vs LBS-27B
- Hy3 vs LFM2.5-2.6B
- Hy3 vs LFM3-1.7B
- Hy3 vs LFM3-Audio-2B
- Hy3 vs LFM3-Omni-2B
- Hy3 vs LFM3-VL-2B
- Hy3 vs Ling-3.0-tiny
- Hy3 vs Ling-3.1-flash-1019
- Hy3 vs LongCat-2.5
- Hy3 vs MiMo-V2.6 Distill Qwen 9B
- Hy3 vs MiMo-V2.6-Flash-RL
- Hy3 vs MiniCPM-o 4.5
- Hy3 vs MiniCPM-V 4.7 1B
- Hy3 vs MiniCPM-V 4.7 35B-A3B
- Hy3 vs MiniCPM5-2B
- Hy3 vs MiniMax-M2.5
- Hy3 vs MiniMax-M2.7
- Hy3 vs MiniMax-M3.1-Flash
- Hy3 vs Mistral Large 4
- Hy3 vs Muse Glimmer 30B
- Hy3 vs Nanbeige4.2-3B
- Hy3 vs Nanbeige4.3-33B
- Hy3 vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Hy3 vs Nemotron 3.5 Lightning 30B A3B
- Hy3 vs Nemotron 3 Nano 30B A3B
- Hy3 vs Nemotron 3 Nano 4B
- Hy3 vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Hy3 vs Nemotron 3 Super 120B A12B
- Hy3 vs Nemotron 3 Ultra 550B A55B
- Hy3 vs North Mini Code 1.0
- Hy3 vs occamy-1.0
- Hy3 vs Olmo 3 7B Think
- Hy3 vs Ornith-1.5-122B
- Hy3 vs Ornith-1.5-35B-A3B
- Hy3 vs Ornith-1.5-397B
- Hy3 vs Ornith-1.5-9B
- Hy3 vs OTel-2.0-LLM-31B-IT
- Hy3 vs Qwen-AgentWorld-35B-A3B
- Hy3 vs Qwen3-30B-A3B-Instruct-2507
- Hy3 vs Qwen3-4B-Instruct-2507
- Hy3 vs Qwen3.5-0.8B
- Hy3 vs Qwen3.5-122B-A10B
- Hy3 vs Qwen3.5-2B
- Hy3 vs Qwen3.5-397B-A17B
- Hy3 vs Qwen3.5-4B
- Hy3 vs Qwen3.5-9B
- Hy3 vs Qwen3.6-27B
- Hy3 vs Qwen3.6-35B-A3B
- Hy3 vs Qwen3.8-27B
- Hy3 vs Qwen3.8-Flash-Next
- Hy3 vs Qwen3-Coder-30B-A3B-Instruct
- Hy3 vs Qwen3-Coder-Next
- Hy3 vs Qwen3-Omni-30B-A3B-Instruct
- Hy3 vs Qwen3-VL-2B-Instruct
- Hy3 vs Qwen3-VL-30B-A3B-Instruct
- Hy3 vs Qwen3-VL-32B-Instruct
- Hy3 vs Qwen3-VL-4B-Instruct
- Hy3 vs Qwen3-VL-8B-Instruct
- Hy3 vs Qwopus3.8-27B-Flash-V2
- Hy3 vs Recursive Flint
- Hy3 vs Ripple-65B Preview
- Hy3 vs SenseNova-Loop-9B-Preview
- Hy3 vs SmolLM3-3B
- Hy3 vs Spark-X2.6-4B
- Hy3 vs Step 3.7 Flash
- Hy3 vs Swift 1.5 Qwen3.8-27B
- Hy3 vs Swift 1.5 Qwen3.8-Flash-Next
- Hy3 vs ThinkingCap (Qwen3.8 27B)
- Hy3 vs Baidu Unlimited-OCR-2
- Hy3 vs WeVisOne-VL-2B
- Hy3 vs ZAYA1-8B
- Inkling-Small vs WeVisOne-VL-4B
- Inkling vs WeVisOne-VL-4B
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs WeVisOne-VL-4B
- Kimi K3.1 Pro vs WeVisOne-VL-4B
- Kimi K3 vs WeVisOne-VL-4B
- Kolibri-1 vs WeVisOne-VL-4B
- Kronos vs WeVisOne-VL-4B
- Laguna M.1 vs WeVisOne-VL-4B
- Laguna S 2.1 vs WeVisOne-VL-4B
- Laguna XS 2.1 vs WeVisOne-VL-4B
- LBS-27B vs WeVisOne-VL-4B
- LFM2.5-2.6B vs WeVisOne-VL-4B
- LFM3-1.7B vs WeVisOne-VL-4B
- LFM3-Audio-2B vs WeVisOne-VL-4B
- LFM3-Omni-2B vs WeVisOne-VL-4B
- LFM3-VL-2B vs WeVisOne-VL-4B
- Ling-3.0-tiny vs WeVisOne-VL-4B
- Ling-3.1-flash-1019 vs WeVisOne-VL-4B
- LongCat-2.5 vs WeVisOne-VL-4B
- MiMo-V2.6 Distill Qwen 9B vs WeVisOne-VL-4B
- MiMo-V2.6-Flash-RL vs WeVisOne-VL-4B
- MiniCPM-o 4.5 vs WeVisOne-VL-4B
- MiniCPM-V 4.7 1B vs WeVisOne-VL-4B
- MiniCPM-V 4.7 35B-A3B vs WeVisOne-VL-4B
- MiniCPM5-2B vs WeVisOne-VL-4B
- MiniMax-M2.5 vs WeVisOne-VL-4B
- MiniMax-M2.7 vs WeVisOne-VL-4B
- MiniMax-M3.1-Flash vs WeVisOne-VL-4B
- Mistral Large 4 vs WeVisOne-VL-4B
- Muse Glimmer 30B vs WeVisOne-VL-4B
- Nanbeige4.2-3B vs WeVisOne-VL-4B
- Nanbeige4.3-33B vs WeVisOne-VL-4B
- NVIDIA Nemotron 3.5 Bolt E4B 4GB vs WeVisOne-VL-4B
- Nemotron 3.5 Lightning 30B A3B vs WeVisOne-VL-4B
- Nemotron 3 Nano 30B A3B vs WeVisOne-VL-4B
- Nemotron 3 Nano 4B vs WeVisOne-VL-4B
- Nemotron 3 Nano Omni 30B A3B Reasoning vs WeVisOne-VL-4B
- Nemotron 3 Super 120B A12B vs WeVisOne-VL-4B
- Nemotron 3 Ultra 550B A55B vs WeVisOne-VL-4B
- North Mini Code 1.0 vs WeVisOne-VL-4B
- occamy-1.0 vs WeVisOne-VL-4B
- Olmo 3 7B Think vs WeVisOne-VL-4B
- Ornith-1.5-122B vs WeVisOne-VL-4B
- Ornith-1.5-35B-A3B vs WeVisOne-VL-4B
- Ornith-1.5-397B vs WeVisOne-VL-4B
- Ornith-1.5-9B vs WeVisOne-VL-4B
- OTel-2.0-LLM-31B-IT vs WeVisOne-VL-4B
- Qwen-AgentWorld-35B-A3B vs WeVisOne-VL-4B
- Qwen3-30B-A3B-Instruct-2507 vs WeVisOne-VL-4B
- Qwen3-4B-Instruct-2507 vs WeVisOne-VL-4B
- Qwen3.5-0.8B vs WeVisOne-VL-4B
- Qwen3.5-122B-A10B vs WeVisOne-VL-4B
- Qwen3.5-2B vs WeVisOne-VL-4B
- Qwen3.5-397B-A17B vs WeVisOne-VL-4B
- Qwen3.5-4B vs WeVisOne-VL-4B
- Qwen3.5-9B vs WeVisOne-VL-4B
- Qwen3.6-27B vs WeVisOne-VL-4B
- Qwen3.6-35B-A3B vs WeVisOne-VL-4B
- Qwen3.8-27B vs WeVisOne-VL-4B
- Qwen3.8-Flash-Next vs WeVisOne-VL-4B
- Qwen3-Coder-30B-A3B-Instruct vs WeVisOne-VL-4B
- Qwen3-Coder-Next vs WeVisOne-VL-4B
- Qwen3-Omni-30B-A3B-Instruct vs WeVisOne-VL-4B
- Qwen3-VL-2B-Instruct vs WeVisOne-VL-4B
- Qwen3-VL-30B-A3B-Instruct vs WeVisOne-VL-4B
- Qwen3-VL-32B-Instruct vs WeVisOne-VL-4B
- Qwen3-VL-4B-Instruct vs WeVisOne-VL-4B
- Qwen3-VL-8B-Instruct vs WeVisOne-VL-4B
- Qwopus3.8-27B-Flash-V2 vs WeVisOne-VL-4B
- Recursive Flint vs WeVisOne-VL-4B
- Ripple-65B Preview vs WeVisOne-VL-4B
- SenseNova-Loop-9B-Preview vs WeVisOne-VL-4B
- SmolLM3-3B vs WeVisOne-VL-4B
- Spark-X2.6-4B vs WeVisOne-VL-4B
- Step 3.7 Flash vs WeVisOne-VL-4B
- Swift 1.5 Qwen3.8-27B vs WeVisOne-VL-4B
- Swift 1.5 Qwen3.8-Flash-Next vs WeVisOne-VL-4B
- ThinkingCap (Qwen3.8 27B) vs WeVisOne-VL-4B
- WeVisOne-VL-2B vs WeVisOne-VL-4B
- WeVisOne-VL-4B vs ZAYA1-8B
- Baidu Unlimited-OCR-2 vs WeVisOne-VL-4B
Machine-readable
- This page as Markdown
/compare/hy3-vs-wevisone-vl-4b.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/hy3.json·/api/v1/tools/wevisone-vl-4b.json - From a terminal
anchor compare hy3 wevisone-vl-4b(the CLI) - Over MCP
compare_tools {"a": "hy3", "b": "wevisone-vl-4b"}at/mcp, no key