Is hy3-preview deprecated?

Q: Is hy3-preview deprecated?

No — still supported. Listed by openrouter. No retirement date announced. Neither the provider's API nor its documentation has been checked for this model.

NOT DEPRECATED

Listed by openrouter. No retirement date announced. Neither the provider's API nor its documentation has been checked for this model.

state=alive sunset=none days_remaining=n/a severity=low sources=openrouter evidence_tier=catalog confirmed_by_endpoint=false documented_by_provider=false replacement=none corroborated=single-source divergent_fields=none checked=2026-09-16 03:02Z

tencent/hy3-preview

Vendor: tencent. Tracked by 1 of 5 sources.

What each source reports

**endpoint** = the provider's own machine-readable API, the strongest evidence. **provider docs** = the provider's own documentation, read by a model — first-party content, inferred reading. Unlabelled rows are third-party catalogs. Where sources disagree both values are shown rather than silently reconciled.
Source	ID	Context	Max out	In $/Mtok	Out $/Mtok	Sunset
openrouter	tencent/hy3-preview	262,144	235,929	$0.18	$0.6	—

Change history

Severity	Change	What	Detected
medium	repriced	tencent/hy3-preview: input_price_per_mtok $0.06/Mtok to $0.18/Mtok	2026-08-15
medium	repriced	tencent/hy3-preview: output_price_per_mtok $0.21/Mtok to $0.60/Mtok	2026-08-15
medium	repriced	tencent/hy3-preview: cache_read_price_per_mtok $0.02/Mtok to $0.06/Mtok	2026-08-15
high	modified	tencent/hy3-preview: capabilities lost frequency_penalty, presence_penalty, repetition_penalty, response_format, stop, structured_outputs	2026-08-03
low	modified	tencent/hy3-preview: capabilities gained frequency_penalty, presence_penalty, repetition_penalty, response_format, stop, structured_outputs	2026-08-02