MiniMax Model | API Docs

MiniMax M3 is available through the Common Chat Completions endpoint, with both non-streaming and SSE streaming text responses.

text

POST https://api.requestbeam.com/v1/chat-completions

Available Model

`model` value	Type	Non-streaming	SSE streaming
`minimax-m3`	Text chat	Yes	Yes

Authentication

http

Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

Non-streaming Request

json

{
  "model": "minimax-m3",
  "messages": [
    {
      "role": "system",
      "content": "You are a code review assistant."
    },
    {
      "role": "user",
      "content": "List five risk areas to review in a payment webhook implementation."
    }
  ],
  "thinking": {
    "type": "disabled"
  },
  "stream": false
}

Streaming Request

json

{
  "model": "minimax-m3",
  "messages": [
    {
      "role": "user",
      "content": "Analyze a duplicate queue-consumption issue step by step."
    }
  ],
  "stream": true
}

This endpoint returns one complete JSON response by default. Set stream: true explicitly when you need SSE streaming.

Request Fields

modelstringrequired

Use minimax-m3.

messagesobject[]required

OpenAI Chat Completions style messages. Each message contains role and content.

streambooleanDefault: false

true returns SSE; false returns one complete JSON response.

max_tokensinteger

Optional maximum output tokens, as a positive integer. Omit this field to use the upstream default for the selected model. Depending on the model, the budget may include reasoning tokens as well as final text. A small budget can truncate the answer or be exhausted before final text; increasing it may increase cost.

max_completion_tokensinteger

Optional compatibility alternative to max_tokens, with the same budget considerations. The selected model determines support; omit both fields to use the upstream default.

thinkingobject

MiniMax thinking control. Use { "type": "disabled" } for short, direct answers that do not need hidden reasoning. Omit the field to keep the model's default thinking behavior.

See Common Chat Completions for shared fields such as temperature, top_p, frequency_penalty, presence_penalty, stop, and n. minimax-m3 accepts these standard fields, but not every parameter necessarily produces a measurable semantic change.

Success Response

json

{
  "id": "chatcmpl_...",
  "object": "chat.completion",
  "created": 1787200000,
  "model": "minimax-m3",
  "choices": [
    {
      "index": 0,
      "message": {
        "role": "assistant",
        "content": "Start by checking idempotency keys, acknowledgements, and retry policy..."
      },
      "finish_reason": "stop"
    }
  ],
  "usage": {
    "prompt_tokens": 29,
    "completion_tokens": 104,
    "total_tokens": 133
  }
}

usage may include optional cached-input or reasoning-token details. Continue to base accounting and telemetry on the standard input, output, and total token fields.

Usage Notes

The current public contract is Chat Completions, including non-streaming and SSE streaming.
minimax-m3 is not currently published as an OpenAI Responses or Claude Messages model.
Use minimax-m3 exactly.
Use GET https://api.requestbeam.com/v1/models for the models visible to the current API Key, and use the console for current pricing.