Last verified
LONG-CONTEXT REASONING1M CONTEXTTEXT ONLYOPEN-WEIGHTNOT ON MINIMAX'S LIST

MiniMax M1 API Pricing

Not on MiniMax's model list: MiniMax's documentation lists MiniMax M1 neither as available nor as retired, and MiniMax never published this price — the figures below come from an OpenRouter resale listing and are kept for reference only. MiniMax M1 is the legacy long-context reasoning model surfaced through OpenRouter. The live OpenRouter model page lists $0.40/M input and $2.20/M output, with no separate cache-read price. Checked by hand against openrouter.ai.

Input - per 1M tokens
$0.40/M
Source openrouter.ai verified
Output - per 1M tokens
$2.20/M
Source openrouter.ai verified
Cached input
Not published
Cache no public row not listed
Effective - agentic blend
$0.544/M
92/8 split - no cache
§ 01 / TERMINAL

MiniMax M1 API cost calculator.

Live calculator pre-loaded with current MiniMax M1 rates. Tweak workload split, then share the URL to share the calculation.

$ /mo
Workload split
Tokens you can process
—
Words equivalent (English)
—
Effective rate
—
Open full calculator (all models · share URL · CSV) →
§ 02 / SCENARIOS

MiniMax M1 cost on real workloads.

§ 03 / TOKENIZER

MiniMax M1 token counter and cost.

What's a token →
Calibrated · measured on the vendor's tokenizer · 2026-06-10 Auto-counts as you type

Counts use a chars-per-token calibration measured on the vendor's own published tokenizer (MiniMaxAI/MiniMax-M2.1, 2026-06-10). English prose is typically within a few percent; code and non-Latin scripts tokenize heavier. For billing-exact counts use the vendor's count-tokens API.

Characters 374
Words 63
Tokens (estimated) 70 tokens
Cost as input · uncached $0.00003 USD
Cost as output · uncached $0.00015 USD
§ 04 / SHELF

MiniMax M1 vs similar models.

All models →
Model Input /M Output /M Effective blended Context Best for
MiniMax M1 Current $0.40 $2.20 $0.544 agentic 92/8 1M Legacy 1M reasoning workloads
MiniMax-01 $0.20 $1.10 $0.272 deprecated · −2.0× 1M Cheaper 1M-context MiniMax tasks
MiniMax M2.7 $0.30 cache $0.06 $1.20 $0.191 deprecated · −2.8× 205K MiniMax agent loops until November 18, 2026
MiniMax M2.5 $0.30 cache $0.03 $1.20 $0.168 deprecated · −3.2× 205K Lower-cost MiniMax agent loops
GPT-6.1 Terra $1.00 cache $0.05 $5.00 $0.645 +19% 1.05M OpenAI's fast, efficient GPT-6 tier
DeepSeek V4 Pro $1.32 cache $0.044 $3.96 $0.569 +5% 1M Low-cost reasoning workloads

MiniMax M1 API pricing FAQ.

Practical MiniMax M1 pricing questions, with source prices separated from workload assumptions.

Q · 01 Is MiniMax M1 still sold by MiniMax? +
Not as a listed product. As of October 28, 2026, MiniMax's model list names MiniMax M3.1 Flash and MiniMax M3 as its current text models and gives a separate table of retired ones, and MiniMax M1 is in neither. MiniMax's own pricing pages do not price it, so the rate on this page is an OpenRouter resale listing rather than a vendor price — check with whoever serves the model before relying on it.
Q · 02 What is the MiniMax M1 API price? +
OpenRouter lists MiniMax M1 at $0.40/M input and $2.20/M output. The page does not publish a separate cached-input tier, so this calculator treats cached input as unavailable.
Q · 03 Is MiniMax M1 on MiniMax's current pay-as-you-go docs? +
No. The current MiniMax first-party PAYG page focuses on M2-family rows. This archive page uses the live OpenRouter model page because the queue marks M1 as surfaced via OpenRouter.
Q · 04 What context window does it support? +
The live OpenRouter page lists a 1M context window for minimax/minimax-m1. That is the main reason to keep an archive pricing page for it.
Q · 05 Does prompt caching change the effective cost? +
No public cache price is listed for this OpenRouter row. The effective tile therefore uses the normal $0.40/M input price for all input tokens in the 92/8 blend.
Q · 06 When was this checked? +
The OpenRouter model page was opened and checked on May 23, 2026. The snapshot row was refreshed to the exact model URL used for this page.
Q · 07 How accurate is the tokenizer estimate? +
The browser widget uses a minimax-tokenizer-estimate planning ratio for English text. Final billing depends on the provider-side tokenizer and can differ for code, Chinese, and mixed-language prompts.