Subscription includes TTS, EVI and voice features, with plan allowances and overages. Current numeric rates remain unverified because the public pricing page redirects to the homepage.Source for Usage metering (opens in a new tab)
Named native options grouped under EVI 3. Web search is a service option; independent checkpoint weights are not established.
Endpoint pricing has not been collected. Check the provider for applicable rates.
Data & enterprise terms
Privacy documentation is internally inconsistent: the EVI-specific section says retention and possible training are enabled by default, while the general API FAQ says API data is not used for training. Verify the account settings and contract; no blanket no-training guarantee is asserted.
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.
Hume API
3
Not verified
No verified provider-side caching policy or cache rate. Continuation, stored chats and downloaded audio do not establish prompt caching.
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 named Hume API release/service from provider documentation and its public weight inventory. No weights for this identity were identified; public TADA releases are excluded. A service record does not assert a separately disclosed checkpoint or parameter count.
