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

Inkling vs Ornith-1.5-397B

Inkling scores 64.2 (B) on agent readiness against Ornith-1.5-397B's 59 (C), and leads in 2 of 4 scored categories. Ornith-1.5-397B 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

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 50
  • Documentation and upkeep, 82 against 36

Also in its favour

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

Watch for

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

Ornith-1.5-397B C

Best for A self-hosted frontier-scale coding agent on an 8-GPU server, where a clear licence file and an answering publisher aren't required

Ahead on

  • Reach, 65 against 50

Watch for

Needs about 290 GB of memory at 4 bits and about 970 GB in BF16, so it doesn't fit the reference machine

Score by category

CategoryWeight this runInklingOrnith-1.5-397BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255065Ornith-1.5-397B +15
Risk20%207050Inkling +20
Agent interface10%108585even
Documentation and upkeep10%108236Inkling +46
Negative events≤1500
TotalB 64.2/100C 59/100

Facts side by side

FactInklingOrnith-1.5-397B
KindOpen-weight modelOpen-weight model
VendorThinking Machines LabOrnith
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0MIT
Read-only variant documentednono
llms.txtnono
Last release2026-07-232026-08-23
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)2/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.

Ornith-1.5-397B

Ornith's flagship coding and terminal-agent cousin, with XML tool calls that vLLM and SGLang parse and 262,144 tokens of context. It needs about 290 GB even at 4 bits, so a multi-GPU server, not the 128 GB reference machine. The main risk is an absent publisher, with no licence file, no safety results and files replaced without a note.

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

Ornith-1.5-397B

  1. Start it with the card's vLLM command at --tensor-parallel-size 8, or ollama run ornith-1.5:397b on a machine with about 300 GB of memory
  2. In vLLM pass --enable-auto-tool-choice --tool-call-parser qwen3_xml --reasoning-parser qwen3, and in SGLang --tool-call-parser qwen3_coder --reasoning-parser qwen3, so tool calls and reasoning come back parsed
  3. Thinking is on by default. Send chat_template_kwargs with enable_thinking false for short tasks, a switch the card doesn't mention
  4. Pin which template your runtime loads, since chat_template.jinja keeps earlier reasoning and the tokenizer_config.json template drops it
  5. When downloading the NVFP4 build, fetch only the files its model.safetensors.index.json names (the 25-shard set, 241.7 GB), not the eight extra shards
  6. Pin a revision when you download, since Ornith has replaced files in place
  7. Validate JSON output yourself, since structured output isn't documented

Questions

Which is better for AI agents, Inkling or Ornith-1.5-397B?

Inkling scores 64.2 (B) on agent readiness against Ornith-1.5-397B's 59 (C), and leads in 2 of 4 scored categories. Ornith-1.5-397B leads on reach.

Other comparisons with Inkling or Ornith-1.5-397B

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.