MiniMax m2.5

MiniMax-M2.5

Use the MiniMax M2.5 API for chat, coding, and reasoning. Send messages to get text responses, explanations, or proposed code changes. Use it to work through multi-step coding tasks or review longer technical material. Compare the available provider routes, request examples, and usage prices on OpenAny.

Published price
From $0.290 / 1M tokens
Billing unit
/ 1M tokens
Context / Max output
200K / 128K
Listed routes
1

Provider

Published price $0.290 / 1M tokens

Request parameters

POST /v1/chat/completions
Other parameters (13)

Result preview

MiniMax · 1414ms

Response example. Run to see the actual response.

{
  "id": "0c4780e1-9046-4b2b-8b38-0e8c590dc844",
  "model": "MiniMax-M2.5",
  "usage": {
    "total_tokens": 79,
    "prompt_tokens": 42,
    "completion_tokens": 37,
    "prompt_tokens_details": {
      "cached_tokens": 0
    },
    "completion_tokens_details": {
      "reasoning_tokens": 28
    }
  },
  "object": "chat.completion",
  "choices": [
    {
      "index": 0,
      "message": {
        "role": "assistant",
        "content": "Hello! How can I help you today?",
        "reasoning_content": "The user has simply said \"hello\" - this is a greeting. I should respond in a friendly and welcoming manner."
      },
      "finish_reason": "stop"
    }
  ],
  "created": 1784615368,
  "openmodels_cost": 50
}

Model API questions

How do I call MiniMax m2.5 through OpenAny?

Use model ID MiniMax-M2.5 with an OpenAny key and the operation published in this model's API tab. The model API base is https://api.openany.si/v1. Confirm the protocol and request schema; model availability does not imply every OpenAI API operation is supported.

How is MiniMax m2.5 billed?

Compare the published rate and billing unit of the selected provider route. Input, output and cache token rates may differ. Image, audio and video models can use other units. Recorded usage determines the charge under that route's billing contract.

Are Community and Verified routes the same as an official publisher API?

No. Inspect the provider name and supply classification for the specific route. A marketplace listing or a supply label is not a claim of publisher endorsement, identical service or measured uptime. Different route prices may reflect different supply and conditions.

Where do these prices come from, and when were they updated?

Rates come from the provider routes in OpenAny's public model catalog, not an independent quote from the model publisher. The catalog does not supply a price update timestamp. A page or catalog snapshot date is not a price revision date. Compare supply, billing units, tiers and conditions; a lower listed rate alone does not establish equivalent service or explain the price difference.

Use MiniMax m2.5 with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.