Sign in

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

occamy-1.0 vs Ornith-1.5-122B

occamy-1.0 and Ornith-1.5-122B score within a point of each other on agent readiness, 61 (C) and 61 (C). Ornith-1.5-122B leads on agent interface. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 6359 open weights comparisons

occamy-1.0Accio (Accio-Lab) · Open-weight model C61/100#59 of 160 open-weight models Ornith-1.5-122BOrnith · Open-weight model C61/100#81 of 160 open-weight models

Which one, for what

occamy-1.0 C

Best for Agents that want an Apache 2.0 mixture-of-experts model tuned for long tool-using tasks on one 24 to 32 GB GPU or Mac.

Ahead on

  • Reach, 90 against 75
  • Risk, 55 against 50
  • Documentation and upkeep, 74 against 36

Watch for

No safety results, prompt-injection guidance or security contact

Ornith-1.5-122B C

Best for Local coding and terminal agents on a 128 GB unified-memory machine or a 96 GB GPU setup, where a clear licence file and an answering publisher aren't required

Ahead on

  • Agent interface, 85 against 70

Watch for

No LICENSE file though the card links one, and no notice for the Apache 2.0 Qwen3.5 and Gemma 4 work it builds on

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Documentation and upkeep occamy-1.0 +38

occamy-1.0 74

Model card 14 of 20, languages and a knowledge cut-off are missing. Training data 15, the mix by type with token counts, the method and a published subset, without a cut-off. Last change 20, Accio's GGUF build card changed on 19 October 2026 and the main card on 2 October. Responsiveness 10, Accio answered 4 of 9 questions. Version policy 5, a first release with no files replaced. File health 10, the files agree with the card. 14 + 15 + 20 + 10 + 5 + 10 = 74.

Ornith-1.5-122B 36

Model card 11, it covers intended use, architecture, parameters and context but not limitations, languages or a knowledge cut-off. Training data 5, a description of the method with no data or cut-off. Last change 20, a folder upload to the MLX builds on 24 October 2026, 17 days ago. Responsiveness 0, Ornith answered none of the 5 questions and reports. Version policy 0, the MLX builds were uploaded a second time four days after the first with no note. File health 0, the card links a missing LICENSE, states hardware its own files don't fit and names a variant that doesn't exist, and the two chat templates differ. 11 + 5 + 20 + 0 + 0 + 0 = 36.

Reach occamy-1.0 +15

occamy-1.0 90

Memory 25 of 30, Accio's MLX mxfp4 build is 18.4 GB, 22.1 GB with a fifth added, and its IQ4_XS GGUF needs 22.5 GB, both within 24 GB. Runtimes 25, the most the line gives, it keeps the base's qwen3_5_moe architecture, which llama.cpp, vLLM, SGLang and Transformers run in released versions, and Ollama v0.40.14 builds a llama.cpp (b11963) that has it. Builds 15, FP8, NVFP4, GGUF and MLX from Accio. Terms 15, Apache 2.0 like its base. Download 10, nothing is gated. Hosted 0, no API or inference provider serves it. 25 + 25 + 15 + 15 + 10 + 0 = 90.

Ornith-1.5-122B 75

Memory 10, since Ornith's own MLX 4-bit build is 69.7 GB and needs about 83.6 GB with the fifth added, over 64 GB and inside the reference machine's 107.4 GB, as do its Q4_K_M GGUF, its NVFP4 build and Ollama's build. Runtimes 25, the most the line gives, from vLLM 0.33.0, SGLang 0.5.23, Transformers 5.22.2, llama.cpp's qwen35moe architecture, Ollama's library and LM Studio's catalogue for the qwen35moe architecture. Builds 15, Ornith publishes FP8, NVFP4, GGUF and MLX at several precisions. Terms 15, MIT as named in the card's metadata, with nothing added, read by its terms though the repository has no licence file. Download 10, nothing is gated. Hosted 0, Ornith runs no API and no inference provider serves it. 10 + 25 + 15 + 15 + 10 + 0 = 75.

Agent interface Ornith-1.5-122B +15

occamy-1.0 70

Chat template 20, the base's Jinja template in the repository. Tool-calling format 10 of 25, the card names the parser but the format lives only in the template. Trained tool calling 20, trained on tool use with several calls a turn. Structured output 0, not documented. Reasoning control 10, enable_thinking per request and the card says to keep the returned reasoning content. Context 10, 262,144 tokens.

Ornith-1.5-122B 85

Chat template 20, a Jinja file in the repository. Tool-calling format 25, the card shows how tools go in and how calls come back and names the parser for vLLM and SGLang. Trained tool calling 20, Ornith trains it on agent tasks and the template renders several calls in one turn. Structured output 0, not documented or claimed. Reasoning control 10, Ornith's template reads enable_thinking per request and the card says the reasoning comes back in reasoning_content, though the card doesn't name the switch. Context 10, 262,144 tokens native.

Risk occamy-1.0 +5

occamy-1.0 55

File safety 25, safetensors only and nothing from the repository runs to load it or build prompts. Provenance 15, the files are in the organisation Accio's GitHub links, with MD5 sums and SHA-256 for every file. Safety evaluation 0, none published. Agent guidance 0. Licence risk 15, plain Apache 2.0 that hasn't changed. Security programme 0, bug reports go to public GitHub issues and there's no security contact.

Ornith-1.5-122B 50

File safety 25, safetensors and GGUF only and no Python in any of Ornith's repositories for this size, so the card's --trust-remote-code flag loads nothing from the repository. Provenance 15, the files come from the ornith-ai organisation Ornith's blog links to, with a SHA-256 for every weight file. Safety evaluation 0 and agent guidance 0, nothing published on either. Licence risk 10, MIT carries no policy, threshold or changeable terms, but the card's licence link is broken. Security programme 0, no security.txt, disclosure policy or security contact.

Score by category

CategoryWeight this runoccamy-1.0Ornith-1.5-122BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259075occamy-1.0 +15
Risk20%205550occamy-1.0 +5
Agent interface10%107085Ornith-1.5-122B +15
Documentation and upkeep10%107436occamy-1.0 +38
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

Factoccamy-1.0Ornith-1.5-122B
KindOpen-weight modelOpen-weight model
VendorAccio (Accio-Lab)Ornith
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0MIT
Read-only variant documentednono
llms.txtnono
Last release2026-10-022026-10-24
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviews3/5 (4)none

How the scores have moved

occamy-1.0

Ornith-1.5-122B

No score change since it was listed.

Verdicts

occamy-1.0

A Qwen3.6-35B-A3B fine-tuned for long agent work with tools, files and code, under plain Apache 2.0, and Accio's 4-bit builds run in about 23 GB. The main gaps are no safety results, agent guidance or security contact, and every benchmark figure is Accio's own.

Ornith-1.5-122B

The largest Ornith that fits a 128 GB machine, a coding and terminal-agent cousin on Qwen3.5-122B-A10B's architecture with XML tool calls and 262,144 tokens of context. Its 4-bit builds need 84 to 93 GB. The main risk is an absent publisher, with no licence file, safety results or replies, and a card that misstates the hardware.

Before you call either

occamy-1.0

  1. Serve with --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder on vLLM 0.19.0 or SGLang 0.5.10 and later
  2. BF16 is 70.2 GB, so on a 128 GB machine run it without the card's 8-way tensor parallelism
  3. Keep the whole assistant message, reasoning and tool calls included, in later turns, as the card says
  4. Sampling per the card is temperature 1.0, top_p 0.95, top_k 20 and presence_penalty 1.5
  5. With the GGUFs, NFC-normalise input text and read TOKENIZER.md, since the files store qwen2 pre-tokenizer metadata
  6. The base's MTP layer isn't in this checkpoint, Accio-Lab/occamy-1.0-MTP is an experimental separate head
  7. Ollama has no Occamy library entry, so load Accio's GGUF in Ollama 0.40.14 or later, which builds a llama.cpp with the qwen35moe architecture

Ornith-1.5-122B

  1. Start it with ollama run ornith-1.5:122b-q4_K_M, or llama-server -hf ornith-ai/Ornith-1.5-122B-GGUF:Q4_K_M --jinja -c 262144
  2. Budget about 92 GB for the Q4_K_M GGUF with a working context, and less context if the machine has under 100 GB for the model
  3. 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
  4. Thinking is on by default. Send chat_template_kwargs with enable_thinking false for short tasks, a switch the card doesn't mention
  5. Pin which template your runtime loads, since chat_template.jinja keeps earlier reasoning and the tokenizer_config.json template drops it
  6. Use temperature 0.6, top_p 0.95, top_k 20 for coding and temperature 1.0 for general tasks, as the card recommends
  7. Add mmproj-Ornith-1.5-122B-BF16.gguf (0.9 GB) for image input in llama.cpp, and validate JSON output yourself, since structured output isn't documented

Questions

Which is better for AI agents, occamy-1.0 or Ornith-1.5-122B?

occamy-1.0 and Ornith-1.5-122B score within a point of each other on agent readiness, 61 (C) and 61 (C). Ornith-1.5-122B leads on agent interface.

Other comparisons with occamy-1.0 or Ornith-1.5-122B

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.

Get an auditSee a sample report