Selector retired June 30, 2026 after replacement by mimo-v2.5-tts on June 27. The default voice was remapped by cluster.
Regions
API cluster/account specific; no residency or jurisdiction guarantee inferred.
Endpoint pricing has not been collected. Check the provider for applicable rates.
Data & enterprise terms
Retention, training use, regional processing and enterprise terms have not been summarized for this endpoint.
Caching
Caching can reuse earlier input processing. Availability, lifetime and billing depend on the endpoint. A cache hit still generates a new response.
01 / INITIAL INPUTProcess & retain
The system processes eligible input and retains reusable state.
02 / LATER REQUESTCheck available state
Reuse depends on matching input, session state and the cache policy.
03 / CACHE HITReuse & generate
Reusing state can reduce repeated work. Any charges follow the billing rules below.
Xiaomi MiMo API
mimo-v2-tts
Not verified
How it works
Not collected
Minimum reusable input
Not collected
Lifetime & refresh
Not collected
How to enable it
Not collected
Usage fields
Not collected
Billing rules
Not collected
Limits & data boundaries
Not collected
No verified cache rate for this endpoint. An empty rate is not a zero charge.
What the measurements say
No benchmark observations have been added for this model. We do not turn a vendor description into a performance score.
Latency and throughput depend on the host, request size, reasoning settings and load. There is no measured speed or global usage figure in this record.
The record behind the model
Why it is included
Inferred closed-weight classification for this exact hosted MiMo release from the original release description and developer public-weight inventory. The matching weights were not found. Later MiMo V2.5/V2.6 language weights and MiMo V2.5 ASR are explicitly public and are not substituted for this release; public MiMo-Audio components do not establish public weights for the separate TTS service.
