Question 1

How is MiniMax served?

Accepted Answer

Through Ollama Cloud. MiniMax is one of a curated set of hosted open-weight models we enable, so you do not provision hardware for it and requests go to Ollama. The Ollama page carries the current roster across both hosted and local.

Question 2

Can I self-host MiniMax instead?

Accepted Answer

Where the model is available to pull, yes. Self-hosted Ollama runs on hardware you control and is open-ended: any model Ollama can serve will work, which is the path for teams whose data cannot leave their own network.

Question 3

Why choose an open-weight model over a frontier one?

Accepted Answer

Cost at volume, and control. Open-weight models price differently from frontier APIs, which matters when query volume is high, and the option to move the same model onto your own hardware later keeps you from being locked to one vendor.

Question 4

Where does MiniMax fit?

Accepted Answer

The many small calls. Classifying exceptions, extracting fields from carrier documents, and drafting routine notices run well on MiniMax at low cost, with a frontier model kept for the few hard cases.

Question 5

Which other models can I run alongside MiniMax?

Accepted Answer

Any of them, and more than one at a time. CommerceShip runs ChatGPT, Claude, Gemini, Mistral, and Muse as frontier models, and DeepSeek, Gemma, GLM, Kimi, Llama, MiniMax, Nemotron, and Qwen as open-weight models, served through Ollama Cloud or on your own hardware. Route routine work to one model and heavier analysis to another, and if a provider is rate-limited or down, the run moves to a fallback and completes.

Question 6

What access does CommerceShip need to MiniMax?

Accepted Answer

The connection uses scoped credentials limited to the record types the integration works with, and you choose which fields are included. Credentials are encrypted at rest and stored separately from your operational data. Revoke the connection from either side at any time and the access ends with it.

Question 7

How is my data protected?

Accepted Answer

TLS in transit and AES-256 at rest, with tenant isolation enforced by row-level security in the database. Role-based permissions control who on your team can see cost data or change carrier settings, and automated actions are written to an audit log. CommerceShip is pursuing SOC 2 Type II certification. The security page carries the full detail.

Run supply chain AI on MiniMax

MiniMax Integration Capabilities

How the MiniMax integration works

Choose MiniMax

Assign MiniMax to the work

Ask and act

MiniMax Integration FAQs

Use MiniMax with no hardware to set up

Other Models