Model
opencode-go/mimo-v2.5
Auth type
Subscription
Official documentation
https://opencode.ai/docs/go/
https://openrouter.ai/api/v1/models
Parameters to add or update
For opencode-go/mimo-v2.5, please verify and add/update the supported request parameters for the OpenAI-compatible Chat Completions route.
Observed/upstream-compatible parameters for Xiaomi MiMo V2.5 appear to include:
-
temperature
- type: number
- default: provider default / unspecified
- range: typically 0-2, exact range to confirm from provider
- applies to: sampling
-
top_p
- type: number
- default: provider default / unspecified
- range: 0-1
- applies to: nucleus sampling
-
max_tokens
- type: integer
- default: provider default / unspecified
- range: provider/model limit to confirm
- applies to: maximum completion tokens
-
stop
- type: string or string[]
- default: none
- applies to: stop sequences
-
presence_penalty
- type: number
- default: 0 / provider default
- range: provider range to confirm
- applies to: repetition/control
-
frequency_penalty
- type: number
- default: 0 / provider default
- range: provider range to confirm
- applies to: repetition/control
-
response_format
- type: object
- default: none
- allowed values: provider/OpenAI-compatible formats to confirm, likely
{ "type": "json_object" } or structured output formats if supported
- applies to: JSON / structured output
-
tools
- type: array
- default: none
- applies to: tool/function calling
-
tool_choice
- type: string or object
- default:
auto / provider default
- allowed values:
auto, none, required, or specific tool object, exact values to confirm
- applies to: tool/function calling
-
reasoning
- type: object or provider-specific reasoning config
- default: provider default / unspecified
- applies to: reasoning controls if supported by OpenCode Go for MiMo V2.5
- note: exact schema needs confirmation
-
include_reasoning
- type: boolean
- default: false / provider default
- applies to: returning reasoning content if supported
- note: exact behavior needs confirmation
Notes
OpenCode Go documents that MiMo-V2.5 is available through the opencode-go provider, but the public Go docs mainly list models, usage limits, request estimates, and pricing. I could not find a provider-specific page that explicitly lists all request parameters accepted for opencode-go/mimo-v2.5.
The parameter list above is based on the upstream/OpenAI-compatible behavior observed for Xiaomi MiMo V2.5 and should be verified against the actual OpenCode Go route.
Important context:
- MiMo V2.5 is a reasoning model.
- It supports tool use according to upstream/OpenAI-compatible metadata.
- It supports multimodal input upstream (
text+image+audio+video -> text), but this issue is only about configurable request parameters, not modality support.
- Please confirm whether
reasoning / include_reasoning are accepted on the OpenCode Go route and what exact schema they use.
Scope check
Model
opencode-go/mimo-v2.5
Auth type
Subscription
Official documentation
https://opencode.ai/docs/go/
https://openrouter.ai/api/v1/models
Parameters to add or update
For
opencode-go/mimo-v2.5, please verify and add/update the supported request parameters for the OpenAI-compatible Chat Completions route.Observed/upstream-compatible parameters for Xiaomi MiMo V2.5 appear to include:
temperaturetop_pmax_tokensstoppresence_penaltyfrequency_penaltyresponse_format{ "type": "json_object" }or structured output formats if supportedtoolstool_choiceauto/ provider defaultauto,none,required, or specific tool object, exact values to confirmreasoninginclude_reasoningNotes
OpenCode Go documents that
MiMo-V2.5is available through theopencode-goprovider, but the public Go docs mainly list models, usage limits, request estimates, and pricing. I could not find a provider-specific page that explicitly lists all request parameters accepted foropencode-go/mimo-v2.5.The parameter list above is based on the upstream/OpenAI-compatible behavior observed for Xiaomi MiMo V2.5 and should be verified against the actual OpenCode Go route.
Important context:
text+image+audio+video -> text), but this issue is only about configurable request parameters, not modality support.reasoning/include_reasoningare accepted on the OpenCode Go route and what exact schema they use.Scope check