hy3
hy3Compare hy3 API pricing, supported endpoints, capabilities and access options on Modelsell.
- Starting price
- Input / Output · 1M
- Context
- 262.1K
- Maximum input window
- Max output
- 128K
- Maximum tokens per response
- Modalities
- →
Pricing by Supplier
Capabilities / Supported modalities
Provider & data privacy
BPE (vendor-specific)Performance
Benchmarks
Scores on standardized evaluations. Higher percentages are better — and rank percentile shows
Metrics sourced fromArtificial Analysis 2026-09-30·hy3
This model is not included in the current benchmark snapshot.
Missing models or measurements are not zero scores.
Benchmark charts preserve the source model selection and reasoning settings. Missing models or measurements are not zero scores, and benchmark cost or speed is not this site’s service commitment.
About hy3
从需求沟通到可执行方案
HY3 适合处理需要反复确认条件、逐步推进的工作：根据需求设计前端页面，结合日志查找代码故障，阅读多份文档形成方案，或在工具帮助下完成一连串操作。它接收和输出文本，重点是理解任务、推理和组织行动。
对于开发团队，可以把已有组件、接口约定和交互要求一起交给它，让它先拆解页面状态，再生成代码与验收清单。涉及数据存储或持续集成的问题，则提供表结构、报错信息和现有配置，要求它说明修改会影响哪些环节。相比一句“帮我优化”，具体的约束能让建议更接近项目实际。
HY3 支持直接回答和不同程度的推理。简单问答、文字整理可以直接给出结果；多步数学、复杂代码分析或有冲突条件的决策，可以增加推理投入。它也支持工具调用和结构化输出，适合嵌入能查询资料、读取项目或调用业务接口的助手。实际查询与执行由应用提供的工具完成。
长对话中的条件继承是它关注的能力之一。协作时可以持续补充需求，但最好保留一份明确的约束清单，例如技术栈、禁止修改的接口和交付标准。遇到材料不足的地方，让它先指出缺口并提出验证办法；正式采用代码或方案前，再按验收清单检查结果。
Use cases and prompting
前端开发提示词
“请依据现有组件实现订单筛选页。技术栈与组件示例见下方；筛选条件需要同步到 URL，加载、空结果和接口失败都要有状态反馈。先列出状态流转与接口依赖，再给出最小实现，最后提供可手动验证的步骤。没有定义的字段请先列为待确认项。”
常见问题
- 需求改了几轮，怎样避免漏掉旧条件？每轮保留当前约束清单，并要求模型说明本次修改影响哪些已完成内容。
- 推理模式怎么选？一般整理用直接回答，复杂故障和多条件方案用更深入的推理；可先做小任务比较实际效果。
- 工具执行失败后怎么办？将错误结果回传给模型，让它先解释失败原因再调整调用，避免重复执行同一操作。
API access
API documentation
Code samples
/v1/chat/completions| Parameter | Type | Default / range | Description |
|---|---|---|---|
temperature | number | = 10 ~ 2 | Sampling temperature; lower is more deterministic |
top_p | number | = 10 ~ 1 | Nucleus sampling probability mass |
max_tokens | integer | >= 1 | Maximum number of tokens in the response |
frequency_penalty | number | = 0-2 ~ 2 | Penalises repetition of frequent tokens |
presence_penalty | number | = 0-2 ~ 2 | Encourages introducing new topics |
stop | array | — | Up to 4 strings that stop generation |
seed | integer | — | Deterministic sampling seed (best-effort) |
n | integer | = 1>= 1 | Number of completions to generate |
stream | boolean | = false | Stream tokens via Server-Sent Events |
response_format | object | — | Force JSON object or schema-conforming output |
tools | array | — | Tool / function declarations the model may call |
tool_choice | string | autononerequired | Tool-choice policy or specific tool name |
logprobs | boolean | = false | Return per-token log probabilities |
top_logprobs | integer | 0 ~ 20 | Number of top log probabilities returned per token |
logit_bias | object | — | Per-token logit bias map |
user | string | — | End-user identifier for abuse monitoring |
Replace <YOUR_API_KEY> with the API key from your token settings.
Authentication
All requests must include Authorization: Bearer <TOKEN> header. Anthropic-formatted endpoints accept the x-api-key header instead.
Generate tokens from the Tokens page; you can scope them to specific models, groups, IPs, and rate-limits.
Supported parameters
| Parameter | Type | Default / range | Description |
|---|---|---|---|
temperature | number | = 10 ~ 2 | Sampling temperature; lower is more deterministic |
top_p | number | = 10 ~ 1 | Nucleus sampling probability mass |
max_tokens | integer | >= 1 | Maximum number of tokens in the response |
frequency_penalty | number | = 0-2 ~ 2 | Penalises repetition of frequent tokens |
presence_penalty | number | = 0-2 ~ 2 | Encourages introducing new topics |
stop | array | — | Up to 4 strings that stop generation |
seed | integer | — | Deterministic sampling seed (best-effort) |
n | integer | = 1>= 1 | Number of completions to generate |
stream | boolean | = false | Stream tokens via Server-Sent Events |
response_format | object | — | Force JSON object or schema-conforming output |
tools | array | — | Tool / function declarations the model may call |
tool_choice | string | autononerequired | Tool-choice policy or specific tool name |
logprobs | boolean | = false | Return per-token log probabilities |
top_logprobs | integer | 0 ~ 20 | Number of top log probabilities returned per token |
logit_bias | object | — | Per-token logit bias map |
user | string | — | End-user identifier for abuse monitoring |
Rate limits
| Supplier | RPM | TPM | RPD |
|---|---|---|---|
| Tencent | Unlimited | Unlimited | Unlimited |
No restriction
Frequently asked questions about hy3
What is hy3?
Compare hy3 API pricing, supported endpoints, capabilities and access options on Modelsell.
How do I call hy3?
Create an API key with access to hy3, then use the exact model ID and a supported endpoint from the API access section. Request fields depend on the selected endpoint.
How is hy3 priced?
Pricing depends on the selected provider group and the model billing unit. The current input, output, request, or media prices are shown on this page before sign-up.
What is the context window of hy3?
The model catalog lists a context window of 262144 tokens. Check the selected endpoint for request limits.
What is the maximum output of hy3?
The model catalog lists a maximum output of 128000 tokens. Your request settings may set a lower limit.
How should I evaluate hy3 for my project?
Start with the use cases and prompting guidance on this page, then evaluate the model with representative inputs from your project.