Skip to content

Hy3

hy3

Hy3 is Tencent's 295B-parameter Mixture-of-Experts (MoE) model, activating 21B parameters per token across 192 experts, and designed for reasoning, agentic workflows, and production-scale applications. It supports a 256K-token context window and configurable reasoning modes, including no-think, low, and high reasoning effort to balance speed and problem-solving depth. Optimized for long-horizon tasks, coding, and tool-driven execution, Hy3 delivers strong performance in multi-turn reasoning, constraint tracking, and stable tool calling. With an emphasis on grounded responses and reduced hallucinations, it is well suited for software development, document processing, financial analysis, game development, and enterprise agent workflows.

Context
262K tokens
Endpoint
Get API KeyCompare

Pricing

Input$0.14 / 1M
Output$0.58 / 1M
Cache Write (5m)Not published
Cache Write (1h)Not published
Cache ReadNot published
Web Search$0 / 1M

Quick Start

Select an endpoint and copy a working example for this model.

Endpoint:
python
from openai import OpenAI client = OpenAI(    api_key="YOUR_API_KEY",    base_url="https://api.apertis.ai/v1") response = client.chat.completions.create(    model="hy3",    messages=[        {"role": "user", "content": "Hello!"}    ],    max_tokens=1024,    temperature=0.7) print(response.choices[0].message.content) # Optional: Enable context compression to reduce token usage# response = client.chat.completions.create(#     model="hy3",#     messages=[{"role": "user", "content": "Hello!"}],#     extra_body={"compression": {"enabled": True, "model": "gpt-4.1-mini"}}# )

Supported Parameters

API docs
Common7 params
modelmessagesmax_tokenstemperaturetop_pstreamtools
Extended4 params
reasoning_effortstream_optionsthinkingextra_body

Cursor IDE Model IDs

Use these namespaced identifiers in Cursor IDE to avoid conflicts with built-in models.

hy3

Decision guidance

Fit the request contract before production.

Use this model when

  • The workload includes code generation or code-oriented text tasks listed in the current catalog record.
  • The required task matches the listed capabilities: text-to-text, text-to-code, translation.
  • The request depends on listed features such as vision, thinking, function-calling.
  • The input fits within the published 262K-token context record, with output and system overhead budgeted separately.

Check before production

  • Confirm the production client uses one of the listed request surfaces: /v1/chat/completions, /v1/responses, /v1/messages.
  • Estimate a representative request from the current Pay As You Go price fields instead of extrapolating from a tiny prompt.
  • Check the observed-availability card and run your own timeout, retry, and fallback test before relying on the model.

Compare with Other Models

See how this model compares to others from the same provider.