Inkling vs Qwen3.5-122B-A10B

Inkling

Thinking Machines' large multimodal generalist, stronger than Inkling-Small on factual recall by its own numbers. It needs about 710 GB of datacentre GPU memory even in NVFP4, so most agents will use a host such as Together AI or Tinker. The main risks are a use policy that binds on download and can change, and no outside safety results.

Qwen3.5-122B-A10B

A strong mid-size cousin for coding, agent steps and reading images or video, with thinking you can switch off per request. Alibaba's 4-bit build needs about 95 GB, which fits one 128 GB unified-memory machine, and several providers host it. The main risk is silence, with no safety results, agent guidance or answers from Alibaba.

Inkling

1. Unless you have a multi-GPU Blackwell or H200 node, call it through Together AI, Fireworks, DeepInfra or Tinker rather than starting it
2. On 8 B200 GPUs, SGLang's recipe is sglang serve --trust-remote-code --model-path thinkingmachines/Inkling-NVFP4 --tp 8 --quantization modelopt_fp4 --enable-multimodal --reasoning-parser inkling --tool-call-parser inkling
3. Use the inkling tool parser, not Hermes, and the inkling reasoning parser
4. Pass reasoning_effort as none, minimal, low, medium, high (the default) or max, or a number from 0 to 0.99. The repository's template has no xhigh preset and raises an error for it, though Thinking Machines' docs list xhigh
5. Tool call arguments must reach the template as an object, not a JSON string, or it raises an error
6. Audio should be 16 kHz WAV, ideally under 20 minutes, and images 40 to 4096 px a side, per the card
7. Read the Model Acceptable Use Policy before deploying, it binds on download and bars some uses that are legal

Qwen3.5-122B-A10B

1. Quickest start on a 128 GB machine is ollama run qwen3.5:122b (Q4_K_M, 81 GB of files, about 97 GB with context)
2. Alibaba's 4-bit build serves with vllm serve Qwen/Qwen3.5-122B-A10B-GPTQ-Int4 --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder --quantization moe_wna16, though that kernel isn't documented for AMD gfx1151
3. Use the qwen3_coder tool parser and the qwen3 reasoning parser, as the card's commands do
4. Turn thinking off with "chat_template_kwargs": {"enable_thinking": false} in the request body, since it's on by default and /think and /nothink aren't supported
5. Sampling per the card is temperature 0.6, top_p 0.95 and top_k 20 when thinking, and temperature 0.7, top_p 0.8, top_k 20 and presence_penalty 1.5 without
6. Keep the context at 128K or more if you rely on thinking, and turn on YaRN only past 262,144 tokens
7. Add --language-model-only in vLLM to skip the vision encoder and free memory for the KV cache when you only need text
8. Validate any JSON it returns, since structured output isn't documented