SageMaker Batch Transform workflow, not a managed API discount.
Endpoint pricing has not been collected. Check the provider for applicable rates.
Data & enterprise terms
Provider documents network-isolated deployment inside the customer VPC, with no outbound internet from the container. This applies to the self-hosted package, not the managed API.
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.
Amazon SageMaker · Sarvam package
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 for this exact native API release/service from provider documentation and review of Sarvam’s public weight inventory. No weights for this identity were identified. Public Sarvam language/translation weights and hosted third-party weights are excluded. A named service or version does not establish an independently disclosed checkpoint.
