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

Apertus v1.5 8B vs GLM-5.3

GLM-5.3 scores 64.6 (B) on agent readiness against Apertus v1.5 8B's 61 (C), and leads in 1 of 4 scored categories. Apertus v1.5 8B leads on risk, agent interface and documentation and upkeep. 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

Apertus v1.5 8B C

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 50
  • Agent interface, 85 against 70
  • Documentation and upkeep, 84 against 58

Watch for

No released runtime supports it, only Swiss AI's forks of vLLM and Transformers

GLM-5.3 B

Best for Teams with an 8-GPU server who want an open coding and long-horizon agent model with a 1M-token context, or agents that call it through Z.ai or a hosted provider

Ahead on

  • Reach, 55 against 40

Watch for

Z.ai's smallest build is 755.6 GB in FP8, with no local Ollama or LM Studio build

Score by category

CategoryWeight this runApertus v1.5 8BGLM-5.3Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%254055GLM-5.3 +15
Risk20%207550Apertus v1.5 8B +25
Agent interface10%108570Apertus v1.5 8B +15
Documentation and upkeep10%108458Apertus v1.5 8B +26
Negative events≤1500
TotalC 61/100B 64.6/100

Facts side by side

FactApertus v1.5 8BGLM-5.3
KindOpen-weight modelOpen-weight model
VendorSwiss AI Initiative (EPFL and ETH Zurich)Z.ai (Zhipu AI)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0, with the Apertus Acceptable Use Policy (v1.5, 14 July 2026) accepted at the download gateGLM-5.3 License (MIT-style, with a security review for the largest model-as-a-service operators)
Read-only variant documentednono
llms.txtnono
Last release2026-10-142026-10-14
Terms last updatedno 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)2.8/5 (4)

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.

GLM-5.3

A large coding and long-horizon agent model with a 1M-token context, several tool calls per turn and three reasoning budgets. Z.ai's smallest build is 756 GB in FP8, so it needs an 8-GPU server, Z.ai's API or a provider. The main risks are no published safety work, no way to report a flaw, and thinking that can't be turned off.

Before you call either

Apertus v1.5 8B

  1. Accept the terms on the card and set HF_TOKEN before downloading
  2. 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
  3. Serve with --chat-template-content-format string --enable-auto-tool-choice --tool-call-parser apertus for tools, and leave thinking off when you need tools
  4. For thinking, set --reasoning-parser apertus and --default-chat-template-kwargs.enable_thinking true, and budget max tokens generously
  5. Audio is resampled to 24 kHz and costs 40 tokens a second, and video must be passed as frames
  6. Don't cast the loaded model with .half(), the image and audio tokenizers must stay in F32
  7. If you redistribute the weights, the policy says you must pass it on and get the recipient's express assent

GLM-5.3

  1. Start it with vllm serve zai-org/GLM-5.3 --kv-cache-dtype fp8 --tensor-parallel-size 8 --speculative-config.method mtp --speculative-config.num_speculative_tokens 5 --tool-call-parser glm47 --reasoning-parser glm47 --enable-auto-tool-choice --served-model-name glm-5.3 (vLLM 0.28.0 or later, 8xH200 or 8xH20 per vLLM's recipe)
  2. Use the glm47 tool-call and reasoning parsers in vLLM or SGLang; SGLang's cookbook says glm45 leaves the calls as plain text
  3. Pass chat_template_kwargs: {"reasoning_effort": "low"} for short tasks; anything other than low or high falls back to max
  4. Pass clear_thinking: true in chat use, since the template keeps earlier reasoning by default
  5. Don't send enable_thinking: false; the template ignores it and always opens a think block
  6. Validate JSON output yourself, since structured output is documented only for Z.ai's hosted API
  7. No Z.ai build fits a 128 GB machine; the full 1M context needs 8xB200 per vLLM's recipe

Questions

Which is better for AI agents, Apertus v1.5 8B or GLM-5.3?

GLM-5.3 scores 64.6 (B) on agent readiness against Apertus v1.5 8B's 61 (C), and leads in 1 of 4 scored categories. Apertus v1.5 8B leads on risk, agent interface and documentation and upkeep.

Other comparisons with Apertus v1.5 8B or GLM-5.3

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.