hy3
hy3Use the HY3 API for coding and reasoning. Send conversation messages and include tool definitions on supported routes. The listed routes publish a context limit of 256,000 tokens. Use it to work through multi-step coding tasks or review longer technical material. Compare the available provider routes, request examples, and usage prices on OpenAny.
- Published price
- From $0.096 / 1M tokens
- Billing unit
- / 1M tokens
- Context / Max output
- 256K / 128K
- Listed routes
- 1
| Provider | Pricing | Latency | Uptime | Supply | Route |
|---|---|---|---|---|---|
Live | Input $0.096 / 1M tokens Output $0.384 · Cache $0.020 | 270ms | — | Verified |
- Input
- $0.096
- Output
- $0.384
- Cache read
- $0.020
Source: the selected provider route in OpenAny's public model catalog. A price update timestamp is not supplied.
Other parameters (13)
Result preview
Tencent · 270ms
Response example. Run to see the actual response.
{
"id": "f022f679-542b-4228-a021-0d392af48802",
"model": "hy3",
"usage": {
"total_tokens": 28,
"prompt_tokens": 16,
"completion_tokens": 12,
"prompt_tokens_details": {
"cached_tokens": 0
},
"completion_tokens_details": {
"reasoning_tokens": 0
}
},
"object": "chat.completion",
"choices": [
{
"index": 0,
"message": {
"role": "assistant",
"content": "Hello! 👋 How can I help you today?"
},
"finish_reason": "stop"
}
],
"created": 1784710724,
"openmodels_cost": 7
}Request example
POST /v1/chat/completionscurl 'https://api.openany.si/v1/chat/completions' \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"messages": [
{
"content": "hello",
"role": "user"
}
],
"model": "hy3",
"frequency_penalty": 0,
"n": 1,
"presence_penalty": 0,
"stream": false,
"temperature": 1,
"top_p": 1
}'Model API questions
How do I call hy3 through OpenAny?
Use model ID hy3 with an OpenAny key and the operation published in this model's API tab. The model API base is https://api.openany.si/v1. Confirm the protocol and request schema; model availability does not imply every OpenAI API operation is supported.
How is hy3 billed?
Compare the published rate and billing unit of the selected provider route. Input, output and cache token rates may differ. Image, audio and video models can use other units. Recorded usage determines the charge under that route's billing contract.
Are Community and Verified routes the same as an official publisher API?
No. Inspect the provider name and supply classification for the specific route. A marketplace listing or a supply label is not a claim of publisher endorsement, identical service or measured uptime. Different route prices may reflect different supply and conditions.
Where do these prices come from, and when were they updated?
Rates come from the provider routes in OpenAny's public model catalog, not an independent quote from the model publisher. The catalog does not supply a price update timestamp. A page or catalog snapshot date is not a price revision date. Compare supply, billing units, tiers and conditions; a lower listed rate alone does not establish equivalent service or explain the price difference.
Use hy3 with your agent
Inspect endpoint contracts and confirm availability and pricing before a paid call.