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

Granite 4.2 3B vs occamy-1.0

occamy-1.0 scores 61 (C) on agent readiness against Granite 4.2 3B's 59.8 (C), and leads in 0 of 4 scored categories. Granite 4.2 3B leads on reach, agent interface and documentation and upkeep. 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 85
  • Agent interface, 85 against 70
  • Documentation and upkeep, 92 against 74

Also in its favour

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

Watch for

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

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

Score by category

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

Facts side by side

FactGranite 4.2 3Boccamy-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
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)3/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.

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 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

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

Questions

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

occamy-1.0 scores 61 (C) on agent readiness against Granite 4.2 3B's 59.8 (C), and leads in 0 of 4 scored categories. Granite 4.2 3B leads on reach, agent interface and documentation and upkeep.

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