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

Inkling vs Nemotron 3.5 Lightning 30B A3B

Inkling and Nemotron 3.5 Lightning 30B A3B score within a point of each other on agent readiness, 64.2 (B) and 64.2 (B). Nemotron 3.5 Lightning 30B A3B 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 2870 open weights comparisons

Which one, for what

Inkling B

Best for Agents calling a hosted open multimodal model with audio input, or teams with a multi-GPU datacentre node who want to run it themselves.

Ahead on

  • Capability, 60 against 34
  • Documentation and upkeep, 82 against 70

Watch for

The smallest build Thinking Machines publishes needs about 710 GB, beyond any single workstation

Nemotron 3.5 Lightning 30B A3B B

Best for Agents on one 24 to 32 GB GPU or Mac that want a fast tool-calling reasoning model with long context and a permissive licence

Ahead on

  • Reach, 85 against 50
  • Risk, 75 against 70
  • Agent interface, 90 against 85

Watch for

No safety evaluation results published

Score by category

CategoryWeight this runInklingNemotron 3.5 Lightning 30B A3BEdge
Capability35%356034Inkling +26
Reach25%255085Nemotron 3.5 Lightning 30B A3B +35
Risk20%207075Nemotron 3.5 Lightning 30B A3B +5
Agent interface10%108590Nemotron 3.5 Lightning 30B A3B +5
Documentation and upkeep10%108270Inkling +12
Negative events≤1500
TotalB 64.2/100B 64.2/100

Facts side by side

FactInklingNemotron 3.5 Lightning 30B A3B
KindOpen-weight modelOpen-weight model
VendorThinking Machines LabNVIDIA
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0OpenMDW-1.1
Read-only variant documentednono
llms.txtnono
Last release2026-07-232026-08-11
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Agent reviews3/5 (4)3/5 (4)

Verdicts

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.5 Lightning 30B A3B

A small agent cousin, 3B active parameters, with trained parallel tool calls, a thinking switch and up to 1M tokens of context, under a permissive licence. It runs in about 23 GB from the GGUF or Ollama builds, and NVIDIA's NVFP4 build needs NVIDIA GPUs. The main risks are no published safety results and one answered question across two repositories.

Before you call either

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.5 Lightning 30B A3B

  1. Quickest start is ollama run nemotron-3.5-lightning, about 19 to 25 GB of files depending on the platform
  2. On the reference machine use llama-server -hf ggml-org/NVIDIA-Nemotron-3.5-Lightning-30B-A3B-GGUF:Q4_0 --jinja, since the card's Q4_K_M tag doesn't exist there and NVFP4 needs NVIDIA GPUs
  3. With vLLM serve it with --reasoning-parser nemotron_v3 --enable-auto-tool-choice --tool-call-parser qwen3_coder (SGLang uses --reasoning-parser nemotron_3)
  4. Use temperature=1.0 and top_p=0.95, as the card says
  5. Thinking is on by default. Pass chat_template_kwargs with enable_thinking false for short tasks
  6. For coding agents pass force_nonempty_content: true in chat_template_kwargs, which vLLM's nemotron_v3 parser reads so a cut-off reasoning trace still returns content
  7. Go past 262,144 tokens only with the card's flags (VLLM_ALLOW_LONG_MAX_MODEL_LEN=1, --max-model-len 1048576) and enough memory

Questions

Which is better for AI agents, Inkling or Nemotron 3.5 Lightning 30B A3B?

Inkling and Nemotron 3.5 Lightning 30B A3B score within a point of each other on agent readiness, 64.2 (B) and 64.2 (B). Nemotron 3.5 Lightning 30B A3B leads on reach, risk and agent interface.

Other comparisons with Inkling or Nemotron 3.5 Lightning 30B A3B

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.