Published model label is not a verified API request selector.
Access
Announced for enterprise API and joint-development projects; current access to this exact revision requires confirmation.
Regions
Deployment-specific; no universal processing-region guarantee verified.
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.
ELYZA enterprise (earlier generation)
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.
Caching reviewed 14 Oct 2026
What the measurements say
Japanese MT-Bench
ELYZA · vendor-reported
9.08score / 10
September 2024 provider presentation, slide 16. Earlier 70B dialogue/task scores are reused from its launch; not an independent evaluation or a universal model ranking.
September 2024 provider presentation, slide 16. Earlier 70B dialogue/task scores are reused from its launch; not an independent evaluation or a universal model ranking.
September 2024 provider presentation, slide 16. Earlier 70B dialogue/task scores are reused from its launch; not an independent evaluation or a universal model ranking.
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
ELYZA explicitly distinguishes the generally published 8B weights from the 70B model offered through a demo, enterprise APIs and joint development. No matching public 70B checkpoint was verified; the open upstream model does not establish public weights for this derivative.
