MiniMax M3.1 Flash

minimax/minimax-m3.1-flash

MiniMax M3.1 Flash is listed with a 1,048,576-token window and text, image and video input. The publisher describes an open-weight mixture-of-experts model built around agentic work, coding and cybersecurity.

Input · Account credit
$0.15

per 1M tokens

Cash equivalent $0.015

Output · Account credit
$0.60

per 1M tokens

Cash equivalent $0.06

Context window
1,048,576

tokens · OpenRouter

Input → Output
Text · Image · Video→ Text
Model specifications
Sources reviewed: Y-API catalog snapshot:

Choosing this model

Selection advice by Y-API. The checks below are suggested evaluations, not published test results.

Where to start

Start with visual-to-code work — a screenshot of a dashboard or a slide plus a written spec — where you can compare the rendered result against the input, rather than on open-ended chat.

What to watch for

Video input and the million-token window are model specifications, not proof that a given gateway forwards video or accepts a maximal request. The catalog also lists a `-preview` string for this generation at a different price, so pin the exact ID your client sends.

Model specifications

These are OpenRouter model-level specifications, not a Y-API compatibility test. A particular route may accept fewer input formats, parameters or tokens. Verify the features you need with a small request; a successful text response does not validate vision or tool calling.

Context window
1,048,576 tokens
Input
Text · Image · Video
Output
Text
Listed on OpenRouter
Parameters listed by OpenRouter
frequency_penaltyinclude_reasoninglogit_biaslogprobsmax_tokensmin_ppresence_penaltyreasoningreasoning_effortrepetition_penaltyresponse_formatseedstopstructured_outputstemperaturetool_choicetoolstop_ktop_logprobstop_p
OpenRouter model page & specifications

API pricing & cost estimate

Estimated credit consumed
$0.45
Estimated cash equivalent
$0.045

Illustrative token budget, not measured usage or a quote. Includes input and output; excludes separate media charges, cache discounts and retries. Include billed reasoning tokens in your output budget where applicable. Actual billing follows usage returned by the service.

$1 paid adds $10 of credit. Cash equivalent = credit consumed ÷ 10; this is not the model publisher’s list price.

Same token budget, different models
ModelEstimated credit consumedEstimated cash equivalent
MiniMax M3.1 Flash$0.45$0.045
MiniMax M3.1 Flash Preview$0.90$0.09
MiniMax M3$0.90$0.09
View LLM API pricing & billing

API integration examples

These minimal, text-only requests use the exact Y-API model ID. They do not demonstrate image, audio, video, file or tool support. The output limit also needs room for reasoning; an empty answer with finish_reason=length can mean the budget was exhausted.

A task to try

Here is a screenshot of a settings page and the JSON schema behind it. Build the form component with the same labels and spacing, and list any control in the screenshot that the schema cannot represent.

Set the TOKEN environment variable to a key from your console. Run this on your server or locally; never expose a key in browser code or a public repository.

cURL · MiniMax M3.1 Flash
curl --fail-with-body --silent --show-error --max-time 120 \
  'https://api.y-api.bestvirtualgoods.com/v1/chat/completions' \
  -H "Authorization: Bearer ${TOKEN:?Set TOKEN first}" \
  -H 'Content-Type: application/json' \
  --data-binary @- <<'JSON'
{
  "model": "minimax/minimax-m3.1-flash",
  "messages": [
    {
      "role": "user",
      "content": "Here is a screenshot of a settings page and the JSON schema behind it. Build the form component with the same labels and spacing, and list any control in the screenshot that the schema cannot represent."
    }
  ],
  "max_tokens": 4096
}
JSON

How to evaluate the result

Render the component at the same viewport and compare it with the screenshot field by field. Controls the schema cannot represent should be named explicitly; silently dropping them is the failure to catch.

Before you choose

Should I call this ID or the `-preview` ID?

They are separate strings in the catalog with different prices. Pin the exact one your client sends and check the price table rather than assuming both bill alike; this page documents the standard ID shown above.

Sources & scope

Technical facts come from the cited model page and, where available, its linked publisher card. A card describes that checkpoint; it is not proof of the weights a gateway serves. Prices come only from the Y-API catalog. We do not claim measured latency, uptime or benchmark scores for this endpoint.