--- title: "Tencent HY Text Generation Global / Hunyuan Translation free inference" description: "100M tokens for new accounts; it does not recur. See verified limits, model IDs, privacy terms, and primary sources for Tencent HY Text Generation Global / Hunyuan Translation." canonical_url: "https://freeinferencing.com/provider/tencent_hunyuan_global_translation/" md_url: "https://freeinferencing.com/provider/tencent_hunyuan_global_translation.md" last_updated: "2026-09-19" --- # Tencent HY Text Generation Global / Hunyuan Translation > 100M tokens for new accounts; it does not recur. ## Classification - **Directory:** Current - **Free access:** One-time trial - **Status:** Current trial - **Confidence:** Medium High - **Payment card:** No - **Account:** Required - **Equivalent paid value:** Up to $77.14 once ## Models mentioned - `hunyuan-translation` ## Limits and terms ```yaml free_tokens: 100000000 scope: shared_input_and_output validity_years: 1 recurrence: false requests_per_second: 20 default_concurrency: 5 exhausted_behavior: billing_exception_unless_postpaid_enabled caveat: The controlling table grants 100M tokens, while one calculation example incorrectly refers to a 1M package; the conflict is preserved. ``` ## What happens to your prompts? **Partially private.** No international HY Text Generation plan-specific disclosure was verified for prompt/output retention, training, human access, or deletion. Privacy is audited separately from price. Review the current governing terms before sending sensitive or regulated data. ## Data governance and agreements ```yaml data_governance: review_status: partial plan_scope: Tencent Cloud International HY Text Generation Global ChatTranslations free-resource package. prompt_retention: No plan-specific international prompt-retention duration was found in the billing or API documentation. response_retention: not_documented ordinary_logging: Tencent Cloud necessarily records signed-request, account, usage, security, quota, and billing metadata; content-versus-metadata boundaries and retention are not published on the offer pages. model_training: No international ChatTranslations plan-specific no-training commitment was verified. product_improvement: not_documented human_or_operator_access: not_documented subprocessors_and_routing: Tencent Cloud International processes the signed request in its selected service region; the offer pages do not enumerate all processing parties. deletion_controls: General account and privacy mechanisms may apply, but no inference-specific content deletion or TTL is documented. caveat: Do not inherit the separate mainland-China Hunyuan plan's legal assumptions. Obtain the governing international cloud agreement before sending sensitive text. ``` ## Eligibility ```yaml account_required: true first_activation_only: true payment_method_required: false_if_postpaid_not_enabled real_name_verification_required: not_documented_on_international_offer_page ``` ## API compatibility and modalities - **Compatibility:** TencentCloud API 3 SDK Or HTTP With SSE - **Modalities:** Text generation - **Geography:** International Tencent Cloud Service ## Before you build with Tencent HY Text Generation Global / Hunyuan Translation ### Read the classification narrowly This record describes the bounded offer supported by evidence on 2026-09-19; it does not guarantee permanence, production suitability, uptime, latency, model quality, or access from every account and region. “One-time trial” should be interpreted together with the Current directory placement, Medium High confidence, No payment-card status, and the plan-specific sources below. ### Resolve the live model route The snapshot records 1 model ID. Match the exact ID against the provider's current catalog before using it in code because zero-price routes, aliases, context limits, and feature support can rotate while an older documentation page remains online. ### Match the quota to the workload shape Translate the allowance into peak requests per minute, input and output tokens, concurrency, retries, and every daily or monthly ceiling that applies to the intended account. The first limit reached by the workload is the practical ceiling. A large token pool can still fail interactive bursts, and a high request limit can still fail long-context work. Include tool calls and retry traffic, test the largest realistic payload, and treat research, experimental, and community access as conditional on their eligibility and fair-use terms. ### Preserve billing and privacy boundaries The recorded payment-card requirement is No, and account access is required. Confirm both in the live signup flow, set provider-side budgets when charges are possible, and observe the balance or usage fields after a complete request. The prompt-handling classification is **Partially private** because No international HY Text Generation plan-specific disclosure was verified for prompt/output retention, training, human access, or deletion. Re-read the terms for the exact route and plan before sending sensitive, regulated, or proprietary content. ### Follow the evidence, then re-check it This record links 4 first-party sources covering the offer, catalog, limits, pricing, terms, privacy, or adoption evidence available to the audit. Prefer the newest and most specific governing document or live catalog when sources disagree. A dated finding can become stale even when the page remains online, so retain the source and snapshot that supported the decision and submit a correction when a provider changes a material term. ### Plan fallback without policy drift A fallback should preserve modality, context length, streaming, structured output, tools, safety controls, and data terms, not only API syntax. Decide which errors may retry, cap retry storms, and prevent an exhausted free route from silently switching to a billable model. Rotating aliases and free pools can change behavior without changing the endpoint, so retain the response model field and test at least one substitute route before the primary offer becomes unavailable. ### Monitor the offer as a dependency Capture the model ID, response model, rate-limit headers, usage fields, latency, HTTP status, and provider request identifier. Watch authorization failure, quota exhaustion, catalog removal, policy revision, and balance movement as separate failure modes. Re-check the live catalog and governing sources on a schedule proportionate to the workload's importance, and keep an owner and exit path for any production dependency on volatile free capacity. ### Test one complete request before scaling Start with the smallest permitted request using the exact credential, model ID, endpoint, region, and account type intended for deployment. Record the status, headers, usage fields, response model, latency, and dashboard balance movement. Then exercise an invalid model, quota exhaustion, or rate limit so failure is explicit and cannot silently switch to a paid route. Validate streaming, structured output, and tool calls separately because a free model can expose fewer features than its paid counterpart. Keep a budget ceiling outside the application whenever billing is possible, and do not send sensitive data until the observed route matches the reviewed agreement. ## Primary sources - [Billing and free resource package](https://intl.cloud.tencent.com/pt/document/product/1284/77186): Official Pricing - [ChatTranslations API](https://intl.cloud.tencent.com/jp/document/product/1284/77188): Official API Docs - [HY Text Generation Global](https://intl.cloud.tencent.com/pt/document/product/1284/75531): Official Docs - [Tencent organization on Hugging Face](https://huggingface.co/tencent): Official Repository ## Sitemap See the full [semantic sitemap](/sitemap.md) for every page and markdown mirror.