Hunyuan

tencent/hy3

$0.0880 / M input tokens · $0.3530 / M output tokens

HY3 is a Tencent Hunyuan model route on OurToken for developers who want a low-cost chat completions model for application testing, coding support, and production evaluation.

Get API Key
24H Status Monitor
100% uptime
3 hours agonow
Available

2026-07-09 13:08:26 UTC

Pricing

Pay-per-use

No upfront costs, pay only for what you use

60% of official price
Input$0.147 / M$0.0880 / M Tokens
Output$0.588 / M$0.3530 / M Tokens

API Usage

API Access Guide

Base URLhttps://api.ourtoken.ai/v1
API Endpointchat/completions
Full URLhttps://api.ourtoken.ai/v1/chat/completions
Model IDhy3
Get API Key

Code examples

Use the OurToken API endpoint for this model. The examples below use direct HTTP requests and the recommended endpoint for the model family.

curl https://api.ourtoken.ai/v1/chat/completions \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{
    "model": "hy3",
    "messages": [
      {
        "role": "user",
        "content": "Hello!"
      }
    ],
    "max_tokens": 256
  }'

Chat Completions API Reference

Create a chat response with the OpenAI Chat Completions-compatible endpoint. Use https://api.ourtoken.ai/v1 as the SDK Base URL and POST /chat/completions as the endpoint.

Authorization

Content-Typeapplication/json
AuthorizationBearer YOUR_API_KEY

Request Body

FieldTypeRequiredDescription
modelstringRequiredModel ID to call.
messagesarray<object>RequiredConversation messages sent to the model.
max_tokensintegerOptionalMaximum number of output tokens.
temperaturenumberOptionalSampling temperature.
top_pnumberOptionalNucleus sampling parameter.
streambooleanOptionalWhether to return a streaming response.
stream_optionsobjectOptionalAdditional options for streaming responses.
toolsarray<object>OptionalTools available to the model.
tool_choicestring | objectOptionalControls how the model selects tools.
response_formatobjectOptionalControls structured output, such as JSON object responses.

Response Body

FieldTypeRequiredDescription
idstringRequiredUnique chat completion identifier.
object"chat.completion"RequiredObject type returned by the Chat Completions API.
createdintegerRequiredUnix timestamp when the response was created.
modelstringRequiredModel that produced the response.
choicesarray<object>RequiredCandidate responses returned by the model.
choices[].message.rolestringRequiredRole of the returned chat message.
choices[].message.contentstringOptionalText content in the returned chat message.
choices[].finish_reasonstringOptionalReason generation stopped.
usageobjectOptionalToken usage information for the chat completion.
usage.prompt_tokensintegerOptionalInput token count.
usage.completion_tokensintegerOptionalOutput token count.
usage.total_tokensintegerOptionalTotal token count.
usage.prompt_tokens_detailsobjectOptionalBreakdown of input token usage.
usage.prompt_tokens_details.cached_tokensintegerOptionalTokens served from cache.

Model Introduction

Hunyuan hy3

HY3 is a Tencent Hunyuan model route on OurToken for developers who want a low-cost chat completions model for application testing, coding support, and production evaluation.

Use HY3 when your team wants Tencent Hunyuan model access through the same OurToken API workflow used for other LLM routes. OurToken keeps the hy3 model ID, API examples, availability status, and pricing details close to the implementation workflow.

Why It Looks Great

  • Tencent Hunyuan route for cost-sensitive chat and assistant workloads.
  • OpenAI-compatible chat completions setup through the OurToken endpoint.
  • Dedicated route page for model ID, code examples, status, and pricing review.
  • Useful for comparing real prompt quality, latency, token usage, and cost across providers.
  • Simple path from Tencent model discovery into API implementation.

Key Features

  • Model ID: hy3
  • Provider: Tencent Hunyuan
  • Input price: $0.0880 per 1M tokens on OurToken
  • Output price: $0.3530 per 1M tokens on OurToken
  • Cache read price: $0.0220 per 1M tokens on OurToken
  • Cache write price: $0 per 1M tokens on OurToken
  • API endpoint: chat completions
  • Evaluation focus: chat, coding help, multilingual prompts, route comparison, and production fit

Specifications

ProviderTencent Hunyuan
Model IDhy3
Model TypeLarge Language Model (LLM)
OurToken Input Price$0.0880 / 1M tokens
OurToken Output Price$0.3530 / 1M tokens
OurToken Cache Read Price$0.0220 / 1M tokens
OurToken Cache Write Price$0 / 1M tokens
Official Input Reference$0.147 / 1M tokens
Official Output Reference$0.588 / 1M tokens
Official Cache Read Reference$0.0367 / 1M tokens
Official Cache Write Reference$0 / 1M tokens
Context WindowReview current provider and route documentation
API Endpointhttps://api.ourtoken.ai/v1/chat/completions

tencent hy3 api Features for Developers

Use tencent hy3 api to test the hy3 model, compare Hunyuan Hy3 pricing, and evaluate Tencent workflows through one API.

API Access

Call tencent hy3 api through the OurToken unified endpoint with model ID hy3. This keeps API keys, request examples, route status, and model testing in one developer workflow for teams evaluating Tencent Hunyuan access.

Pricing Review

Review Hunyuan Hy3 pricing before production rollout. OurToken lists $0.0880 input, $0.3530 output, $0.0220 cache read, and $0 cache write per 1M tokens, while public official references show higher baseline pricing.

Model Context

Public Tencent Hy3 model card materials describe a 295B-parameter MoE architecture, 21B active parameters, and long-context positioning. Treat those figures as provider or benchmark context, then validate the hy3 model against your own prompts on OurToken.

Benchmark Review

Use tencent hy3 benchmarks as research signals, not production guarantees. Compare coding, agent, reasoning, and long-context claims with your own workload, latency targets, and acceptance criteria before routing traffic to hy3.

Provider Comparison

HY3 is useful when teams compare Tencent with Qwen, GLM, DeepSeek, MiniMax, OpenRouter listings, or Hugging Face references. OurToken focuses on the active hy3 route, current pricing, and a repeatable API workflow.

Production Fit

Before adopting hy3 tencent traffic paths, test expected prompt sizes, output lengths, structured answer needs, error handling, and cost. The right route should reflect workload quality, availability, pricing, and support requirements.

How to Use tencent hy3 api on OurToken

Create an API key, set hy3 as the model, call chat completions, review pricing, compare benchmarks, and monitor route quality.

Create Key

Create an OurToken API key from the dashboard and store it in a secure server-side environment variable. This gives your backend a stable credential for tencent hy3 api calls without exposing secrets in browser code.

01

Set Model

Use hy3 as the model value in your request body. Keep the model ID configurable so your team can compare Hunyuan Hy3 API behavior with Qwen, GLM, DeepSeek, MiniMax, or existing production baselines.

02

Call Endpoint

Send requests to the OurToken chat completions endpoint with your API key, model ID, and prompt payload. Existing OpenAI-compatible request patterns can usually be reused after changing the base URL, credential, and model value.

03

Review Pricing

Before scaling usage, review the configured HY3 prices: $0.0880 input, $0.3530 output, $0.0220 cache read, and $0 cache write per 1M tokens. Compare these rows with prompt size and output length.

04

Compare Benchmarks

Collect public hy3 preview, official release, and tencent hy3 benchmarks as background research. Then run the same prompts through OurToken so quality, latency, token use, and failure behavior are measured in your own workflow.

05

Monitor Results

After testing, review usage logs, failures, latency patterns, and spend inside OurToken. This helps decide whether tencent hy3 api is ready for production traffic or needs more prompt and routing validation.

06

tencent hy3 api FAQ

Answers about Hunyuan Hy3 API access, pricing, hy3 preview, benchmarks, OpenRouter, free access, Hugging Face, and model selection.

01

What is tencent hy3 api?

tencent hy3 api is the OurToken route for calling the hy3 model through a unified chat completions workflow. Developers can copy the model ID, create an API key, run OpenAI-compatible requests, review OurToken pricing, and compare real outputs before deciding whether HY3 fits production traffic.
02

How much does Hunyuan Hy3 API cost on OurToken?

Hunyuan Hy3 API pricing on OurToken is $0.0880 per 1M input tokens and $0.3530 per 1M output tokens. Cache read is $0.0220 per 1M tokens, and cache write is $0 per 1M tokens. Compare those numbers with prompt size, output length, and expected cache-hit volume.
03

How is HY3 different from hy3 preview?

Public Tencent materials describe HY3 as the formal release after hy3 preview, with stronger post-training and improvements for agent, coding, reasoning, and long-context tasks. Treat those provider claims as research context, then test the active hy3 model through OurToken using prompts close to your real workload.
04

Where should I read tencent hy3 benchmarks?

Tencent hy3 benchmarks may appear in provider model cards, public analysis pages, OpenRouter-style listings, or community comparisons. Use them to choose test categories, but do not treat leaderboard numbers as a production guarantee. For routing decisions, compare HY3 on OurToken against your own acceptance criteria.
05

Is there hy3 free access, hy3 openrouter, or hy3 huggingface support?

Searches for hy3 free, hy3 openrouter, or hy3 huggingface can refer to trials, public model listings, model weights, demos, or third-party routes. OurToken does not assume those offers apply to your account. Use this page for the supported OurToken hy3 route, current pricing, and API workflow.
06

When should I choose the hy3 tencent route?

Choose the hy3 tencent route when you want Tencent Hunyuan access for coding help, agent workflows, long-context evaluation, or cost-sensitive chat completions. Compare HY3 with your baseline models on quality, latency, reliability, and token spend before making it a production default.