The general automatic-caching guide demonstrates M3; explicit-cache support lists M2.x. M3.1-specific cache limits, eligibility and pricing are not verified.
Endpoint pricing has not been collected. Check the provider for applicable rates.
Data & enterprise terms
The March 30, 2026 service terms retain provider IP and allow use of inputs and generated content to provide, maintain, develop and improve the service. This review does not establish a no-training or zero-retention guarantee.
Endpoint pricing has not been collected. Check the provider for applicable rates.
Data & enterprise terms
The March 30, 2026 service terms retain provider IP and allow use of inputs and generated content to provide, maintain, develop and improve the service. This review does not establish a no-training or zero-retention guarantee.
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.
MiniMax
MiniMax-M3.1-Flash-Preview
Not verified
No model-specific cache contract verified for this endpoint.
How it works
Not collected
No model-specific cache contract verified for this endpoint.
Minimum reusable input
Not collected
No model-specific cache contract verified for this endpoint.
Lifetime & refresh
Not collected
No model-specific cache contract verified for this endpoint.
How to enable it
Not collected
No model-specific cache contract verified for this endpoint.
Usage fields
Not collected
No model-specific cache contract verified for this endpoint.
Billing rules
Not collected
No model-specific cache contract verified for this endpoint.
Limits & data boundaries
Not collected
No model-specific cache contract verified for this endpoint.
No verified cache rate for this endpoint. An empty rate is not a zero charge.
MiniMax
MiniMax-M3.1-Flash-Preview
Not verified
No model-specific cache contract verified for this endpoint.
How it works
Not collected
No model-specific cache contract verified for this endpoint.
Minimum reusable input
Not collected
No model-specific cache contract verified for this endpoint.
Lifetime & refresh
Not collected
No model-specific cache contract verified for this endpoint.
How to enable it
Not collected
No model-specific cache contract verified for this endpoint.
Usage fields
Not collected
No model-specific cache contract verified for this endpoint.
Billing rules
Not collected
No model-specific cache contract verified for this endpoint.
Limits & data boundaries
Not collected
No model-specific cache contract verified for this endpoint.
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 service variant: the exact model is documented through MiniMax service access and no corresponding weight release was identified in the reviewed official MiniMaxAI repository inventory. Service terms reserve underlying IP. Public M-series, H3 and Music 3 weights are explicitly excluded; the OpenAPI MIT label licenses documentation, not model weights.