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

Inkling 2 Small vs Nanbeige4.3-33B

Nanbeige4.3-33B scores 60.8 (C) on agent readiness against Inkling 2 Small's 58.8 (C), and leads in 1 of 4 scored categories. Inkling 2 Small leads on risk 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 6472 open weights comparisons

Which one, for what

Inkling 2 Small C

Best for Teams with 512 GB or more of datacentre GPU memory who want Thinking Machines' newest open multimodal agent model and can run a runtime's pre-release image.

Ahead on

  • Risk, 65 against 60
  • Documentation and upkeep, 67 against 56

Watch for

The smaller checkpoint needs about 472 GB, and Thinking Machines says 500 GB of GPU memory

Nanbeige4.3-33B C

Best for Agents with a 32 GB GPU (INT4) or more, or the 128 GB reference machine at BF16, that want an Apache-tagged 33B model for long coding and tool loops.

Ahead on

  • Reach, 80 against 40

Watch for

Independent results so far are Artificial Analysis's alone (Intelligence Index v5.0 20.4, Terminal-Bench 4.0 29.8 per cent); the card's other agentic numbers are Nanbeige's own runs

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.

Reach Nanbeige4.3-33B +40

Inkling 2 Small 40

Memory 0 of 30, the smallest build is Thinking Machines' NVFP4 checkpoint at 393.5 GB, about 472 GB with a fifth added, above the 256 GB line. Runtimes 0, no released version of the six runs it; vLLM and SGLang serve it from their own images and Transformers has it on its main branch only. Builds 15, two precisions from the publisher (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 serves it as beta serverless inference, and Together is live on Hugging Face. 0 + 0 + 15 + 10 + 10 + 5 = 40.

Nanbeige4.3-33B 80

Memory earns 20, since Nanbeige's INT4 build is 22.57 GB, about 27 GB with a fifth added, which fits 32 GB. Runtimes earn 20 from released vLLM, SGLang, Transformers and llama.cpp, which all run the Llama architecture, and Ollama and LM Studio have no build. Builds earn 15 for Nanbeige's INT4, INT8 and FP8 builds of 31 October 2026. Terms earn 15 for Apache 2.0 with nothing added, though only the metadata names it. Download earns 10, with no gate. Hosted earns 0, as no provider or Nanbeige API serves it.

Documentation and upkeep Inkling 2 Small +11

Inkling 2 Small 67

Model card 17 of 20, everything but a dated knowledge cut-off. Training data 15, an EU training-content summary with sources, mix, an October 2026 collection cut-off and filtering. Last change 20, the files were uploaded on 12 November 2026. Responsiveness 0, the repository has no questions yet, which reads as none answered. Version policy 5, a first release. File health 10, the files agree and no broken-file report waits. 17 + 15 + 20 + 0 + 5 + 10 = 67.

Nanbeige4.3-33B 56

The model card earns 11, with intended use, parameters, context and languages but no limitations, architecture or cut-off. Training data earns 0, as nothing describes it. Last change earns 20 for the quantised builds of 31 October 2026. Responsiveness earns 10, a Nanbeige member answering nine of 30 discussions. Version policy earns 5 for a first release, with a config change made and reverted under bare commit titles. File health earns 10, the files and the card agreeing.

Risk Inkling 2 Small +5

Inkling 2 Small 65

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 StrongREJECT, FORTRESS, HoneyBench and DistressBench results and described outside red-teaming, but nothing an outside party published or a harness to rerun. Agent guidance 5, the card names safeguards to add but doesn't say what its refusals cover, 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 programme 5, a security.txt and a disclosure policy, with public advisories unchecked and scored as absent. 25 + 15 + 10 + 5 + 5 + 5 = 65.

Nanbeige4.3-33B 60

File safety earns 25, safetensors only and no repository code, so the card's trust_remote_code has nothing to run. Provenance earns 15, the lab's own organisation as its arXiv report links it, with a hash for every file. Safety evaluation earns 0 and agent guidance 0, since neither card says anything on either. Licence risk keeps all 15 under Apache 2.0. The security programme earns 5 for BOSS Zhipin's security response centre, which isn't linked to the model.

Score by category

CategoryWeight this runInkling 2 SmallNanbeige4.3-33BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%254080Nanbeige4.3-33B +40
Risk20%206560Inkling 2 Small +5
Agent interface10%108585even
Documentation and upkeep10%106756Inkling 2 Small +11
Negative events≤1500
TotalC 58.8/100C 60.8/100

Facts side by side

FactInkling 2 SmallNanbeige4.3-33B
KindOpen-weight modelOpen-weight model
VendorThinking Machines LabNanbeige LLM Lab (BOSS Zhipin)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0 (Hub metadata only; the repository has no LICENSE file)
Read-only variant documentednono
llms.txtnono
Last release2026-11-122026-10-31
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked

How the scores have moved

Verdicts

Inkling 2 Small

Thinking Machines' newest open model, a 594B mixture-of-experts generalist with images in, several tool calls a turn and per-request thinking effort. The NVFP4 checkpoint needs about 472 GB, and no released runtime runs it yet, so today that means vLLM's or SGLang's own images, or Tinker and Together hosted. The use policy binds on download and can change.

Nanbeige4.3-33B

A dense 33B Llama-architecture cousin for long agentic coding and office tasks, with per-request thinking, XML tool calls that stock vLLM and SGLang parse, and 512K of context. Nanbeige's INT4 build needs about 27 GB. Artificial Analysis's first independent runs give it 20.4 on its Intelligence Index, and there are no safety results, training data notes or licence file.

Before you call either

Inkling 2 Small

  1. No released runtime runs it yet. Serve the NVFP4 checkpoint from SGLang's dev-inkling-2-small image with the cookbook's recipe for your hardware, or from vLLM's vllm/vllm-openai:inkling-2-small image
  2. In vLLM pass --reasoning-parser inkling --enable-auto-tool-choice --tool-call-parser inkling. In SGLang the tool-call parser is inkling2 and the reasoning parser inkling
  3. Transformers' main branch loads only thinkingmachines/Inkling-2-Small-MXFP8, the 622.8 GB checkpoint, and no release has the code yet
  4. Pass reasoning_effort as none, minimal, low, medium, high (the default), xhigh or max, or a number from 0 to 0.99
  5. Effort none conditions the model toward no reasoning but doesn't forbid it, and higher effort needs a larger max_tokens
  6. Tool call arguments must reach the template as an object, not a JSON string, or it raises an error
  7. Images should be 40 to 4096 px a side. The model 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, call it on Tinker's OpenAI-compatible endpoint with a Tinker key, at $0.30 input and $1.00 output per million tokens as read on 6 November 2026
  10. Read the Model Acceptable Use Policy before deploying, it binds on download and bars some uses that are legal

Nanbeige4.3-33B

  1. Serve with vllm serve Nanbeige/Nanbeige4.3-33B --enable-auto-tool-choice --reasoning-parser qwen3 --tool-call-parser qwen3_coder, as the card says, or SGLang with the same two parsers
  2. On a 32 GB GPU use Nanbeige/Nanbeige4.3-33B-INT4 with the same vLLM or SGLang flags; the INT8 and FP8 builds need about 43 GB
  3. Keep tool_call_format at its default xml, since qwen3_coder parses that format; the json option writes Hermes-style JSON calls, which need a different parser such as vLLM's hermes
  4. Pass chat_template_kwargs {"preserve_thinking": true} for multi-turn tool use and coding, and {"enable_thinking": false} to skip reasoning, as the card recommends
  5. Use temperature 1.0, top_p 0.95 and up to 65,536 new tokens for agent work, and temperature 0.6 for reasoning and chat, per the card
  6. Send your own system prompt, since without one the template injects a Chinese identity line, or a Chinese tool-expert prompt when tools are passed
  7. Send one system message at the start only, as the template raises an error for a later one
  8. In plain Transformers pass use_cache=True to generate, since config.json and generation_config.json set it false; trust_remote_code isn't needed

Questions

Which is better for AI agents, Inkling 2 Small or Nanbeige4.3-33B?

Nanbeige4.3-33B scores 60.8 (C) on agent readiness against Inkling 2 Small's 58.8 (C), and leads in 1 of 4 scored categories. Inkling 2 Small leads on risk and documentation and upkeep.

Other comparisons with Inkling 2 Small or Nanbeige4.3-33B

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.