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

Nanbeige4.3-33B vs Ornith-1.5-397B

Nanbeige4.3-33B scores 61 (C) 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 3341 open weights comparisons

Which one, for what

Nanbeige4.3-33B C

Best for Agents with about 96 GB of GPU memory, or the 128 GB reference machine, that want an Apache-tagged 33B model for long coding and tool loops and can wait for independent results.

Ahead on

  • Risk, 60 against 50
  • Documentation and upkeep, 56 against 36

Watch for

No independent benchmark result yet; every agentic number on the card is Nanbeige's own run

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 55

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 runNanbeige4.3-33BOrnith-1.5-397BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255565Ornith-1.5-397B +10
Risk20%206050Nanbeige4.3-33B +10
Agent interface10%108585even
Documentation and upkeep10%105636Nanbeige4.3-33B +20
Negative events≤1500
TotalC 61/100C 59/100

Facts side by side

FactNanbeige4.3-33BOrnith-1.5-397B
KindOpen-weight modelOpen-weight model
VendorNanbeige LLM Lab (BOSS Zhipin)Ornith
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0 (Hub metadata only; the repository has no LICENSE file)MIT
Read-only variant documentednono
llms.txtnono
Last release2026-10-242026-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 reviewsnone2/5 (4)

Verdicts

Nanbeige4.3-33B

A dense 33B Llama-architecture cousin for long agentic coding and office tasks, with per-request thinking, XML tool calls that stock vLLM and SGLang parse, and 512K of context. It needs about 96 GB at BF16, as Nanbeige ships no quantised build. Its agentic results so far are Nanbeige's own, with no safety results, training data notes or licence file.

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

Nanbeige4.3-33B

  1. Serve with vllm serve Nanbeige/Nanbeige4.3-33B --enable-auto-tool-choice --reasoning-parser qwen3 --tool-call-parser qwen3_coder, as the card says, or SGLang with the same two parsers
  2. Keep tool_call_format at its default xml, since qwen3_coder parses that format; the json option writes Hermes-style JSON calls, which need a different parser such as vLLM's hermes
  3. Pass chat_template_kwargs {"preserve_thinking": true} for multi-turn tool use and coding, and {"enable_thinking": false} to skip reasoning, as the card recommends
  4. Use temperature 1.0, top_p 0.95 and up to 65,536 new tokens for agent work, and temperature 0.6 for reasoning and chat, per the card
  5. Send your own system prompt, since without one the template injects a Chinese identity line, or a Chinese tool-expert prompt when tools are passed
  6. Send one system message at the start only, as the template raises an error for a later one
  7. In plain Transformers pass use_cache=True to generate, since config.json and generation_config.json set it false; trust_remote_code isn't needed

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, Nanbeige4.3-33B or Ornith-1.5-397B?

Nanbeige4.3-33B scores 61 (C) 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 Nanbeige4.3-33B 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.