Stateless Responses compatibility: no stored responses, previous_response_id, Conversations, background jobs or Webhooks. This does not establish a provider-wide no-retention policy.
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.
The counter exists in the response schema; it is not proof of caching support.
Billing rules
Not collected
Limits & data boundaries
Not collected
No verified cache rate for this endpoint. An empty rate is not a zero charge.
Caching reviewed 12 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
Classification is an inference from the named native commercial service or licensed edge release, its official access documentation, and cross-checking the developer’s public-weight inventory. The named service weights were not published in the reviewed inventory. This does not classify every SenseNova model as closed: public U1, U1.5, Vision, SI, MARS, InteractiveOmni and Piccolo releases are excluded.
