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

MiniMax-M3.1-Flash vs occamy-1.0

occamy-1.0 scores 61 (C) on agent readiness against MiniMax-M3.1-Flash's 50.5 (D), and leads in 3 of 4 scored categories. Both do open-weight models you run yourself.

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

Which one, for what

MiniMax-M3.1-Flash D

Best for Teams with a 4 to 8 GPU server who want an open multimodal agent and coding model with 1M tokens of context and can meet the licence's attribution and notice terms.

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

Watch for

No released vLLM or SGLang ran it on 24 October 2026; only llama.cpp b11861 from that day did

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.

Ahead on

  • Reach, 85 against 40
  • Risk, 55 against 35
  • Documentation and upkeep, 74 against 41

Also in its favour

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

Watch for

No safety results, prompt-injection guidance or security contact

Score by category

CategoryWeight this runMiniMax-M3.1-Flashoccamy-1.0Edge
Capability35%pendingpendingpendingnot scored in this run
Reach25%254085occamy-1.0 +45
Risk20%203555occamy-1.0 +20
Agent interface10%107070even
Documentation and upkeep10%104174occamy-1.0 +33
Negative events≤1500
TotalD 50.5/100C 61/100

Facts side by side

FactMiniMax-M3.1-Flashoccamy-1.0
KindOpen-weight modelOpen-weight model
VendorMiniMaxAccio (Accio-Lab)
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceMiniMax Community License (custom; commercial use needs a "Built with MiniMax M3.1-Flash" line and a one-time notice to MiniMax, and MiniMax's written authorisation above $20M yearly revenue)Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-10-232026-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 reviews2.3/5 (4)3/5 (4)

Verdicts

MiniMax-M3.1-Flash

A 428B mixture-of-experts model, 23B active, for agent work, coding and computer use, with image and video input, about 1M tokens of context and parallel tool calls. It needs a 4 to 8 GPU server for 250 GB of NVFP4 and MXFP8 weights, and vLLM and SGLang support was pre-release on 24 October 2026. Commercial use needs attribution and notice.

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

MiniMax-M3.1-Flash

  1. Check the use case first; commercial products must show "Built with MiniMax M3.1-Flash" and notify MiniMax once, or get written authorisation above $20M yearly revenue
  2. On 8 H100 or H200 GPUs use vLLM's nightly image vllm/vllm-openai:minimax-m31-flash with --tensor-parallel-size 8 --block-size 128 --kv-cache-dtype fp8 --moe-backend marlin --max-model-len 262144
  3. Pass --reasoning-parser minimax_m3 --tool-call-parser minimax_m3 --enable-auto-tool-choice in vLLM, or minimax-m3 for both in SGLang with --trust-remote-code
  4. --block-size 128 is mandatory in vLLM, since MSA's sparse block size is 128
  5. Set effort per request with chat_template_kwargs reasoning_effort (low, medium, high, xhigh, max); sample at temperature 1.0 and top_p 0.95
  6. On Blackwell or MI355X, 4 GPUs serve it with the DSpark draft from dspark/; vLLM's Hopper command leaves DSpark off and turns video input off
  7. For GGUF builds by others, use llama.cpp b11861 or later; earlier builds mis-scale the NVFP4 experts and produce garbage
  8. Without the hardware, call MiniMax-M3.1-Flash on MiniMax's API (minimax-api), whose thinking defaults to max effort

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, MiniMax-M3.1-Flash or occamy-1.0?

occamy-1.0 scores 61 (C) on agent readiness against MiniMax-M3.1-Flash's 50.5 (D), and leads in 3 of 4 scored categories.

Other comparisons with MiniMax-M3.1-Flash 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.