tencent
Hy3
Built for real-world business scenarios, Hy3 features a 295B/21B active MoE architecture, native 256K context support, and three reasoning modes. It enhances coding, long-form comprehension, multi-turn dialogue, and agentic task execution, balancing reliability, efficiency, and cost across both high-frequency interactions and complex workflows.
const response = await fetch('https://api.minirouter.sh/v1/chat/completions', { method: 'POST', headers: { Authorization: `Bearer ${process.env.MINIROUTER_KEY}`, 'Content-Type': 'application/json', }, body: JSON.stringify({ model: 'tencent/hy3', messages: [{ role: 'user', content: 'Why is the sky blue?' }], }),}) const data = await response.json()console.log(data.choices[0].message.content)Overview
Live catalog values only. MiniRouter does not publish latency or throughput here until those measurements are connected to the public feed.
- Model type
- language
- Context window
- 262,144
- Maximum output
- 262,144
- Input / 1M tokens
- $0.147
- Output / 1M tokens
- $0.609
- Released
- 2026-07-06
Prices include the MiniRouter fee. Compatibility snapshot: 2026-08-06. Input: text. Output: text.
Endpoints
/v1/chat/completions/v1/messages/v1/responsesPlatform-funded routing only. Caller BYOK credentials and OIDC-based upstream authentication are intentionally excluded; authenticate with a MiniRouter bearer key.
Captured parameters: max_tokens, temperature, stop, tools, tool_choice, reasoning, include_reasoning.
API
Use the setup panel above to switch between Chat Completions, Messages, and supported client configuration drafts. Every snippet keeps the model ID unchanged.
https://api.minirouter.sh/v1tencent/hy3Providers
MiniRouter selects from the configured routes below. Priority is the catalog order, not a latency or availability score.
| Provider | Priority | Input / 1M | Output / 1M | Parameters | Access |
|---|---|---|---|---|---|
vercel | 1 | $0.147 | $0.609 | max_tokens, temperature, stop, tools, tool_choice, reasoning, include_reasoning | MiniRouter balance |