Workload
Long textual processing
The capacity profile is designed around extended inputs.
MiniMax M2 model, 1M context profile, and long-text capabilities.
The `minimax-m2` protocol and 1M economic profile are configured below the main picker. Video and image integrations use separate workflow paths.
Floatboat · MiniMax
Configured below the picker
MiniMax
What do you want to finish?
Process a long low-cost workload
Not exposed in the main client picker
- Model ID
- minimax-m2
- Capacity
- 1M profile
- Positioning
- Low-cost long workloads
- Availability
- Not in main picker
MiniMax M2 model overview
Prepared around the economics of long-running text work.
MiniMax M2 is differentiated by its configured 1M low-cost profile. Media integrations remain separate workflow paths.
Economics
Low-cost profile
The configured role emphasizes economical processing.
Media boundary
Separate workflows
Image and video integrations are not represented as chat-picker features.
Availability
Prepared below picker
There is no current public picker entry.
Configured model
One exact model ID with a 1M profile.
The configured state does not imply main-picker availability.
minimax-m2
1M low-cost capacity profile.
Not in the main picker
Intended workload
The configured value is sustained processing at a lower cost profile.
These tasks match the configured capacity role. MiniMax M2 is not currently available through the main client picker.
Long text queue
Task input
Process extended textual material where economy matters.
Processing focus
The 1M low-cost profile defines the intended runtime role.
Expected result: A prepared route for sustained textual workloads.
Cost-aware planning
Task input
Evaluate which future workloads warrant an economical long-context option.
Processing focus
Compare the configured context budget with the task requirements, and confirm a supported model-access path.
Expected result: A realistic capacity plan.
Media workflow separation
Task input
Avoid confusing text capacity with image or video integrations.
Processing focus
Use the dedicated image or video workflow for media deliverables; MiniMax M2’s configured role is text processing.
Expected result: A clearer product path for each deliverable.
Configured foundation
A focused economic profile below the picker.
The configured model ID is `minimax-m2`. Text processing and media workflows have separate access requirements.
Exact M2 identity
The configured model ID is `minimax-m2`.
1M profile
The runtime matrix registers a 1M capacity profile.
Low-cost positioning
Its recorded role emphasizes economical long workloads.
Separate media paths
Video and image integrations are carried by other workflows.
Evaluate MiniMax M2 for long-text work and cost requirements.
Useful for evaluating
- Future workloads combine long input and cost sensitivity.
- You need the exact configured MiniMax ID.
- You are separating text capacity from media workflows.
Use another product path when
- You need a model that is selectable in the client now.
- The deliverable is an image or video.
- You need confirmed public availability rather than configured capacity.
Explore Other Model Families
Compare model families by the kind of work they support. Availability differs by model and entry point.
MiniMax · FAQ
What is MiniMax M2?+
MiniMax M2 is a model profile positioned for economical processing of long textual workloads.
What is the MiniMax M2 model ID?+
The exact configured model ID is `minimax-m2`.
How large is the MiniMax M2 context profile?+
The registered economic profile carries a 1M capacity budget.
What is MiniMax M2 best suited for?+
Its confirmed role is long, cost-sensitive textual processing rather than image or video generation.
What is the current MiniMax M2 support status?+
Its protocol and 1M economic profile are configured, but it is not currently exposed in the main picker.
Need an efficient route while MiniMax M2 stays configured
MiniMax M2 has a cost-oriented profile below the picker, not a public selection. Compare live models for high-volume text work.