Choosing this model
Selection advice by Y-API. The checks below are suggested evaluations, not published test results.
Where to start
Evaluate it on demanding multimodal work where the Flash variant has fallen short: video understanding, audio-plus-text reasoning, or tasks that need the larger parameter count to hold a complex specification.
What to watch for
A published parameter count describes the checkpoint, not the throughput or quality you will see through the gateway. Audio and video input still need their own compatibility test before you build on them.
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_biasmax_tokensmin_ppresence_penaltyreasoningrepetition_penaltyresponse_formatseedstopstructured_outputstemperaturetool_choicetoolstop_ktop_p
API pricing & cost estimate
- Estimated credit consumed
- $1.00
- Estimated cash equivalent
- $0.10
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.
| Model | Estimated credit consumed | Estimated cash equivalent |
|---|---|---|
| MiMo-V2.6-Pro | $1.00 | $0.10 |
| MiMo-V2.6-Flash | $0.36 | $0.036 |
| MiMo-V2.5 | Free — no credit deducted | |
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
Given a screen recording and its narration, list the steps the user actually performed, in order, and flag any step the narration does not mention.
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 --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-pro",
"messages": [
{
"role": "user",
"content": "Given a screen recording and its narration, list the steps the user actually performed, in order, and flag any step the narration does not mention."
}
],
"max_tokens": 4096
}
JSONHow to evaluate the result
Compare the extracted steps against a manually written ground truth. Then run the same recording through the Flash entry to see whether the Pro tier is worth its higher price for your footage.
Before you choose
Does the linked card describe the served weights?
The card names a checkpoint from the publisher’s training pipeline. It is useful technical background, but it does not prove which weights the gateway serves, so verify behavior with your own requests.
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.