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

Granite 4.2 30B vs ZAYA1-8B

Granite 4.2 30B and ZAYA1-8B 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 6359 open weights comparisons

Which one, for what

Granite 4.2 30B C

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

Ahead on

  • Reach, 90 against 80
  • Agent interface, 85 against 60
  • Documentation and upkeep, 87 against 50

Watch for

No safety results published for it

ZAYA1-8B C

Best for People who want a small, fast reasoning model for maths and code and can live without tool calling

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

Watch for

Tool calling needs a parser that only Zyphra's vLLM fork has

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 30B +37

Granite 4.2 30B 87

Model card 17, Intended use (best for), limitations (ethical considerations and limitations), architecture, parameters (30B), context length (128K native) and 12 tested languages are on the card. Training data 20, IBM's disclosure file for the 30B lists the datasets used in pre-training and post-training as machine-readable metadata, and the card describes the three training stages. Last change 15, the last commit to the repository was on 4 September 2026, 67 days before this check. Responsiveness 20, Of the 4 discussions that aren't pull requests (28 August to 3 November 2026), 3 have a reply from an ibm-granite member. Version policy 5, Granite 4.1 30B 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 + 15 + 20 + 5 + 10 = 87.

ZAYA1-8B 50

Model card 5, Intended use and the parameter counts are on the card. Training data 0, Nothing on the card about the training data. Last change 10, the main repository last changed on 26 June 2026 (the checkpoint reshaped for Transformers), 137 days before this check, and the quantised repositories on 2 July, 131 days. Responsiveness 20, Of the 16 most recent discussions that aren't pull requests (7 May to 14 August 2026), 10 have a reply from a Zyphra member, which is most. Version policy 5, the original checkpoint is kept as ZAYA1-8B-legacy and the card says so at the top, without a date. File health 10, Config, template and card agree on the architecture after the reshape. 5 + 0 + 10 + 20 + 5 + 10 = 50.

Agent interface Granite 4.2 30B +25

Granite 4.2 30B 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.

ZAYA1-8B 60

Chat template 20, chat_template.jinja in the repository (10,700 characters). Tool-calling format 10, only the template and a fork say it. Trained tool calling 10, the template takes tools and renders calls, and the card recommends settings for agent use, but it doesn't say the model was trained for tool calling or for several calls in a turn, so the lower band. Structured output 0, Nothing on the card about JSON or schema-constrained output. Reasoning control 10, the template has an enable_thinking switch, and the card names the qwen3 reasoning parser, which returns the reasoning apart from the answer. Context 10, 131,072 positions in config.json, for an architecture Zyphra trained end to end, so the config is the model's own. 20 + 10 + 10 + 0 + 10 + 10 = 60.

Reach Granite 4.2 30B +10

Granite 4.2 30B 90

Memory 25, IBM's own 4-bit MLX build granite-4.2-30b-q4-mlx is 16.47 GB, and 16.47 GB × 1.2 = 19.8 GB, which fits 24 GB but not 16 GB. Its Q4_0 GGUF is 16.58 GB and Ollama's library build granite4.2:30b 18 GB, the same band. 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, 30b 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. 25 + 25 + 15 + 15 + 10 + 0 = 90.

ZAYA1-8B 80

Memory 30, the smallest build from Zyphra is the MXFP4-Experts repository, 5.85 GB, and 5.85 GB × 1.2 = 7.0 GB, within 16 GB. Runtimes 10, Released Transformers 5.22.2 has the zaya model and SGLang 0.5.23 has srt/models/zaya.py. Builds 15, Quantised builds from Zyphra at two precisions, FP8 and MXFP4 for the experts, each in its own repository. Terms 15, Apache 2.0 in the card's metadata, an OSI licence with nothing added. Download 10, the Hub API reports gated false for the model and its builds on 10 November 2026, so the files download with no account and nothing to accept. Hosted 0, Hugging Face maps no inference provider to it, and the card names no API. Zyphra's site lists a cloud product for its open models, which wasn't checked for this model. 30 + 10 + 15 + 15 + 10 + 0 = 80.

Score by category

CategoryWeight this runGranite 4.2 30BZAYA1-8BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259080Granite 4.2 30B +10
Risk20%205555even
Agent interface10%108560Granite 4.2 30B +25
Documentation and upkeep10%108750Granite 4.2 30B +37
Negative events≤1500
TotalC 61/100C 61/100

Facts side by side

FactGranite 4.2 30BZAYA1-8B
KindOpen-weight modelOpen-weight model
VendorIBMZyphra
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-09-042026-07-02
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked

Verdicts

Granite 4.2 30B

IBM's largest reasoning cousin, with the same strengths as the 3B. It runs in every runtime we count from IBM's own builds on a 24 GB card, 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.

ZAYA1-8B

A small reasoning model trained from scratch by one lab, with a clean licence, 4-bit and FP8 builds and a team that answers questions. It's the hardest of the small models to run: its own architecture, a card that points at forks, and tool calling that needs a parser no release has. Little on limits, data or safety.

Before you call either

Granite 4.2 30B

  1. Start it with ollama run granite4.2:30b, or llama-server -hf ibm-granite/granite-4.2-30b-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

ZAYA1-8B

  1. Use it for reasoning, maths and code. Don't count on tool calling outside Zyphra's vLLM fork
  2. Run it with Transformers 5.22.2 or SGLang 0.5.23, which have the model built in
  3. Use temperature 1.0 and top_p 0.95 in general, and temperature 0.6 for agent and code work
  4. Download Zyphra/ZAYA1-8B, not the legacy repository, for the released runtimes
  5. The quantised repositories have no licence tag. The main one is Apache 2.0

Questions

Which is better for AI agents, Granite 4.2 30B or ZAYA1-8B?

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

Other comparisons with Granite 4.2 30B or ZAYA1-8B

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.