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

Inkling-Small vs ZAYA1-8B

Inkling-Small scores 67 (B) on agent readiness against ZAYA1-8B's 61 (C), and leads in 3 of 4 scored categories. ZAYA1-8B leads on reach. 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

Inkling-Small B

Best for Teams with 256 GB or more of datacentre GPU memory who want an open multimodal agent model with audio input and adjustable thinking.

Ahead on

  • Risk, 70 against 55
  • Agent interface, 85 against 60
  • Documentation and upkeep, 87 against 50

Watch for

The smallest build Thinking Machines publishes needs about 205 GB

ZAYA1-8B C

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

Ahead on

  • Reach, 80 against 55

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 Inkling-Small +37

Inkling-Small 87

Model card 17 of 20, everything but a dated knowledge cut-off, counting Thinking Machines' own model card page. Training data 15, an EU training-content summary with sources, mix, a July 2026 collection cut-off and filtering. Last change 20, the files last changed on 31 July 2026, but Thinking Machines' Inkling renderer in tinker-cookbook changed in its 30 October 2026 release. Responsiveness 20, Thinking Machines answered 8 of the 9 questions in its discussions. Version policy 5, a first release. File health 10, the files agree and no broken-file report waits. 17+15+20+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.

Reach ZAYA1-8B +25

Inkling-Small 55

Memory 5 of 30, the smallest 4-bit build is Thinking Machines' NVFP4 at 170.8 GB, about 205 GB with a fifth added, so it needs 256 GB. Runtimes 15, released Transformers, vLLM and SGLang run it, llama.cpp, Ollama and LM Studio don't. Builds 10, one quantised build (NVFP4). Terms 10, Apache 2.0 with a binding acceptable use policy on top, read as a custom licence. Download 10, no gate. Hosted 5, Thinking Machines' own Tinker serves it as beta serverless inference, and DeepInfra is live on Hugging Face.

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.

Agent interface Inkling-Small +25

Inkling-Small 85

Chat template 20, a Jinja file in the repository. Tool-calling format 25, Thinking Machines' tml-renderers guide shows how tools are declared and how calls come back, and its package ships the parser. Trained tool calling 20, several calls in one turn. Structured output 0, not documented. Reasoning control 10, thinking effort is set per request from none to the maximum, and the reasoning comes back in reasoning_content. Context 10, up to 1M tokens.

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.

Risk Inkling-Small +15

Inkling-Small 70

File safety 25, safetensors only and no repository code to run. Provenance 15, the files are in the organisation Thinking Machines links to, with a SHA-256 on every LFS file. Safety evaluation 10, Thinking Machines' own StrongREJECT and FORTRESS results and described external red-teaming, but nothing an outside party published or a harness to rerun. Agent guidance 10, the card says what its refusals miss and which safeguards to add, with nothing on prompt injection. Licence risk 5, 10 off for a use policy that reaches beyond the law and that can change at any time. Security programme 5, a security.txt and a disclosure policy, with public advisories unchecked and scored as absent.

ZAYA1-8B 55

File safety 25, safetensors only, no .bin, .pt or .pth files and no Python in the repository. Provenance 15, the files sit in the Zyphra organisation, which the card ties to zyphra.com's blog post for the model (10). Safety evaluation 0, no safety results on the card. Agent guidance 0, the card has no limitations or safety section, and nothing on prompt injection, instruction priority or what the model refuses. Licence risk 15, Apache 2.0 has no use policy, threshold or change clause. Security programme 0, no way to report a flaw on the card, and www.zyphra.com has no security.txt. 25 + 15 + 0 + 0 + 15 + 0 = 55.

Score by category

CategoryWeight this runInkling-SmallZAYA1-8BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%255580ZAYA1-8B +25
Risk20%207055Inkling-Small +15
Agent interface10%108560Inkling-Small +25
Documentation and upkeep10%108750Inkling-Small +37
Negative events≤1500
TotalB 67/100C 61/100

Facts side by side

FactInkling-SmallZAYA1-8B
KindOpen-weight modelOpen-weight model
VendorThinking Machines LabZyphra
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-07-312026-07-02
Terms last updatedno document linkedno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviews3.5/5 (4)none

How the scores have moved

Inkling-Small

ZAYA1-8B

No score change since it was listed.

Verdicts

Inkling-Small

A mixture-of-experts generalist with images and audio in, several tool calls a turn and per-request thinking effort. It needs about 205 GB for Thinking Machines' NVFP4 build on recent NVIDIA or AMD datacentre GPUs, and Tinker or DeepInfra host it. The main risks are a use policy that binds on download and can change, and no outside safety results.

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

Inkling-Small

  1. Start the NVFP4 build with SGLang's recipe, sglang serve --trust-remote-code --model-path thinkingmachines/Inkling-Small-NVFP4 --tp 8 --enable-multimodal --reasoning-parser inkling --tool-call-parser inkling, on Blackwell for W4A4
  2. Use the inkling tool and reasoning parsers in vLLM or SGLang, or Thinking Machines' tml-renderers package to render prompts and parse calls yourself
  3. Pass reasoning_effort as none, minimal, low, medium, high (the default) or max, or a number from 0 to 0.99. The repository's template has no xhigh preset and raises an error for it, though Thinking Machines' docs and SGLang's cookbook list xhigh
  4. Effort none conditions the model toward no reasoning but doesn't forbid it, and higher effort needs a larger max_tokens
  5. Tool call arguments must reach the template as an object, not a JSON string, or it raises an error
  6. Images should be 40 to 4096 px a side and audio 16 kHz WAV under two minutes, per the card
  7. Use guided decoding or validate JSON yourself, since structured output isn't documented
  8. Read the Model Acceptable Use Policy before deploying, it binds on download and bars some uses that are legal

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, Inkling-Small or ZAYA1-8B?

Inkling-Small scores 67 (B) on agent readiness against ZAYA1-8B's 61 (C), and leads in 3 of 4 scored categories. ZAYA1-8B leads on reach.

Other comparisons with Inkling-Small 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.