Topic starter
06/06/2026 11:28 am
TL;DR: MiniMax M2.5 is now the most-used model on OpenRouter by token volume, processing over 2.45 trillion tokens in a week as of February 2026, while Chinese AI models reached 61% market share and the model delivered near frontier performance at far lower cost, according to WorkOS. The governance issue is no longer model quality alone but routing, escalation, and control boundaries across AI agent workloads.
Editorial analysis by NHI Mgmt Group, based on content published by WorkOS: “Why MiniMax M2.5 is the most popular model on OpenRouter right now”.
By the numbers:
- MiniMax M2.5 is the number one most-used model on OpenRouter by token volume, with over 2.45 trillion tokens processed in a single week as of February 2026.
- M2.5 scores 80.2% on SWE-Bench Verified, compared with 80.8% for Claude Opus 4.6.
- MiniMax says M2.5 completes SWE-Bench tasks 37% faster than its predecessor, M2.1.
Key questions
Q: How should security teams govern model routing in AI agent workflows?
A: Security teams should treat model routing as a policy decision, not a performance shortcut.
Q: Why does using a cheaper model still require governance controls?
A: A cheaper model still makes a governance decision whenever it handles user data, calls tools, or triggers downstream actions.
Q: What breaks when AI systems route every task through one default model?
A: One-default-model designs break when task complexity, sensitivity, and reasoning depth are not uniform.
Practitioner guidance
- Define model routing policies Classify AI workloads by task type, required reasoning depth, latency tolerance, and cost sensitivity so routing choices are explicit and repeatable.
- Set escalation thresholds for complex tasks Reserve specialist models for multi-step reasoning, subtle debugging, and high-impact decisions, and document the conditions that trigger escalation.
- Inventory open-weight deployment paths Map where open-weight models are downloaded, hosted, fine-tuned, and accessed so the internal control surface is visible to security and platform teams.
Bottom line: AI governance is moving from model selection to model routing, because task-by-task escalation now matters more than picking one default system.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/06/2026 12:18 pm
Model routing is now an identity governance problem, not just an optimisation problem. Once AI workloads can be split across general and specialist models, the routing layer becomes the place where trust, cost, and escalation are decided. That decision point deserves the same governance attention as an access policy, because it determines which system is allowed to act first and which system is allowed to override it. Practitioners should treat routing as part of the control plane for AI work.
A question worth separating out:
Q: What should security teams monitor in self-hosted open-weight model deployments?
A: Security teams should monitor where the model is hosted, who can access it, how it is updated, and whether routing rules are being changed without review. Self-hosting removes vendor dependency, but it increases responsibility for availability, change control, and lifecycle governance across the model estate.
👉 Read our full editorial: MiniMax M2.5 shows why model routing now drives AI governance