hy3Tencent
- endpoints
- 2
- regions
- 1
- api
- chat
- released
- July 2026
capabilities 4/8
| # | flags | ||||||
|---|---|---|---|---|---|---|---|
| 1 | Global | 262K | $0.13 | $0.53 | $0.03 | no-train | |
| 2 | Global | 262K | $0.14 | $0.58 | $0.04 | zdr |
no measured traffic for this model yet. the endpoints table above carries provider pricing
no published benchmark scores for this model
hy3requesty routes this id across every provider serving hy3, picking on price and health and failing over automatically. the id stays valid when a provider changes underneath it
Base url is https://router.requesty.ai/v1 for every id here. One key reaches the whole catalog.
from openai import OpenAI client = OpenAI( api_key="YOUR_REQUESTY_API_KEY", base_url="https://router.requesty.ai/v1",) response = client.chat.completions.create( model="hy3", messages=[ {"role": "user", "content": "Explain quantum computing in one paragraph."}, ],) print(response.choices[0].message.content)
Change the base url, use your Requesty key, set the model to any id in the call pane. Existing OpenAI SDK code needs no other edit, and the same key reaches every other model in the catalog, so switching later is a one-parameter change. Browse all models
Hy3 is built for real world business scenarios with a 295B total, 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 high frequency interactions and complex workflows.
questions 6
Which providers serve hy3?
How much does hy3 cost?
Is hy3 open weights?
What is the context window of hy3?
How do I use hy3 with the OpenAI SDK?
Should I call hy3 by its managed id or a provider id?
more from tencent 1
| model | context | from /M | providers |
|---|---|---|---|
| hy4-preview | 1.0M | $0.83 | 1 |
route hy3 through one endpoint
One key for 2 providers on this model and 600+ others. No markup on provider prices, automatic failover, caching built in. Weekly aggregates in the measured pane come from production traffic routed through Requesty, one line per provider on a shared axis. Methodology
