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

Granite 4.2 8B vs occamy-1.0

Granite 4.2 8B and occamy-1.0 score within a point of each other on agent readiness, 61 (C) and 61 (C). Both do open-weight models you run yourself.

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

Which one, for what

Granite 4.2 8B C

Best for Agents that want a documented, signed, Apache 2.0 reasoning model with tool calling on a 16 GB machine

Ahead on

  • Reach, 95 against 90
  • Agent interface, 85 against 70
  • Documentation and upkeep, 92 against 74

Watch for

No safety results published for it

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.

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

Watch for

No safety results, prompt-injection guidance or security contact

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 Granite 4.2 8B +18

Granite 4.2 8B 92

Model card 17, Intended use (best for), limitations (ethical considerations and limitations), architecture, parameters (8B), context length (128K native) and 12 tested languages are on the card. Training data 20, IBM's disclosure file for the 8B lists the datasets used in pre-training and post-training as machine-readable metadata, and the card describes the three training stages. Last change 20, the last commit, on 20 October 2026, replaced model.safetensors.index.json (titled "granite-4.2 index file fix"), 21 days before this check. Responsiveness 20, Of the 5 discussions that aren't pull requests (13 September to 5 November 2026), 4 have a reply from an ibm-granite member. Version policy 5, Granite 4.1 8B stays in its own repository and 4.2 came out in new ones. File health 10, Config, template and card agree on the architecture, the 131,072-token context and the thinking switch. 17 + 20 + 20 + 20 + 5 + 10 = 92.

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.

Agent interface Granite 4.2 8B +15

Granite 4.2 8B 85

Chat template 20, chat_template.jinja in the repository, with roles, tools, tool responses, the thinking switch and low effort. Tool-calling format 25, the card has tool-calling sections for vLLM and SGLang, declares tools with OpenAI's function schema and names the parser to use, qwen3_coder, which both runtimes ship in the released versions read. Trained tool calling 20, the template loops over every entry in an assistant turn's tool_calls, so it renders several calls in one turn, and the card names tool calling and agentic workflows as what it's best for. Structured output 0, the card doesn't document JSON or JSON Schema output or how to ask for it. Reasoning control 10, the card documents thinking on by default, non-thinking and low-effort modes per request through the template (enable_thinking and low_effort), with the reasoning returned apart from the answer. Context 10, 131,072 tokens natively per the card and config.json. 20 + 25 + 20 + 0 + 10 + 10 = 85.

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.

Reach Granite 4.2 8B +5

Granite 4.2 8B 95

Memory 30, IBM's own 4-bit MLX build granite-4.2-8b-q4-mlx is 4.95 GB, and 4.95 GB × 1.2 = 5.9 GB, within 8 GB. Its Q4_0 GGUF is 5.06 GB and Ollama's library build granite4.2:8b (5.3 GB) fits 8 GB too. Runtimes 25, Released versions run the granite architecture in llama.cpp (granite, b12242), vLLM (GraniteForCausalLM in the v0.33.0 registry), SGLang (granite.py at v0.5.23), Transformers (v5.22.2) and Ollama (its own granite4.2 library entry, 8b tag). Builds 15, IBM publishes FP8, MXFP4 and NVFP4 safetensors builds, a GGUF repository with Q4_0 to Q8_0 and BF16 files, and 4-bit, 8-bit and BF16 MLX builds, so quantised builds at two precisions or more. Terms 15, Apache 2.0, an OSI-approved licence, with no use policy or other terms added on the card. Download 10, the Hub API reports gated false for the BF16, FP8, MXFP4, NVFP4, GGUF and MLX repositories, so the files download with no account and nothing to accept. Hosted 0, Hugging Face maps one inference provider (DeepInfra, live), short of the two the line needs. 30 + 25 + 15 + 15 + 10 + 0 = 95.

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.

Score by category

CategoryWeight this runGranite 4.2 8Boccamy-1.0Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259590Granite 4.2 8B +5
Risk20%205555even
Agent interface10%108570Granite 4.2 8B +15
Documentation and upkeep10%109274Granite 4.2 8B +18
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactGranite 4.2 8Boccamy-1.0
KindOpen-weight modelOpen-weight model
VendorIBMAccio (Accio-Lab)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-10-202026-10-02
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone3/5 (4)

How the scores have moved

Verdicts

Granite 4.2 8B

IBM's mid-size reasoning cousin, with the same strengths as the 3B. It runs in every runtime we count from IBM's own builds on a 16 GB machine, is signed, plain Apache 2.0, and comes with a disclosure of its training data. No safety results are published and structured output isn't documented.

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.

Before you call either

Granite 4.2 8B

  1. Start it with ollama run granite4.2:8b, or llama-server -hf ibm-granite/granite-4.2-8b-GGUF:Q4_K_M --jinja
  2. With vLLM 0.32.0 or later leave out --reasoning-parser-plugin, since the parser is built in, and use --tool-call-parser qwen3_coder
  3. Thinking is on by default. Pass enable_thinking false to turn it off or low_effort true for short reasoning
  4. The context is 131,072 tokens. The card's 512K extension isn't documented
  5. Validate JSON output yourself, since structured output isn't documented
  6. IBM recommends Granite Guardian beside it to flag risky inputs and outputs

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

Questions

Which is better for AI agents, Granite 4.2 8B or occamy-1.0?

Granite 4.2 8B and occamy-1.0 score within a point of each other on agent readiness, 61 (C) and 61 (C).

Other comparisons with Granite 4.2 8B or occamy-1.0

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.