Skip to content

MiniMax M2.7 High Speed

MiniMax M2.7 High Speed is the throughput-optimized variant of M2.7. It supports a context window of 204.8K tokens and a max output of 131.1K tokens.

ReasoningTool UseImplicit CachingVision (Image)fille-input
index.ts
import { streamText } from 'ai'


const result = streamText({
  model: 'minimax/minimax-m2.7-highspeed',
  prompt: 'Why is the sky blue?'
})
OverviewPlaygroundAboutProvidersThroughputLatencyUptimeStatusSimilarFAQ

Frequently Asked Questions

  • What fundamentally changed between the 2.5 and 2.7 generations?

    Three capabilities that didn't exist in M2.5: native multi-agent coordination (no external orchestration code), dynamic tool search (tools found at runtime rather than declared upfront), and enterprise office automation (document analysis, structured data, reporting).

  • How does runtime tool discovery work?

    Instead of receiving a fixed tool manifest in the prompt, MiniMax M2.7 High Speed evaluates the evolving task state and identifies relevant tools. It invokes them without prior declaration, expanding the model's effective action space over long sessions.

  • Does switching from the previous highspeed variant require code changes?

    Only the model identifier string. Update to minimax/minimax-m2.7-highspeed in your API calls. The tool-calling format, API surface, and AI Gateway configuration stay the same.

  • Can MiniMax M2.7 High Speed coordinate agents built on different model families?

    Yes. The orchestration logic is native to the M2.7 architecture, but the agents it coordinates can run any model. Coordination fidelity is strongest when MiniMax M2.7 High Speed serves as the orchestrating agent.

  • Is throughput the same as the prior highspeed generation?

    Both target comparable throughput (see live metrics on this page). The improvement is capability breadth per token, not token velocity.

  • When does the standard-rate M2.7 make more sense?

    When nobody is waiting on the output. Background batch processing, scheduled overnight jobs, and any pipeline where wall-clock duration doesn't affect user experience or business outcomes.