Hy3
Hy3 is an Apache 2.0 Mixture-of-Experts model from the Tencent Cloud 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.
View API reference- Input and output price
- Prices from: Input $0.13, Output $0.52, Per 1M tokens
- 24h uptime
- Loading AI Gateway uptime
import { streamText } from 'ai'
const result = streamText({ model: 'tencent/hy3', prompt: 'Why is the sky blue?'})Copy link to headingPlayground
Try out Hy3 by Tencent Cloud. 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.
Hy3
Copy link to headingProviders
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 |
|---|
Copy link to headingUptime24 hours
Direct request success rate on AI Gateway and per-provider. Visit the docs for more info.
Copy link to headingThroughput24 hours
P50 throughput on live AI Gateway traffic, in tokens per second (TPS). Visit the docs for more info.
Copy link to headingLatency24 hours
P50 time to first token (TTFT) on live AI Gateway traffic, in milliseconds. View the docs for more info.
Getting started
Call Hy3 through AI Gateway with the AI SDK generateText and streamText functions, or through the OpenAI Chat Completions, OpenAI Responses, and Anthropic Messages APIs by changing the base URL. AI Gateway authenticates the request and routes it to an available provider.
Install the AI SDK (pnpm add ai dotenv), create an API key from the API Keys page, and set it as AI_GATEWAY_API_KEY in your environment. Full setup is covered in the text generation quickstart.
import { generateText } from 'ai';import 'dotenv/config';
async function main() { const result = await generateText({ model: 'tencent/hy3', prompt: 'Why is the sky blue?', });
console.log(result.text);}
main().catch(console.error);Top-level parameters
The same Hy3 request in each API format AI Gateway supports.
import { generateText } from 'ai';import 'dotenv/config';
async function main() { const result = await generateText({ model: 'tencent/hy3', system: 'You are a concise technical assistant.', prompt: 'Summarize the tradeoffs between static generation and SSR.', maxOutputTokens: 1024, });
console.log(result.text);}
main().catch(console.error);Standard parameters like prompt, messages, temperature, and tools work as documented in the AI SDK docs. These are the parameters with model-specific behavior.
| Parameter | Type | Required | Description |
|---|---|---|---|
model | string | Yes | Model ID in the form creator/model, e.g. tencent/hy3. AI Gateway routes the request to an available provider. |
maxOutputTokens | number | No | Hard cap on generated tokens. Hy3 supports up to 262,144 output tokens. Reasoning tokens count toward this limit. |
reasoning | 'provider-default' | 'none' | 'minimal' | 'low' | 'medium' | 'high' | 'xhigh' | No | Provider-agnostic reasoning effort, available in AI SDK 7 or later. Maps to the provider’s native reasoning configuration; reasoning settings under providerOptions take precedence when both are set. See the Reasoning section below. |
providerOptions | Record<string, JSONValue> | No | AI Gateway routing options under gateway, plus any provider-native options under the provider’s own namespace — see the table below. |
Input limits
| Input | Formats | Sources | Max count | Max size | Limits |
|---|---|---|---|---|---|
| Text | — | — | — | — | Prompt and response share the 262K-token context window |
Provider options
Set AI Gateway routing options under providerOptions.gateway. For provider-specific options, pass them under the provider’s namespace as documented by the AI SDK.
Learn more in the AI SDK provider docs.
import { generateText } from 'ai';import 'dotenv/config';
async function main() { const result = await generateText({ model: 'tencent/hy3', prompt: 'Why is the sky blue?', providerOptions: { gateway: { only: ['deepinfra', 'novita'], }, }, });
console.log(result.text);}
main().catch(console.error);These AI Gateway routing options apply to every model. Provider-specific options pass through under the provider’s own namespace (for example providerOptions.anthropic) exactly as documented by the AI SDK.
| Parameter | Type | Required | Description |
|---|---|---|---|
providerOptions.gateway.only | string[] | No | Restrict routing to these provider slugs. Requests fail over only within the listed providers. |
providerOptions.gateway.order | string[] | No | Preferred provider order. Listed providers are tried first; unlisted providers remain available as fallbacks. |
providerOptions.gateway.sort | 'cost' | 'ttft' | 'tps' | No | Rank candidate providers by price, time to first token, or tokens per second instead of the default routing order. |
providerOptions.gateway.zeroDataRetention | boolean | No | Route only to providers with a zero-data-retention policy for this model. |
Routing across providers
AI Gateway serves the same model through multiple providers and fails over automatically. order expresses a preference while keeping every provider eligible; only is a hard allowlist — if none of the listed providers are available the request fails instead of falling back.
Options under a provider's own namespace (for example providerOptions.anthropic) are forwarded to that provider with the request. Providers ignore option namespaces that don't apply to them, so it is safe to set provider options alongside gateway routing options.
Reasoning
AI Gateway bridges reasoning across every API format. The AI SDK exposes a provider-agnostic top-level reasoning level (none, minimal, low, medium, high, or xhigh); the Chat Completions and Responses formats take the same effort under reasoning.effort; and the Anthropic Messages format uses a native thinking token budget. Whichever you send, the gateway maps it to the target model’s native configuration, converting between effort levels and token budgets as needed. Reasoning-related settings under providerOptions take full precedence over the top-level reasoning value and are never merged. Reasoning tokens typically count toward your output-token usage, though how they’re reported and billed varies by provider.
Learn more in the AI Gateway reasoning guide.
import { generateText } from 'ai';import 'dotenv/config';
async function main() { const result = await generateText({ model: 'tencent/hy3', prompt: 'Explain the Monty Hall problem step by step.', reasoning: 'high', });
console.log(result.text);}
main().catch(console.error);Tool calling
Expose tools the model can call. Define each tool’s inputs with a Zod schema.
import { generateText, tool } from 'ai';import { z } from 'zod';import 'dotenv/config';
async function main() { const result = await generateText({ model: 'tencent/hy3', prompt: 'What is the weather in San Francisco?', tools: { getWeather: tool({ description: 'Get the current weather for a location', inputSchema: z.object({ location: z.string() }), execute: async ({ location }) => ({ location, temperatureC: 18 }), }), }, });
console.log(result.text);}
main().catch(console.error);Copy link to headingAbout Hy3
Tencent Cloud 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 Cloud 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 Cloud 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.126 per million input tokens, $0.522 per million output tokens, and $0.0315 per million cached input tokens at current list rates.
Copy link to headingWhat To Consider When Choosing a Provider
- Configuration: Hy3 defaults to
no_think, so a plain request returns a direct answer with no reasoning tokens. Setreasoning_efforttohighon 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 Cloud recommends sampling at
temperature=0.9andtop_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 Cloud'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: Zero Data Retention is available for this model. It is offered on a per-provider and model basis. See the documentation for details.
- Authentication: AI Gateway authenticates requests using an API key or OIDC token. You do not need to manage provider credentials directly.
Copy link to headingWhen 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_effortleaves Hy3 on direct answers - Short Single-Turn Chat: Reasoning depth adds output overhead that brief exchanges never recover
Copy link to headingConclusion
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.
Copy link to headingFrequently Asked Questions
What is Hy3?
Hy3 is a text-only Mixture-of-Experts language model from the Tencent Cloud Hunyuan team, released on July 6, 2026. It carries 295B total parameters with 21B active per token and succeeds the Hy3 Preview from late April 2026.
What architecture does Hy3 use?
A Mixture-of-Experts (MoE) design with 295B total parameters, 21B active per token, 80 layers, and 192 routed experts using top-8 routing. Attention is grouped-query with 64 heads and eight key-value heads, and a 3.8B multi-token prediction layer supports speculative decoding.
How do the three reasoning modes work?
Set
reasoning_efforton the request.no_thinkreturns a direct answer and is the default,lowapplies shallow reasoning, andhighapplies deep chain-of-thought for math, coding, and analysis. Providers expose the field differently, so check that your client forwards it, and remember reasoning tokens count toward your output budget.What is the context window for Hy3?
Hy3 supports a context window of 262.1K tokens and a max output of 262.1K tokens per request. That covers long agent transcripts, large document sets, and repository-scale code review.
Is Hy3 open source?
Yes. Tencent Cloud released Hy3 under the Apache License 2.0, with BF16 and FP8 weights on Hugging Face, ModelScope, GitCode, and CNB. Through AI Gateway you use hosted inference, so licensing matters only if you also run the weights yourself.
What sampling parameters does Tencent Cloud recommend?
temperature=0.9andtop_p=1.0. Published quality figures assume those settings, so treat them as the starting point before you tune for your own task.How consistent is Hy3 across agent frameworks?
SWE-Bench Verified accuracy varies by less than 4% across scaffoldings including CodeBuddy, Cline, and KiloCode. That narrow spread means a result you measure in one harness generally holds when you switch to another.
How much does Hy3 hallucinate?
Tencent Cloud's internal evaluations on real-world scenarios report a 5.4% hallucination rate, down from 12.5%, and a 12.7% commonsense error rate, down from 25.4%. The stated design target is to answer when grounded and say so when evidence is missing.
How do I call Hy3 through AI Gateway?
Use the model identifier
tencent/hy3with the AI SDK, the Chat Completions API, the Responses API, the Messages API, or another supported API format. You authenticate with an AI Gateway API key, and no Tencent Cloud account is needed.Does AI Gateway support Zero Data Retention for Hy3?
Yes, Zero Data Retention is available for this model. Zero Data Retention is offered on a per-provider basis. See https://vercel.com/docs/ai-gateway/capabilities/zdr for details.
Your use is subject to Tencent Cloud's Terms & Privacy Policies.