MiMo-V2.6-Flash

xiaomi/mimo-v2.6-flash

MiMo-V2.6-Flash is Xiaomi’s efficiency-oriented multimodal entry for coding and agent workflows. OpenRouter links the Flash-RL checkpoint card, which describes reinforcement-learning work across varied task environments.

Input · Account credit
$0.18

per 1M tokens

Cash equivalent $0.018

Output · Account credit
$0.36

per 1M tokens

Cash equivalent $0.036

Context window
1,050,000

tokens · OpenRouter

Input → Output
Text · Image · Video · Audio→ 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

Try it for a longer task that must retain constraints across revisions: a research summary, a code change or a visual review followed by corrections. Track which requirements survive each turn.

What to watch for

The catalog ID and the linked Flash-RL card use different names. The card is useful technical background, not proof of a gateway’s weights. As with V2.5, listed media inputs do not establish media generation.

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,050,000 tokens
Input
Text · Image · Video · Audio
Output
Text
Listed on OpenRouter
Parameters listed by OpenRouter
frequency_penaltyinclude_reasoninglogit_biaslogprobsmax_tokensmin_ppresence_penaltyreasoningrepetition_penaltyresponse_formatseedstopstructured_outputstemperaturetool_choicetoolstop_ktop_logprobstop_p
OpenRouter model page & specifications

Estimate your cost

Estimated credit consumed
$0.36
Estimated cash equivalent
$0.036

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
MiMo-V2.6-Flash$0.36$0.036
MiMo-V2.5Free — no credit deducted
DeepSeek V4.1 Flash$0.70$0.07

Use the API

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

Summarize these constraints and revise the plan without dropping any: no new dependencies; keep the public API; add retry support only for idempotent requests.

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 · MiMo-V2.6-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": "xiaomi/mimo-v2.6-flash",
  "messages": [
    {
      "role": "user",
      "content": "Summarize these constraints and revise the plan without dropping any: no new dependencies; keep the public API; add retry support only for idempotent requests."
    }
  ],
  "max_tokens": 4096
}
JSON

How to evaluate the result

Check that all three constraints remain explicit after a follow-up change. In a coding run, inspect the dependency diff and test non-idempotent requests to catch silent scope expansion.

Before you choose

Is the Flash-RL model card the exact API identifier?

No. Use xiaomi/mimo-v2.6-flash in the request. The linked publisher card names a checkpoint; copying that repository name into the model field would select a different, unlisted identifier.

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.