MiniMax API

Two MiniMax text models on the standard Text API passthrough. Do not confuse them with the MiniMax H3 video models, which use the Video API. Every model here answers on all four request formats the Text API supports.

OpenAI Chat Completions

POST https://api.beatapi.io/v1/chat/completions

1
import OpenAI from "openai";
2
3
const client = new OpenAI({
4
  apiKey: process.env.BEATAPI_API_KEY,
5
  baseURL: "https://api.beatapi.io/v1"
6
});
7
8
const completion = await client.chat.completions.create({
9
  model: "MiniMax-M3",
10
  max_tokens: 2000,
11
  messages: [
12
    { role: "user", content: "Given this changelog, draft release notes grouped by user-visible impact." }
13
  ]
14
});
15
16
console.log(completion.choices[0].message.content);

$
curl --request POST \
>
  --url https://api.beatapi.io/v1/chat/completions \
>
  --header 'Authorization: Bearer <BEATAPI_API_KEY>' \
>
  --header 'Content-Type: application/json' \
>
  --data '{
>
  "model": "MiniMax-M3",
>
  "messages": [
>
    {
>
      "role": "user",
>
      "content": "Given this changelog, draft release notes grouped by user-visible impact."
>
    }
>
  ]
>
}'

Long context pricing

MiniMax-M3 switches to a higher rate once the prompt passes 512,000 tokens, and the higher rate then applies to the whole request — input, cached input and output all double. It is a step, not a gradual increase: a request one token over the threshold bills entirely at the higher rate.

Model names are case-sensitive here: send MiniMax-M3, not minimax-m3.

Other SDK formats

The same models answer on /v1/responses, /v1/messages and the Gemini-compatible endpoint. The request and response shapes are identical for every text model, so they are documented once on the Text API page rather than repeated here.

Authentication and availability

One BeatAPI key reaches every model on this page — there is no per-vendor key, no per-vendor base URL, and no separate signup. Send Authorization: Bearer <BEATAPI_API_KEY> against https://api.beatapi.io.