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

Apertus v1.5 8B vs Apodex-1.1-mini

Apertus v1.5 8B and Apodex-1.1-mini score within a point of each other on agent readiness, 61 (C) and 61 (C). Apodex-1.1-mini 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

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 65
  • Documentation and upkeep, 84 against 38

Watch for

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

Apodex-1.1-mini C

Best for Long-running agent tasks with tools on a 32 GB GPU or Mac, or through Apodex's API, under a plain licence

Ahead on

  • Reach, 85 against 40

Also in its favour

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

Watch for

No safety results, and agent guidance only from the harness

Score by category

CategoryWeight this runApertus v1.5 8BApodex-1.1-miniEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%254085Apodex-1.1-mini +45
Risk20%207565Apertus v1.5 8B +10
Agent interface10%108585even
Documentation and upkeep10%108438Apertus v1.5 8B +46
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactApertus v1.5 8BApodex-1.1-mini
KindOpen-weight modelOpen-weight model
VendorSwiss AI Initiative (EPFL and ETH Zurich)Apodex 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 gateApache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-10-142026-08-25
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)3.3/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.

Apodex-1.1-mini

An agent cousin fine-tuned from Qwen3.5-35B-A3B for long tasks with files, code and tools, with parallel tool calling and about 3B active parameters. It needs 32 GB for Apodex's GGUF, NVFP4 or GPTQ-Int4 builds or about 86 GB in BF16, and Apodex's API serves it too. The main risks are no safety results and no replies from the publisher.

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

Apodex-1.1-mini

  1. Serve it with vllm serve apodex/Apodex-1.1-mini --enable-auto-tool-choice --tool-call-parser qwen3_coder --reasoning-parser qwen3, or the same parsers in SGLang, so tool calls and reasoning come back parsed
  2. For llama.cpp, llama-server -hf apodex/Apodex-1.1-mini-GGUF:Q4_K_M --jinja --reasoning-format deepseek, and the card passes the repository's chat_template.jinja with --chat-template-file
  3. Pass tools through the API's tools parameter rather than in the system prompt, as the card asks
  4. The card recommends temperature 1.0, top_p 0.95, repetition_penalty 1.05 and max_tokens up to 32,768
  5. Send your own system prompt, or set identity_mode, since the template otherwise adds an Apodex identity block
  6. The template keeps all earlier reasoning in the context unless preserve_thinking is false, which grows long agent sessions
  7. Thinking is on by default, send chat_template_kwargs with enable_thinking false for short tasks, a switch the card doesn't mention
  8. The card's Python example has a broken line where it runs the tool (available_toolsname), so fix it to available_tools[name](**args) before running
  9. Validate JSON output yourself, since structured output isn't documented

Questions

Which is better for AI agents, Apertus v1.5 8B or Apodex-1.1-mini?

Apertus v1.5 8B and Apodex-1.1-mini score within a point of each other on agent readiness, 61 (C) and 61 (C). Apodex-1.1-mini leads on reach.

Other comparisons with Apertus v1.5 8B or Apodex-1.1-mini

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.