MiniMax: MiniMax M2.7

Models

Model details

Model
minimax/minimax-m2.7
Provider
openrouter
API
openai-completions
Base URL
https://openrouter.ai/api/v1
Input
text
Reasoning
Yes
Context window
196,608
Max tokens
176,947
Show configuration
{
  "providers": {
    "openrouter": {
      "apiKey": "YOUR_API_KEY",
      "models": [
        {
          "id": "minimax/minimax-m2.7",
          "name": "MiniMax: MiniMax M2.7",
          "reasoning": true,
          "input": [
            "text"
          ],
          "thinkingLevelMap": {
            "off": null
          },
          "contextWindow": 196608,
          "maxTokens": 176947,
          "cost": {
            "input": 0.21,
            "output": 0.84,
            "cacheRead": 0.042,
            "cacheWrite": 0
          },
          "compat": {
            "supportsDeveloperRole": false,
            "thinkingFormat": "openrouter",
            "supportsStrictMode": true,
            "sendSessionAffinityHeaders": true
          }
        }
      ],
      "api": "openai-completions",
      "baseUrl": "https://openrouter.ai/api/v1"
    }
  }
}

Pricing

USD per million tokens. A tier is selected from the total input tokens in each request and applies to that entire request.

Pricing rates for MiniMax: MiniMax M2.7
Request inputInputOutputCache readCache write
All requests$0.21$0.84$0.042$0

Session cost calculator

Estimate the requests made during an agent session. A user turn can make several model calls while using tools, so costs are calculated per model request.

Session shape
Rounded median shapes from recent Pi agent sessions.
Warm-request cache reuse
Effective token reuse combines partial hits and occasional complete misses.
Estimated session$0.00
Uncached input
—
Cache reads
—
Uncached prefixes
—
Cache writes
—
Output
—
Without caching
—

The first request starts cold unless marked otherwise. Output is billed separately from context growth because reasoning tokens are not always retained. This remains a directional estimate: providers differ in eligibility, rounding, and retention.

Compatibility flags

Effective values after applying Pi's API defaults and model overrides.

Effective compatibility flags for MiniMax: MiniMax M2.7
FeatureValue
supportsStoreYes
supportsDeveloperRoleNo
supportsReasoningEffortYes
supportsUsageInStreamingYes
maxTokensFieldmax_completion_tokens
requiresToolResultNameNo
requiresAssistantAfterToolResultNo
requiresThinkingAsTextNo
requiresReasoningContentOnAssistantMessagesNo
thinkingFormatopenrouter
openRouterRoutingEmpty
vercelGatewayRoutingEmpty
chatTemplateKwargsEmpty
zaiToolStreamNo
supportsStrictModeYes
cacheControlFormatNone
sendSessionAffinityHeadersYes
supportsLongCacheRetentionYes