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

Granite 4.2 3B vs Ornith-1.5-397B

Granite 4.2 3B and Ornith-1.5-397B score within a point of each other on agent readiness, 59.8 (C) and 59 (C). 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

Granite 4.2 3B C

Best for Agents on small hardware that want a permissive reasoning model for tool calls and coding, with thinking they can switch off

Ahead on

  • Reach, 95 against 65
  • Risk, 55 against 50
  • Documentation and upkeep, 92 against 36

Also in its favour

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

Watch for

No safety results published for 4.2, and only general safety cautions

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

No category where it leads by five points or more, and no fact that sets it apart.

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 runGranite 4.2 3BOrnith-1.5-397BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259565Granite 4.2 3B +30
Risk20%205550Granite 4.2 3B +5
Agent interface10%108585even
Documentation and upkeep10%109236Granite 4.2 3B +56
Negative events≤1500
TotalC 59.8/100C 59/100

Facts side by side

FactGranite 4.2 3BOrnith-1.5-397B
KindOpen-weight modelOpen-weight model
VendorIBMOrnith
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0MIT
Read-only variant documentednono
llms.txtnono
Last release2026-10-202026-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.8/5 (4)2/5 (4)

Verdicts

Granite 4.2 3B

A small reasoning cousin for tool calls, coding and multilingual chat that runs almost anywhere, from a 2.2 GB Ollama build to vLLM and SGLang, under plain Apache 2.0 with signed files and a dataset disclosure. Thinking turns off or shortens per request. It has no published safety results and no documented JSON mode.

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

Granite 4.2 3B

  1. Start it with ollama run granite4.2:3b; set options.num_ctx in the request, since Ollama's default context is short and the model takes up to 131,072
  2. With vLLM 0.32.0 or later, serve ibm-granite/granite-4.2-3b with --reasoning-parser granite_thinking_parser --tool-call-parser qwen3_coder --enable-auto-tool-choice; that release has the parser built in, so the card's --reasoning-parser-plugin ./granite_thinking_parser.py isn't needed
  3. With SGLang 0.5.18 or later, --reasoning-parser auto --tool-call-parser auto resolve to IBM's recommended parsers, and the reasoning comes back in reasoning_content
  4. Use temperature 1.0 and top_p 0.95 for every mode, as IBM requires
  5. Pass enable_thinking false for direct answers or low_effort true for short reasoning, through chat_template_kwargs on an OpenAI-compatible server
  6. Earlier turns' thinking is stripped by default (truncate_history_thinking), so pass it false to keep reasoning in multi-turn history
  7. For JSON, use the runtime's guided decoding, since IBM documents no JSON mode for 4.2
  8. Verify the files with python -m model_signing verify sigstore and IBM's identity, per IBM's signature guide

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, Granite 4.2 3B or Ornith-1.5-397B?

Granite 4.2 3B and Ornith-1.5-397B score within a point of each other on agent readiness, 59.8 (C) and 59 (C).

Other comparisons with Granite 4.2 3B 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.