Skip to content
Dashboard

Hy3

Hy3 is an Apache 2.0 Mixture-of-Experts model from the Tencent Hunyuan team, with 295B total parameters, 21B active per token, and three selectable reasoning levels. It supports a context window of 262.1K tokens and a max output of 262.1K tokens per request. Your use is subject to Tencent's Terms & Privacy Policies.

import { streamText } from 'ai'
const result = streamText({
model: 'tencent/hy3',
prompt: 'Why is the sky blue?'
})
Read docs

Playground

Try out Hy3 by Tencent. Usage is billed to your team at API rates. Free users (those who haven't made a payment) get $5 of credits every 30 days.

T
T

Hy3

Providers

Route requests across multiple providers. Copy a provider slug to set your preference. Visit the docs for more info. Using a provider means you agree to their terms, listed under Legal.

Provider
Context
Max Output
Latency
Throughput
Input
Output
Cache
Web Search
Capabilities
ZDR
No Training
Release Date
262K262K
0.2s
53tps
$0.14/M
$0.58/M
Read:$0.04/M
Write:
07/06/2026
262K262K
1.6s
72tps
$0.14/M
$0.58/M
Read:$0.04/M
Write:
07/06/2026
Throughput

P50 throughput on live AI Gateway traffic, in tokens per second (TPS). Visit the docs for more info.

Latency

P50 time to first token (TTFT) on live AI Gateway traffic, in milliseconds. View the docs for more info.

Uptime

Direct request success rate on AI Gateway and per-provider. Visit the docs for more info.

About Hy3

Tencent released Hy3 on July 6, 2026 under the Apache 2.0 license, publishing BF16 and FP8 weights on Hugging Face, ModelScope, GitCode, and CNB. Hy3 comes out of the Hunyuan line and follows the Hy3 Preview release from late April 2026.

The architecture is a Mixture-of-Experts (MoE) with 295B total parameters and 21B active per token, spread across 80 layers and 192 routed experts with top-8 routing. Attention is grouped-query with 64 heads and eight key-value heads. A separate 3.8B multi-token prediction layer drafts more than one token per forward pass, which serving stacks use for speculative decoding. The context window is 262.1K tokens, and one request can return up to 262.1K tokens.

Reasoning depth is a per-request setting. The reasoning_effort field accepts no_think for a direct answer, low for shallow reasoning, and high for deep chain-of-thought on math, coding, and analysis. no_think is the default, so you opt into reasoning tokens rather than paying for them on every call.

Tencent focused on tool-call and output-format stability, drawing on feedback from more than 50 of its own products. On SWE-Bench Verified, Hy3 holds accuracy variance within 4% across agent scaffoldings including CodeBuddy, Cline, and KiloCode, so a result from one harness carries to another. Internal evaluations built on real-world scenarios put the hallucination rate at 5.4%, down from 12.5%, and the commonsense error rate at 12.7%, down from 25.4%. On a multi-turn suite covering coreference resolution, ellipsis recovery, and constraint inheritance, the issue rate fell from 17.4% to 7.9%.

Tencent also ran a blind evaluation in which 270 experts scored tasks drawn from their own work. Hy3 averaged 2.67 out of four against GLM-5.1 at 2.51, with the widest margins on frontend development, data and storage, and CI/CD tasks.

Call Hy3 with one API key and get provider routing, automatic failover, and built-in observability. Integrate through the AI SDK, the Chat Completions API, the Responses API, the Messages API, or other supported API formats. Pay $0.14 per million input tokens, $0.58 per million output tokens, and $0.035 per million cached input tokens at current list rates.

What To Consider When Choosing a Provider

  • Configuration: Hy3 defaults to no_think, so a plain request returns a direct answer with no reasoning tokens. Set reasoning_effort to high on math, coding, and analysis work, and expect longer outputs and higher output-token spend when you do. Harness support for the field varies, so confirm your client forwards it.
  • Configuration: Tencent recommends sampling at temperature=0.9 and top_p=1.0. Start there before you tune, because the published quality figures assume those settings.
  • Configuration: Hy3 takes text in and returns text out. Route requests that carry images, audio, or video to a multimodal model.
  • Configuration: The hallucination, multi-turn, and expert-panel figures come from Tencent's own evaluations rather than a neutral third party. Validate on your own workload before you shift production traffic. For current throughput and latency, see live metrics on this page.
  • Zero Data Retention: AI Gateway supports Zero Data Retention for this model via direct gateway requests (BYOK is not included). To configure this, check the documentation.
  • Authentication: AI Gateway authenticates requests using an API key or OIDC token. You do not need to manage provider credentials directly.

When to Use Hy3

Best for

  • Tool-Heavy Agent Loops: Multi-step runs where 21B active parameters keep per-request compute low
  • Long-Context Analysis: Repositories, contracts, and report sets that fill the 262.1K tokens window
  • Mixed Reasoning Traffic: Requests that switch between direct answers and deep chain-of-thought
  • Multi-Turn Assistants: Long dialogues that must track references, intent, and inherited constraints
  • Grounded Question Answering: Work where a fabricated detail costs more than a missing answer

Consider alternatives when

  • Multimodal Inputs: Hy3 handles text only, so send images, audio, or video to a vision-capable model
  • Frontier Coding Ceilings: Larger flagship models still lead on the hardest coding suites
  • Fixed Client Parameters: A client that cannot pass reasoning_effort leaves Hy3 on direct answers
  • Short Single-Turn Chat: Reasoning depth adds output overhead that brief exchanges never recover

Conclusion

Hy3 pairs a 295B MoE with a 21B active footprint, a context window of 262.1K tokens, and reasoning you turn up per request. The reliability work on tool calls, grounding, and multi-turn tracking makes Hy3 a practical agent default rather than a benchmark showcase. Route it through AI Gateway for failover, observability, and one key across the catalog.