Early-bird pricing (ends Dec 25), locked in while you stay subscribed: Go $10/mo (normally $20), Plus with Opus 5.5 just $30/mo (normally $50)Subscribe →
Text chat1M context

MiniMax M3

Use MiniMax M3 for long-context document review, agent memory inspection, knowledge workflows, and production text automation.

Price / 1M tokensSave 70%
OfficialAIReiter
Input$1.20$0.36
Output$4.80$1.44
Cache read$0.24$0.072
Readme
Input
Caps the reply length. Reasoning models count their thinking toward it too.
minimax-m3
Output

A codebase you don't know is a risk, not a hurdle. The plan should burn down that risk in order: understand, run, trace, spike, then make the change small enough that "production-ready" is a property you can demonstrate, not a hope.

Here are the first five steps, with the evidence you collect at each.

Step 1 — Get it building and the baseline green (half day)
Read the README, the manifest(s), the CI config, and any architecture docs. Boot the app locally, run the full test suite, run the linter/typechecker.
Evidence: The exact commands that reproduce a clean build and a passing test suite from a fresh checkout (recorded output, not memory of it). A one-page map you wrote yourself: where the entry points are, the layers, the build/test toolchain, and the main risks to your feature (e.g. "this touches cron jobs and payments").

Step 2 — Trace the smallest end-to-end slice that resembles your feature (half day)
Don't start with your feature. Pick a neighboring one that already works and follow it from entry to persistence. Note the conventions along the way: how errors surface, how config is injected, how logging is done, how tests are written.
Evidence: An annotated trace — file → function → what it does — for that slice. A written list of "conventions I must follow" (not intuitions; things you observed in real code). A named shortlist of the 3–5 files you will actually touch. If you can't produce this trace, you're not ready to write code.

Step 3 — Spike the core path (day 2)
Build the ugly version: hardcoded values, no error handling, no tests. The purpose is to confirm the path you traced in step 2 is real and to surface what you didn't know you didn't know.
Evidence: A working spike demonstrating the feature's central data path, alongside a list of every assumption the spike broke and what you corrected. That correction list is the most valuable document in this whole plan.

Step 4 — Write the contract before the code (half of day 2 / day 3)
Once the spike proves the path, pin down what production needs: the inputs/outputs, the error cases, where it sits in the conventions from step 2. Then write the tests — they'll be red, but they're the specification.
Evidence: A one-to-two-page design doc, an agreed interface/API shape (with the team if there is one), and a red test suite that encodes intended behavior. If you can't write the contract without consulting the code, you haven't finished step 2.

Step 5 — Implement in small, verified increments (days 3–4)
Replace the spike with the real thing in small commits, each one keeping the suite green, leaning on the existing patterns. Run lint/tests/typecheck per commit — CI, not just locally — and exercise the actual path against a real instance (staging or a local environment that isn't stubbed).
Evidence: A branch with progressive commits, each green in CI; coverage on the new code; something that proves it works against reality (a test result, a log trace, a screenshot); and a review by at least one person who knows the codebase. The review counts as evidence — an unfamiliar codebase has tribal knowledge you cannot extract from the files alone.

Steps 6+ would be the things that actually make it "shipped": a migration plan and its rollback, feature flagging, observability, the release and post-release verification. But the first five get you to a reviewed, green, working slice in staging — which is the point at which you can say "this will work in production" with evidence behind it, instead of a guess.

Generated in42.7s
Input tokens134
Output tokens2,354
Tokens / sec55.13
TTFT-

Runs in this page. Sign-in and credits are required.

Model details

Use the same model key in Playground, API requests, and internal workflows.

Model ID
minimax-m3
Provider
Minimax
Protocol
Anthropic Messages
Context window
1,000,000 tokens
Max output
131,072 tokens
Input tokens
36 credits / 1M tokens
Output tokens
144 credits / 1M tokens
Cache read
7.2 credits / 1M tokens
Cache write
-

A long-context route for documents and agent memory

MiniMax M3 is useful when a workflow must keep more evidence in one request: policy sets, research packs, meeting history, or long agent memory.

MiniMax M3 API cover

Should you choose MiniMax M3?

Position it as a practical long-context model for document-heavy teams and agent workflows that need continuity.

Choose it when

You need long document review, memory inspection, knowledge-base synthesis, or a cheaper long-context route before escalating to a flagship model.

Use another model when

The task is a small chat turn, simple extraction, or high-risk code reasoning that needs a more specialized coding model.

Public API protocol

Call POST https://aireiter.com/api/v1/messages with model "minimax-m3". Streaming is supported through the same Messages-compatible endpoint.

Token and cache usage

Pricing is based on input, cache-read, and output usage. For long prompts, cache-read fields matter because reused context can materially change cost.

MiniMax M3 production workloads

Best for long inputs where continuity and summarization quality matter.

Document packs

Review policies, reports, transcripts, and research notes while keeping cross-document references visible.

Agent memory

Inspect long histories, tool calls, and state updates to explain why an agent made a decision.

Knowledge workflows

Turn long internal material into summaries, briefs, requirements, and action lists.

Cost-aware long context

Evaluate whether a practical long-context model is enough before using a higher-cost flagship route.

How MiniMax M3 fits your model stack

Manage API keys →

Do not route every request to the newest model. Pick the cheapest model that still passes your quality bar, then reserve deeper models for failures or high-risk tasks.

01For fast batches

Use Doubao or DeepSeek V4 Flash for small fast tasks; MiniMax M3 is for context-heavy inputs.

02For deeper reasoning

Use GLM 5.2 or DeepSeek V4 Pro when reasoning depth is more important than context size.

03For long context

Compare MiniMax M3 with Kimi K2.7 Code when the workload mixes documents, code, and agent traces.

04For production rollout

Track cache-read usage on repeated long prefixes; this is where long-context workflows can become more economical.

FAQ

01What model ID should I send for MiniMax M3?

Use "minimax-m3" in the API request body. The internal DB key is only used by AIReiter routing.

02Which endpoint should MiniMax M3 use?

Use POST https://aireiter.com/api/v1/messages for public API calls. Keep x-api-key / Authorization authentication consistent with your AIReiter API key setup.

03Does MiniMax M3 support streaming?

Yes. Send stream=true and read server-sent events until the message completes. Test non-streaming first when debugging authentication or model ID issues.

04How do I confirm token and cache billing for MiniMax M3?

Check the usage object returned by the API. Input, output, and cache-read token fields are the source of truth for settlement; a repeated prompt alone does not prove a cache hit.

05Should I always set max_tokens for MiniMax M3?

Set max_tokens according to the expected summary length. Long input does not always require huge output, but review tasks need enough room for findings and evidence.