Inkling vs Nemotron 3 Nano Omni 30B A3B Reasoning

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.

Nemotron 3 Nano Omni 30B A3B Reasoning

A local multimodal cousin for video with speech, long documents, charts, screens and English transcription, with tool calling, a reasoning switch and a 262,144-token context. It needs about 27 GB for NVIDIA's NVFP4 build on Blackwell, or 42 GB for FP8. The main risks are the remote code it loads and a repository where nobody answers questions.

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

Nemotron 3 Nano Omni 30B A3B Reasoning

1. Start it with vllm serve nvidia/Nemotron-3-Nano-Omni-30B-A3B-Reasoning-FP8 --max-model-len 131072 --trust-remote-code --reasoning-parser nemotron_v3 --enable-auto-tool-choice --tool-call-parser qwen3_coder --kv-cache-dtype fp8 on vLLM 0.20.0 or later, after pip install "vllm[audio]" if any audio will be sent
2. Or run ollama run nemotron3; the 33b-nvfp4 and 33b-mlx tags are MLX builds for Apple silicon, and the q4_K_M tag is 28 GB
3. Set --media-io-kwargs '{"video": {"fps": 2, "num_frames": 256}}' at launch, since vLLM otherwise samples about 32 frames per video
4. Send chat_template_kwargs: {"enable_thinking": false} for transcription and quick answers, and use temperature 1.0 with top_k 1 for ASR as the card recommends
5. Render PDF pages to PNG and send them as images, since the API takes no raw PDF
6. Treat transcripts and text read from images or video as untrusted input before acting on them