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

Apertus v1.5 8B vs Inkling 2 Mini

Apertus v1.5 8B and Inkling 2 Mini score within a point of each other on agent readiness, 61 (C) and 61 (C). Inkling 2 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 6586 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 70
  • Documentation and upkeep, 84 against 57

Watch for

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

Inkling 2 Mini C

Best for Developers with a 32 GB laptop or a single GPU who want a small open agent model with images in and a 1M context, and can run a runtime's pre-release build.

Ahead on

  • Reach, 60 against 40

Watch for

No released version of vLLM, SGLang, Transformers, llama.cpp or Ollama runs it on 20 November 2026

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 +27

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.

Inkling 2 Mini 57

Model card 17, no knowledge cut-off. Training data 5, a general description with no cut-off and no summary for this model yet. Last change 20, uploaded today. Responsiveness 0, two questions and none answered within the first hour. Version policy 5, a first release. File health 10, the files and the card agree. 17 + 5 + 20 + 0 + 5 + 10 = 57.

Reach Inkling 2 Mini +20

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.

Inkling 2 Mini 60

Memory 25 of 30, ggml-org's IQ4_NL GGUF with its vision projector is 17.98 GB, about 21.6 GB with a fifth added. Runtimes 0, no released version of the six runs the looped architecture; vLLM and SGLang serve it from their own images and llama.cpp has it on master only. Builds 10, one checkpoint from the publisher in mixed NVFP4 and MXFP8. Terms 10, Apache 2.0 with a binding acceptable use policy on top, read as a custom licence. Download 10, no gate. Hosted 5, Thinking Machines' own Tinker samples from it. 25 + 0 + 10 + 10 + 10 + 5 = 60.

Risk Apertus v1.5 8B +5

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.

Inkling 2 Mini 70

File safety 25, safetensors only and no repository code to run. Provenance 15, the files are in the organisation Thinking Machines links to, with a SHA-256 on every LFS file. Safety evaluation 10, Thinking Machines' own evaluations and monitorability results, nothing an outside party published or a harness to rerun. Agent guidance 10, the card says what the safety work covered and names safeguards for agent use (a sandbox, confirmation before destructive actions), with nothing on prompt injection. Licence risk 5, 10 off for a use policy that reaches beyond the law and that can change at any time. Security 5, security.txt and a disclosure policy. 25 + 15 + 10 + 10 + 5 + 5 = 70.

Score by category

CategoryWeightApertus v1.5 8BInkling 2 MiniEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%4060Inkling 2 Mini +20
Risk20%7570Apertus v1.5 8B +5
Agent interface10%8585even
Documentation and upkeep10%8457Apertus v1.5 8B +27
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactApertus v1.5 8BInkling 2 Mini
KindOpen-weight modelOpen-weight model
VendorSwiss AI Initiative (EPFL and ETH Zurich)Thinking Machines Lab
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-11-20
Terms last updatednot read yetno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviews2.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.

Inkling 2 Mini

Thinking Machines' small open model, a looped 26.4B mixture-of-experts with images in, several tool calls a turn and per-request thinking effort, in one 20 GB checkpoint that fits a 32 GB laptop. No released runtime runs it yet, so today it's vLLM's or SGLang's images, llama.cpp from master, or Tinker.

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 tokenisers 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

Inkling 2 Mini

  1. No released runtime runs it yet. Serve it from vLLM's vllm/vllm-openai:inkling-2-mini image with --reasoning-parser inkling --enable-auto-tool-choice --tool-call-parser inkling, or from SGLang's lmsysorg/sglang:inkling-2-mini image, where the tool-call parser is inkling2
  2. On a laptop, ggml-org's GGUF runs in a llama.cpp built after b12591: llama-server -hf ggml-org/Inkling-2-Mini-GGUF:IQ4_NL. The looped architecture isn't in a llama.cpp release yet
  3. Pass reasoning_effort as none, minimal, low, medium, high (the default), xhigh or max, or a number from 0 to 0.99. The minimum doesn't fully turn reasoning off
  4. The card says it can get stuck re-checking its own work, so cap output tokens and agent turns
  5. Run it in a sandbox and confirm destructive actions: the card says it may delete or overwrite files without asking and misreport what it did
  6. Tool call arguments must reach the template as an object, not a JSON string, as for Inkling 2 Small
  7. Images should be 40 to 4096 px a side. It takes no audio, and the template raises an error for an audio part
  8. Use guided decoding or validate JSON yourself, since structured output isn't documented
  9. Without the hardware, sample from it on Tinker with the Tinker SDK; Tinker's OpenAI-compatible endpoint doesn't serve it yet
  10. Read the Model Acceptable Use Policy before deploying, it binds on download and bars some uses that are legal

Questions

Which is better for AI agents, Apertus v1.5 8B or Inkling 2 Mini?

Apertus v1.5 8B and Inkling 2 Mini score within a point of each other on agent readiness, 61 (C) and 61 (C). Inkling 2 Mini leads on reach.

Other comparisons with Apertus v1.5 8B or Inkling 2 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.