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

GLM-5.3 vs Inkling 2 Mini

GLM-5.3 scores 64.6 (B) on agent readiness against Inkling 2 Mini's 61 (C), and leads in 1 of 4 scored categories. Inkling 2 Mini leads on reach, risk and agent interface. 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

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

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

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

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 55
  • Risk, 70 against 50
  • Agent interface, 85 against 70

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.

Risk Inkling 2 Mini +20

GLM-5.3 50

File safety is full, with safetensors only, no Python in the repository and no remote code needed in Transformers 5.12.0 or later. Provenance is full, files in the zai-org organisation Z.ai links to with a SHA-256 for every shard. Safety evaluation is 0, because the blog mentions safety evaluation and hardening but publishes no results, and agent guidance is 0, with nothing on refusals, prompt injection or cautions. Licence risk is 10, losing 5 for the security review that model-as-a-service operators above US$10 billion of revenue must pass. The security programme is 0, with no security.txt, no SECURITY.md and no advisories.

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.

Agent interface Inkling 2 Mini +15

GLM-5.3 70

A Jinja chat template sits in the repository, for 20. The tool-calling format is 10, since it is defined only by the template and the glm47 parser is named by vLLM and SGLang rather than by Z.ai. The template takes several calls in one turn, for 20. Structured output is 0, with nothing on the card and JSON documented only for the hosted API. Reasoning control is 10, a per-request budget through reasoning_effort with the reasoning in a think block, though thinking can't be turned off. Context is 10, 1,048,576 tokens native with no rope scaling.

Inkling 2 Mini 85

Chat template 20, chat_template.jinja in the repository. Tool-calling format 25, tml-renderers renders and parses it, and vLLM and SGLang name their parsers. Trained tool calling 20, several calls in one turn. Structured output 0, not documented. Reasoning control 10, reasoning_effort per request. Context 10, 1M trained. 20 + 25 + 20 + 0 + 10 + 10 = 85.

Reach Inkling 2 Mini +5

GLM-5.3 55

Memory earns nothing, since Z.ai's smallest build is the 755.6 GB FP8 one, about 907 GB with the fifth added, and Ollama only lists a cloud entry. Four runtimes run it in a released version, llama.cpp, vLLM, SGLang and Transformers, for 20, while Ollama and LM Studio have no local build. Z.ai publishes one quantised build, FP8, for 10, since the BF16 repository is the full precision. The GLM-5.3 License is a custom licence that is free for commercial use below a revenue threshold, for 10. The files download with no account or gate, for 10, and Z.ai's own API plus eight live providers on Hugging Face serve it, for 5.

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.

Score by category

CategoryWeightGLM-5.3Inkling 2 MiniEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%5560Inkling 2 Mini +5
Risk20%5070Inkling 2 Mini +20
Agent interface10%7085Inkling 2 Mini +15
Documentation and upkeep10%5857GLM-5.3 +1
Negative events≤1500
TotalB 64.6/100C 61/100

Facts side by side

FactGLM-5.3Inkling 2 Mini
KindOpen-weight modelOpen-weight model
VendorZ.ai (Zhipu AI)Thinking Machines Lab
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceGLM-5.3 License (MIT-style, with a security review for the largest model-as-a-service operators)Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-10-152026-11-20
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviews2.8/5 (4)none

Verdicts

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.

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

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

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, GLM-5.3 or Inkling 2 Mini?

GLM-5.3 scores 64.6 (B) on agent readiness against Inkling 2 Mini's 61 (C), and leads in 1 of 4 scored categories. Inkling 2 Mini leads on reach, risk and agent interface.

Other comparisons with GLM-5.3 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.