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

Cosmos-Reason2-2B vs Inkling

Inkling scores 64.2 (B) on agent readiness against Cosmos-Reason2-2B's 59.5 (C), and leads in 3 of 4 scored categories. Cosmos-Reason2-2B leads on reach. 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

Cosmos-Reason2-2B C

Best for Agents that need a small local model to reason over camera footage and images for robotics, driving or smart spaces

Ahead on

  • Reach, 65 against 50

Watch for

Gated behind a click-through licence that needs a Hugging Face account

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

  • Risk, 70 against 60
  • Agent interface, 85 against 65
  • Documentation and upkeep, 82 against 39

Also in its favour

  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5

Watch for

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

Score by category

CategoryWeight this runCosmos-Reason2-2BInklingEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256550Cosmos-Reason2-2B +15
Risk20%206070Inkling +10
Agent interface10%106585Inkling +20
Documentation and upkeep10%103982Inkling +43
Negative events≤1500
TotalC 59.5/100B 64.2/100

Facts side by side

FactCosmos-Reason2-2BInkling
KindOpen-weight modelOpen-weight model
VendorNVIDIAThinking Machines Lab
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceNVIDIA Open Model License (custom, commercial use allowed, not an OSI licence); built on Qwen3-VL-2B-Instruct under Apache 2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-03-102026-07-23
Terms last updatedno 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 reviews2.5/5 (4)3/5 (4)

Verdicts

Cosmos-Reason2-2B

A small local cousin for reasoning over video and images in robotics, driving and warehouse scenes, returning points, boxes and timed events as JSON. The 4.9 GB file runs in Transformers or vLLM, though NVIDIA asks for 24 GB of GPU memory. Development has moved to Cosmos 3, and the gated licence is revocable.

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.

Before you call either

Cosmos-Reason2-2B

  1. Accept the licence on the Hugging Face card with a signed-in account and set HF_TOKEN before downloading
  2. Serve it with vllm serve nvidia/Cosmos-Reason2-2B --max-model-len 16384 --media-io-kwargs '{"video": {"num_frames": -1}}' --reasoning-parser qwen3, keeping max-model-len between 8,192 and 16,384 as NVIDIA advises
  3. For local video or images, make a folder for them (mkdir -p media) and pass --allowed-local-media-path "$(pwd)/media", so the server can read only that folder, not everything under the directory you start it from
  4. Sample video at 4 fps and allow at least 4,096 output tokens so the reasoning isn't cut off
  5. For reasoning, add the card's instruction to answer with a think block and then the answer; leave it out for a direct reply
  6. Use NVIDIA's prompt files (prompts/*.yaml in nvidia-cosmos/cosmos-reason2) when you want JSON boxes, events or trajectories, and validate the JSON yourself
  7. Check its plans before a robot acts on them, since NVIDIA's own safety card warns of collision and manipulation risks

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

Questions

Which is better for AI agents, Cosmos-Reason2-2B or Inkling?

Inkling scores 64.2 (B) on agent readiness against Cosmos-Reason2-2B's 59.5 (C), and leads in 3 of 4 scored categories. Cosmos-Reason2-2B leads on reach.

Other comparisons with Cosmos-Reason2-2B or Inkling

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.