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

Inkling vs Mistral Large 4

Inkling scores 64.2 (B) on agent readiness against Mistral Large 4's 54.6 (C), and leads in 2 of 5 scored categories. Mistral Large 4 leads on risk and agent interface. Both do open-weight models you run yourself.

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

Which one, for what

Inkling B

Best for Agents calling a hosted open multimodal model with audio input, or teams with a multi-GPU datacentre node who want to run it themselves.

Ahead on

  • Capability, 60 against 32
  • Documentation and upkeep, 82 against 64

Watch for

The smallest build Thinking Machines publishes needs about 710 GB, beyond any single workstation

Mistral Large 4 C

Best for Operators with an 8-GPU Blackwell or H200 node who want a frontier-sized open model for coding agents and defensive security, with a hosted twin on Mistral's API.

Ahead on

  • Risk, 75 against 70
  • Agent interface, 95 against 85

Watch for

The smallest 4-bit build needs about 732 GB, so nothing fits a single workstation or a 128 GB machine

Score by category

CategoryWeight this runInklingMistral Large 4Edge
Capability35%356032Inkling +28
Reach25%255050even
Risk20%207075Mistral Large 4 +5
Agent interface10%108595Mistral Large 4 +10
Documentation and upkeep10%108264Inkling +18
Negative events≤1500
TotalB 64.2/100C 54.6/100

Facts side by side

FactInklingMistral Large 4
KindOpen-weight modelOpen-weight model
VendorThinking Machines LabMistral AI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Mistral Ecosystem Open-Weight License (modified MIT)
Read-only variant documentednono
llms.txtnono
Last release2026-07-232026-10-29
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/5 (4)none

Verdicts

Inkling

Thinking Machines' large multimodal generalist, stronger than Inkling-Small on factual recall by its own numbers. It needs about 710 GB of datacentre GPU memory even in NVFP4, so most agents will use a host such as Together AI or Tinker. The main risks are a use policy that binds on download and can change, and no outside safety results.

Mistral Large 4

A frontier-sized open cousin for coding agents and defensive security, with strict JSON Schema output, parallel tool calls and three reasoning efforts. It needs a multi-GPU server, about 732 GB for the smallest 4-bit build, and vLLM and SGLang run it only from special images. The main risk is a licence that bars Model-as-a-Service businesses without a separate deal.

Before you call either

Inkling

  1. Unless you have a multi-GPU Blackwell or H200 node, call it through Together AI, Fireworks, DeepInfra or Tinker rather than starting it
  2. On 8 B200 GPUs, SGLang's recipe is sglang serve --trust-remote-code --model-path thinkingmachines/Inkling-NVFP4 --tp 8 --quantization modelopt_fp4 --enable-multimodal --reasoning-parser inkling --tool-call-parser inkling
  3. Use the inkling tool parser, not Hermes, and the inkling reasoning parser
  4. 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 list xhigh
  5. Tool call arguments must reach the template as an object, not a JSON string, or it raises an error
  6. Audio should be 16 kHz WAV, ideally under 20 minutes, and images 40 to 4096 px a side, per the card
  7. Read the Model Acceptable Use Policy before deploying, it binds on download and bars some uses that are legal

Mistral Large 4

  1. Serve the NVFP4 build on Blackwell with vllm/vllm-openai:mistral-large-4 --model mistralai/Mistral-Large-4-1T-A52B-NVFP4 --tensor-parallel-size 8 --kv-cache-dtype fp8_ds_mla --tool-call-parser mistral --reasoning-parser mistral --enable-auto-tool-choice; released vLLM doesn't load it
  2. On H200 use the FP8 build with tensor parallelism of 16 or 8 by 2 pipelines, per vLLM's recipe
  3. Pass reasoning_effort low, medium or high (default high); any other value makes the template raise an error, and there is no off switch
  4. Read the reasoning from message.reasoning; max_completion_tokens counts reasoning tokens too
  5. Use temperature 1.0 and top_p 0.95 at every effort, per the card
  6. Ask for JSON with response_format type json_schema and strict true; the template passes the schema to the model
  7. The template rejects a tool message straight after a user message and a conversation that doesn't start with a user or system message
  8. Add --speculative-config '{"method": "dspark", "num_speculative_tokens": 3}' to use the embedded draft head
  9. If you'll offer it to others as a hosted model, read the licence first; Model-as-a-Service use needs Mistral's commercial licence

Questions

Which is better for AI agents, Inkling or Mistral Large 4?

Inkling scores 64.2 (B) on agent readiness against Mistral Large 4's 54.6 (C), and leads in 2 of 5 scored categories. Mistral Large 4 leads on risk and agent interface.

Other comparisons with Inkling or Mistral Large 4

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.