Skip to content
Model infoModelsSnapshot: 15 Oct 2026

NAVER Cloud / HyperCLOVA X

HyperCLOVA X HCX-005

Text and image model with a 128,000-token context. Vision, function calling and tuned-model requests have separate API restrictions.

availableClosed weightsText generationVision
Official documentation (opens in a new tab)Reviewed 12 Oct 2026
12 of 18 specification fields collected
Input token limit128K128,000 tokens
Maximum output4.1K4,096 tokens
Input billingNot collectedCLOVA Studio
Output billingNot collectedNo inferred price

Specifications

Provider-documented facts. “Not collected” means we have not verified that field yet, not that the feature is unsupported.

Context / input limit
128,000 tokensSource for Context / input limit (opens in a new tab)

Context is the combined input and output budget. Separate maxima cannot be added together.

Maximum output
4,096 tokensSource for Maximum output (opens in a new tab)

The combined context budget still applies.

Streaming
SupportedSource for Streaming (opens in a new tab)

Native chat API documents token streaming using Accept: text/event-stream.

Batch processing
Not collected
Fine-tuning
SupportedSource for Fine-tuning (opens in a new tab)

PEFT support added July 17, 2025. Tuned v3 endpoints do not support image input, thinking, function calling or structured outputs.

Knowledge cutoff
Not collected
Parameters
Not collected
Architecture
Not collected
Languages
Not collected
Context caching
Not collected
Maximum input tokens
128,000 tokensSource for Maximum input tokens (opens in a new tab)

The combined context budget still applies.

Input image limits
One image per turn, at most five per request. BMP, PNG, JPG, JPEG or WebP; up to 20 MB per image and 50 MB for the entire request. Long side at most 2,240 px, short side at least 4 px; aspect ratio at most 5:1 in either direction.Source for Input image limits (opens in a new tab)

Access & pricing

Prices belong to an endpoint and billing tier. A provider listing does not guarantee access for every account or region.

API model ID
HCX-005
Access
NAVER Cloud account and CLOVA Studio API key required. Native documentation lists Classic and VPC availability; no paid inference call was made.
Regions
Account and contract dependent; the common API hostname alone does not prove data residency.
API endpoint URL
POST https://clovastudio.stream.ntruss.com/v3/chat-completions/HCX-005Source for API endpoint URL (opens in a new tab)
Request limits
Web/test: 60 requests/min, 60,000 tokens/min. Production: 300 requests/min, 180,000 tokens/min.Source for Request limits (opens in a new tab)

Published quota snapshot, not guaranteed throughput. Usage is aggregated by main account, including subaccounts; tuned models share the base model quota. Token accounting includes input plus reserved maximum output where applicable.

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.

API model ID
HCX-005
Access
NAVER Cloud account and CLOVA Studio API key required. Native documentation lists Classic and VPC availability; no paid inference call was made.
Regions
Account and contract dependent; the common API hostname alone does not prove data residency.
API endpoint URL
POST https://clovastudio.stream.ntruss.com/v1/openai/chat/completionsSource for API endpoint URL (opens in a new tab)
Endpoint caveat
The model catalog lists this compatibility route. OpenAI API parameters and features are not all supported; native capability support should not be read as parity on this route.Source for Endpoint caveat (opens in a new tab)
Tool calling
SupportedSource for Tool calling (opens in a new tab)

Documented for the v3 and OpenAI-compatible APIs; not supported on tuned models or concurrently with thinking.

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.

CLOVA Studio

HCX-005
Not verified

The reviewed model and API guides do not establish provider-side prompt caching for this model. Missing documentation is not evidence of no support.

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.

CLOVA Studio

HCX-005
Not verified

The reviewed model and API guides do not establish provider-side prompt caching for this model. Missing documentation is not evidence of no support.

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 NAVER native commercial model/service from its official API documentation and comparison with the public HyperCLOVA X SEED inventory. No public weights for this exact service were found in the reviewed sources. This does not establish that every NAVER service is closed; BGE-M3 and public SEED releases are excluded.

Classification evidence (opens in a new tab)

Lifecycle dates

Model released17 Apr 2025Source (opens in a new tab)

Sources reviewed