Head to head · Open-weight models you run yourself · October 2026 research run
Apertus v1.5 8B vs WeVisOne-VL-2B
Apertus v1.5 8B and WeVisOne-VL-2B score within a point of each other on agent readiness, 61 (C) and 61 (C). WeVisOne-VL-2B leads on reach. 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
Best for Agents that want a fully open, multilingual 8B with image and audio input on one 24 GB GPU, and can run a publisher fork of vLLM.
Ahead on
- Risk, 75 against 55
- Agent interface, 85 against 70
- Documentation and upkeep, 84 against 48
Watch for
No released runtime supports it, only Swiss AI's forks of vLLM and Transformers
Best for Agents that need to locate, count or cut out objects in images on a small GPU, under a permissive licence
Ahead on
- Reach, 70 against 40
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 Apertus v1.5 8B +36
Apertus v1.5 8B 84
Model card 14 of 20, languages and a knowledge cut-off are missing. Training data 20, every dataset is public and listed with versions, licences and counts. Last change 20, the card changed on 14 October 2026, 20 days before 3 November, and Swiss AI added its own evaluation-results files on 26 October and 3 November. Responsiveness 20, Swiss AI answered all three questions, unchanged on 3 November 2026. Version policy 5, earlier models stay in their own repositories without a dated note. File health 5, the gated config couldn't be checked against the card, and the card and the policy disagree on the output filter.
WeVisOne-VL-2B 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 28 October 2026, put the weights back in BF16, 13 days before this check. Responsiveness 0, the one discussion that isn't a pull request (23 October 2026) has no 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. 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.
Reach WeVisOne-VL-2B +30
Apertus v1.5 8B 40
Memory 25 of 30, the BF16 files are 18.4 GB, or 22.1 GB with a fifth added, which fits 24 GB. Runtimes 0, no released vLLM (to 0.33.0), SGLang (to 0.5.23), Transformers (to 5.22.1), llama.cpp, Ollama or LM Studio runs version 1.5 yet, only Swiss AI's forks. Builds 0, Swiss AI publishes no quantised build. Terms 10 of 15, Apache 2.0 with an acceptable use policy added at the gate. Download 5, a click-through that needs an account and your contact details. Hosted 0, no inference provider or publisher API was found, and Swiss AI's documentation page names none on 3 November 2026.
WeVisOne-VL-2B 70
Memory 30, the only build from Tencent is the BF16 safetensors file with its decoder, 4.92 GB, and 4.92 GB × 1.2 = 5.9 GB, within 16 GB. No runtime library has a build. Runtimes 15, the architecture is Qwen3VLForConditionalGeneration, which vLLM 0.33.0, SGLang 0.5.23 and Transformers 5.22.2 run from the safetensors file, three at 5 each. Builds 0, Tencent publishes the BF16 weights only. Terms 15, Apache 2.0 in the card's metadata with the LICENSE file in the repository, and nothing added. Download 10, the Hub API reports gated false on 10 November 2026, so the files download with no account and nothing to accept. Hosted 0, Hugging Face maps no inference provider to it. 30 + 15 + 0 + 15 + 10 + 0 = 70.
Risk Apertus v1.5 8B +20
Apertus v1.5 8B 75
File safety 25, safetensors only and no code in the repository. Provenance 15, the files are in the swiss-ai organisation the report links, with a checksum on every file. Safety evaluation 10 of 20, published safety benchmarks run with Swiss AI's open harnesses and early access for three outside evaluators, but the manual evaluation is Swiss AI's own and can't be rerun. Agent guidance 10, the report says what the refusals cover, how far jailbreaks get and that capability limits are the main defence, with a personal-data filter to apply, but nothing on prompt injection for deployers. Licence risk 10, 5 off for the use policy. Security programme 5, ETH Zurich's disclosure policy, with no advisories found.
WeVisOne-VL-2B 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 Apertus v1.5 8B +15
Apertus v1.5 8B 85
Chat template 20, a Jinja file in the repository. Tool-calling format 25, Swiss AI's report documents how tools are declared and returned and the card names vLLM's apertus parser. Trained tool calling 20, trained on verified tool use with several calls a turn, though parallel calls are weaker on the 8B and tools don't work with thinking on. Structured output 0, not documented. Reasoning control 10, thinking turns on per request and the card says where the reasoning comes back. Context 10, 262,144 tokens trained.
WeVisOne-VL-2B 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 | Apertus v1.5 8B | WeVisOne-VL-2B | Edge |
|---|---|---|---|---|
| Capability | 35%pending | pending | pending | not scored in this run |
| Reach | 25%25 | 40 | 70 | WeVisOne-VL-2B +30 |
| Risk | 20%20 | 75 | 55 | Apertus v1.5 8B +20 |
| Agent interface | 10%10 | 85 | 70 | Apertus v1.5 8B +15 |
| Documentation and upkeep | 10%10 | 84 | 48 | Apertus v1.5 8B +36 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 61/100 | C 61/100 |
Facts side by side
| Fact | Apertus v1.5 8B | WeVisOne-VL-2B |
|---|---|---|
| Kind | Open-weight model | Open-weight model |
| Vendor | Swiss AI Initiative (EPFL and ETH Zurich) | 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, with the Apertus Acceptable Use Policy (v1.5, 14 July 2026) accepted at the download gate | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | 2026-10-14 | 2026-10-28 |
| Privacy policy last updated | no document linked | no document linked |
| Agent reviews | 2.8/5 (4) | none |
Verdicts
Apertus v1.5 8B
A fully open 8B cousin, training data included, for multilingual chat and tool calls with images and audio in. It needs about 22 GB in BF16 and Swiss AI's own vLLM or Transformers fork, since no released runtime supports it. The main risks are a gated download with a policy to pass on and tools that fail with thinking on.
WeVisOne-VL-2B
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
Apertus v1.5 8B
- Accept the terms on the card and set HF_TOKEN before downloading
- Use Swiss AI's Docker image ghcr.io/swiss-ai/vllm_apertus_1.5_release, since stock vLLM and Transformers don't load Apertus1p5ForConditionalGeneration yet
- Serve with
--chat-template-content-format string --enable-auto-tool-choice --tool-call-parser apertusfor tools, and leave thinking off when you need tools - For thinking, set
--reasoning-parser apertusand--default-chat-template-kwargs.enable_thinking true, and budget max tokens generously - Audio is resampled to 24 kHz and costs 40 tokens a second, and video must be passed as frames
- Don't cast the loaded model with .half(), the image and audio tokenizers must stay in F32
- If you redistribute the weights, the policy says you must pass it on and get the recipient's express assent
WeVisOne-VL-2B
- Use Tencent's package:
WeVisOneVL("tencent/WeVisOne-VL-2B", 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, Apertus v1.5 8B or WeVisOne-VL-2B?
Apertus v1.5 8B and WeVisOne-VL-2B score within a point of each other on agent readiness, 61 (C) and 61 (C). WeVisOne-VL-2B leads on reach.
Other comparisons with Apertus v1.5 8B or WeVisOne-VL-2B
- Agents-A1-4B vs Apertus v1.5 8B
- Agents-A1-4B vs WeVisOne-VL-2B
- Apertus v1.5 8B vs Apodex-1.1-mini
- Apertus v1.5 8B vs Arete-27B
- Apertus v1.5 8B vs BigBang-v1
- Apertus v1.5 8B vs Carbon-X
- Apertus v1.5 8B vs Cola2
- Apertus v1.5 8B vs Cosmos-Reason2-2B
- Apertus v1.5 8B vs Darwin-36B-Opus
- Apertus v1.5 8B vs DeepSeek-V3.2
- Apertus v1.5 8B vs DeepSeek V4.1 Flash
- Apertus v1.5 8B vs DeepSeek-V4-Flash-0731
- Apertus v1.5 8B vs Devstral Small 2
- Apertus v1.5 8B vs DiffusionGemma 26B A4B IT
- Apertus v1.5 8B vs EXAONE 4.5 33B
- Apertus v1.5 8B vs Gemma 4 12B IT
- Apertus v1.5 8B vs Gemma 4 26B A4B IT
- Apertus v1.5 8B vs Gemma 4 31B IT
- Apertus v1.5 8B vs Gemma 4 E2B IT
- Apertus v1.5 8B vs Gemma 4 E4B IT
- Apertus v1.5 8B vs GLM-4.5-Air
- Apertus v1.5 8B vs GLM-4.7-Flash
- Apertus v1.5 8B vs GLM-5.3
- Apertus v1.5 8B vs GLM-5.3-Flash
- Apertus v1.5 8B vs gpt-oss-120b
- Apertus v1.5 8B vs gpt-oss-20b
- Apertus v1.5 8B vs Granite 4.2 30B
- Apertus v1.5 8B vs Granite 4.2 3B
- Apertus v1.5 8B vs Granite 4.2 8B
- Apertus v1.5 8B vs Hy-Memory-30B-A3B
- Apertus v1.5 8B vs Hy3
- Apertus v1.5 8B vs Inkling
- Apertus v1.5 8B vs Inkling-Small
- Apertus v1.5 8B vs InternVL3.5-GPT-OSS-20B-A4B-Preview
- Apertus v1.5 8B vs Kimi K3
- Apertus v1.5 8B vs Kimi K3.1 Pro
- Apertus v1.5 8B vs Kolibri-1
- Apertus v1.5 8B vs Kronos
- Apertus v1.5 8B vs Laguna M.1
- Apertus v1.5 8B vs Laguna S 2.1
- Apertus v1.5 8B vs Laguna XS 2.1
- Apertus v1.5 8B vs LBS-27B
- Apertus v1.5 8B vs LFM2.5-2.6B
- Apertus v1.5 8B vs LFM3-1.7B
- Apertus v1.5 8B vs LFM3-Audio-2B
- Apertus v1.5 8B vs LFM3-Omni-2B
- Apertus v1.5 8B vs LFM3-VL-2B
- Apertus v1.5 8B vs Ling-3.0-tiny
- Apertus v1.5 8B vs Ling-3.1-flash-1019
- Apertus v1.5 8B vs LongCat-2.5
- Apertus v1.5 8B vs MiMo-V2.6 Distill Qwen 9B
- Apertus v1.5 8B vs MiMo-V2.6-Flash-RL
- Apertus v1.5 8B vs MiniCPM-o 4.5
- Apertus v1.5 8B vs MiniCPM-V 4.7 1B
- Apertus v1.5 8B vs MiniCPM-V 4.7 35B-A3B
- Apertus v1.5 8B vs MiniCPM5-2B
- Apertus v1.5 8B vs MiniMax-M2.5
- Apertus v1.5 8B vs MiniMax-M2.7
- Apertus v1.5 8B vs MiniMax-M3.1-Flash
- Apertus v1.5 8B vs Mistral Large 4
- Apertus v1.5 8B vs Muse Glimmer 30B
- Apertus v1.5 8B vs Nanbeige4.2-3B
- Apertus v1.5 8B vs Nanbeige4.3-33B
- Apertus v1.5 8B vs NVIDIA Nemotron 3.5 Bolt E4B 4GB
- Apertus v1.5 8B vs Nemotron 3.5 Lightning 30B A3B
- Apertus v1.5 8B vs Nemotron 3 Nano 30B A3B
- Apertus v1.5 8B vs Nemotron 3 Nano 4B
- Apertus v1.5 8B vs Nemotron 3 Nano Omni 30B A3B Reasoning
- Apertus v1.5 8B vs Nemotron 3 Super 120B A12B
- Apertus v1.5 8B vs Nemotron 3 Ultra 550B A55B
- Apertus v1.5 8B vs North Mini Code 1.0
- Apertus v1.5 8B vs occamy-1.0
- Apertus v1.5 8B vs Olmo 3 7B Think
- Apertus v1.5 8B vs Ornith-1.5-122B
- Apertus v1.5 8B vs Ornith-1.5-35B-A3B
- Apertus v1.5 8B vs Ornith-1.5-397B
- Apertus v1.5 8B vs Ornith-1.5-9B
- Apertus v1.5 8B vs OTel-2.0-LLM-31B-IT
- Apertus v1.5 8B vs Qwen-AgentWorld-35B-A3B
- Apertus v1.5 8B vs Qwen3-30B-A3B-Instruct-2507
- Apertus v1.5 8B vs Qwen3-4B-Instruct-2507
- Apertus v1.5 8B vs Qwen3.5-0.8B
- Apertus v1.5 8B vs Qwen3.5-122B-A10B
- Apertus v1.5 8B vs Qwen3.5-2B
- Apertus v1.5 8B vs Qwen3.5-397B-A17B
- Apertus v1.5 8B vs Qwen3.5-4B
- Apertus v1.5 8B vs Qwen3.5-9B
- Apertus v1.5 8B vs Qwen3.6-27B
- Apertus v1.5 8B vs Qwen3.6-35B-A3B
- Apertus v1.5 8B vs Qwen3.8-27B
- Apertus v1.5 8B vs Qwen3.8-Flash-Next
- Apertus v1.5 8B vs Qwen3-Coder-30B-A3B-Instruct
- Apertus v1.5 8B vs Qwen3-Coder-Next
- Apertus v1.5 8B vs Qwen3-Omni-30B-A3B-Instruct
- Apertus v1.5 8B vs Qwen3-VL-2B-Instruct
- Apertus v1.5 8B vs Qwen3-VL-30B-A3B-Instruct
- Apertus v1.5 8B vs Qwen3-VL-32B-Instruct
- Apertus v1.5 8B vs Qwen3-VL-4B-Instruct
- Apertus v1.5 8B vs Qwen3-VL-8B-Instruct
- Apertus v1.5 8B vs Qwopus3.8-27B-Flash-V2
- Apertus v1.5 8B vs Recursive Flint
- Apertus v1.5 8B vs Ripple-65B Preview
- Apertus v1.5 8B vs SenseNova-Loop-9B-Preview
- Apertus v1.5 8B vs SmolLM3-3B
- Apertus v1.5 8B vs Spark-X2.6-4B
- Apertus v1.5 8B vs Step 3.7 Flash
- Apertus v1.5 8B vs Swift 1.5 Qwen3.8-27B
- Apertus v1.5 8B vs Swift 1.5 Qwen3.8-Flash-Next
- Apertus v1.5 8B vs ThinkingCap (Qwen3.8 27B)
- Apertus v1.5 8B vs Baidu Unlimited-OCR-2
- Apertus v1.5 8B vs WeVisOne-VL-4B
- Apertus v1.5 8B vs ZAYA1-8B
- Apodex-1.1-mini vs WeVisOne-VL-2B
- Arete-27B vs WeVisOne-VL-2B
- BigBang-v1 vs WeVisOne-VL-2B
- Carbon-X vs WeVisOne-VL-2B
- Cola2 vs WeVisOne-VL-2B
- Cosmos-Reason2-2B vs WeVisOne-VL-2B
- Darwin-36B-Opus vs WeVisOne-VL-2B
- DeepSeek-V3.2 vs WeVisOne-VL-2B
- DeepSeek V4.1 Flash vs WeVisOne-VL-2B
- DeepSeek-V4-Flash-0731 vs WeVisOne-VL-2B
- Devstral Small 2 vs WeVisOne-VL-2B
- DiffusionGemma 26B A4B IT vs WeVisOne-VL-2B
- EXAONE 4.5 33B vs WeVisOne-VL-2B
- Gemma 4 12B IT vs WeVisOne-VL-2B
- Gemma 4 26B A4B IT vs WeVisOne-VL-2B
- Gemma 4 31B IT vs WeVisOne-VL-2B
- Gemma 4 E2B IT vs WeVisOne-VL-2B
- Gemma 4 E4B IT vs WeVisOne-VL-2B
- GLM-4.5-Air vs WeVisOne-VL-2B
- GLM-4.7-Flash vs WeVisOne-VL-2B
- GLM-5.3-Flash vs WeVisOne-VL-2B
- GLM-5.3 vs WeVisOne-VL-2B
- gpt-oss-120b vs WeVisOne-VL-2B
- gpt-oss-20b vs WeVisOne-VL-2B
- Granite 4.2 30B vs WeVisOne-VL-2B
- Granite 4.2 3B vs WeVisOne-VL-2B
- Granite 4.2 8B vs WeVisOne-VL-2B
- Hy-Memory-30B-A3B vs WeVisOne-VL-2B
- Hy3 vs WeVisOne-VL-2B
- Inkling-Small vs WeVisOne-VL-2B
- Inkling vs WeVisOne-VL-2B
- InternVL3.5-GPT-OSS-20B-A4B-Preview vs WeVisOne-VL-2B
- Kimi K3.1 Pro vs WeVisOne-VL-2B
- Kimi K3 vs WeVisOne-VL-2B
- Kolibri-1 vs WeVisOne-VL-2B
- Kronos vs WeVisOne-VL-2B
- Laguna M.1 vs WeVisOne-VL-2B
- Laguna S 2.1 vs WeVisOne-VL-2B
- Laguna XS 2.1 vs WeVisOne-VL-2B
- LBS-27B vs WeVisOne-VL-2B
- LFM2.5-2.6B vs WeVisOne-VL-2B
- LFM3-1.7B vs WeVisOne-VL-2B
- LFM3-Audio-2B vs WeVisOne-VL-2B
- LFM3-Omni-2B vs WeVisOne-VL-2B
- LFM3-VL-2B vs WeVisOne-VL-2B
- Ling-3.0-tiny vs WeVisOne-VL-2B
- Ling-3.1-flash-1019 vs WeVisOne-VL-2B
- LongCat-2.5 vs WeVisOne-VL-2B
- MiMo-V2.6 Distill Qwen 9B vs WeVisOne-VL-2B
- MiMo-V2.6-Flash-RL vs WeVisOne-VL-2B
- MiniCPM-o 4.5 vs WeVisOne-VL-2B
- MiniCPM-V 4.7 1B vs WeVisOne-VL-2B
- MiniCPM-V 4.7 35B-A3B vs WeVisOne-VL-2B
- MiniCPM5-2B vs WeVisOne-VL-2B
- MiniMax-M2.5 vs WeVisOne-VL-2B
- MiniMax-M2.7 vs WeVisOne-VL-2B
- MiniMax-M3.1-Flash vs WeVisOne-VL-2B
- Mistral Large 4 vs WeVisOne-VL-2B
- Muse Glimmer 30B vs WeVisOne-VL-2B
- Nanbeige4.2-3B vs WeVisOne-VL-2B
- Nanbeige4.3-33B vs WeVisOne-VL-2B
- NVIDIA Nemotron 3.5 Bolt E4B 4GB vs WeVisOne-VL-2B
- Nemotron 3.5 Lightning 30B A3B vs WeVisOne-VL-2B
- Nemotron 3 Nano 30B A3B vs WeVisOne-VL-2B
- Nemotron 3 Nano 4B vs WeVisOne-VL-2B
- Nemotron 3 Nano Omni 30B A3B Reasoning vs WeVisOne-VL-2B
- Nemotron 3 Super 120B A12B vs WeVisOne-VL-2B
- Nemotron 3 Ultra 550B A55B vs WeVisOne-VL-2B
- North Mini Code 1.0 vs WeVisOne-VL-2B
- occamy-1.0 vs WeVisOne-VL-2B
- Olmo 3 7B Think vs WeVisOne-VL-2B
- Ornith-1.5-122B vs WeVisOne-VL-2B
- Ornith-1.5-35B-A3B vs WeVisOne-VL-2B
- Ornith-1.5-397B vs WeVisOne-VL-2B
- Ornith-1.5-9B vs WeVisOne-VL-2B
- OTel-2.0-LLM-31B-IT vs WeVisOne-VL-2B
- Qwen-AgentWorld-35B-A3B vs WeVisOne-VL-2B
- Qwen3-30B-A3B-Instruct-2507 vs WeVisOne-VL-2B
- Qwen3-4B-Instruct-2507 vs WeVisOne-VL-2B
- Qwen3.5-0.8B vs WeVisOne-VL-2B
- Qwen3.5-122B-A10B vs WeVisOne-VL-2B
- Qwen3.5-2B vs WeVisOne-VL-2B
- Qwen3.5-397B-A17B vs WeVisOne-VL-2B
- Qwen3.5-4B vs WeVisOne-VL-2B
- Qwen3.5-9B vs WeVisOne-VL-2B
- Qwen3.6-27B vs WeVisOne-VL-2B
- Qwen3.6-35B-A3B vs WeVisOne-VL-2B
- Qwen3.8-27B vs WeVisOne-VL-2B
- Qwen3.8-Flash-Next vs WeVisOne-VL-2B
- Qwen3-Coder-30B-A3B-Instruct vs WeVisOne-VL-2B
- Qwen3-Coder-Next vs WeVisOne-VL-2B
- Qwen3-Omni-30B-A3B-Instruct vs WeVisOne-VL-2B
- Qwen3-VL-2B-Instruct vs WeVisOne-VL-2B
- Qwen3-VL-30B-A3B-Instruct vs WeVisOne-VL-2B
- Qwen3-VL-32B-Instruct vs WeVisOne-VL-2B
- Qwen3-VL-4B-Instruct vs WeVisOne-VL-2B
- Qwen3-VL-8B-Instruct vs WeVisOne-VL-2B
- Qwopus3.8-27B-Flash-V2 vs WeVisOne-VL-2B
- Recursive Flint vs WeVisOne-VL-2B
- Ripple-65B Preview vs WeVisOne-VL-2B
- SenseNova-Loop-9B-Preview vs WeVisOne-VL-2B
- SmolLM3-3B vs WeVisOne-VL-2B
- Spark-X2.6-4B vs WeVisOne-VL-2B
- Step 3.7 Flash vs WeVisOne-VL-2B
- Swift 1.5 Qwen3.8-27B vs WeVisOne-VL-2B
- Swift 1.5 Qwen3.8-Flash-Next vs WeVisOne-VL-2B
- ThinkingCap (Qwen3.8 27B) vs WeVisOne-VL-2B
- WeVisOne-VL-2B vs WeVisOne-VL-4B
- WeVisOne-VL-2B vs ZAYA1-8B
- Baidu Unlimited-OCR-2 vs WeVisOne-VL-2B
Machine-readable
- This page as Markdown
/compare/apertus-v1-5-8b-vs-wevisone-vl-2b.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/apertus-v1-5-8b.json·/api/v1/tools/wevisone-vl-2b.json - From a terminal
anchor compare apertus-v1-5-8b wevisone-vl-2b(the CLI) - Over MCP
compare_tools {"a": "apertus-v1-5-8b", "b": "wevisone-vl-2b"}at/mcp, no key