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.
Relace Repos
Not verified
No model-specific cache support or discounted cache tariff established.
How it works
Not collected
No model-specific cache support or discounted cache tariff established.
Minimum reusable input
Not collected
No model-specific cache support or discounted cache tariff established.
Lifetime & refresh
Not collected
No model-specific cache support or discounted cache tariff established.
How to enable it
Not collected
No model-specific cache support or discounted cache tariff established.
Usage fields
Not collected
No model-specific cache support or discounted cache tariff established.
Billing rules
Not collected
No model-specific cache support or discounted cache tariff established.
Limits & data boundaries
Not collected
No model-specific cache support or discounted cache tariff established.
No verified cache rate for this endpoint. An empty rate is not a zero charge.
Caching reviewed 15 Oct 2026
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
Licensed hosted orchestration service; not an independently established model checkpoint.
