Tencent HY Text Generation Global / Hunyuan Translation
Operated by Tencent Cloud International
100M tokens for new accounts; it does not recur.
Models mentioned
hunyuan-translationEquivalent paid value
How this was valued: Upper-bound value of the controlling 100M shared input/output-token package, assigned entirely to the higher-priced output direction at USD 0.7714 per million. Input-only use would be USD 25.71. Partial because one worked example incorrectly describes a 1M package even though the free-resource table says 100M.
Limits and terms
- Free Tokens
- 100,000,000
- Scope
- shared input and output
- Validity Years
- 1
- Recurrence
- No
- 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?
No international HY Text Generation plan-specific disclosure was verified for prompt/output retention, training, human access, or deletion.
- 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.
No provider terms or privacy-policy link is captured in this snapshot. Review the provider’s current legal documents before sending sensitive data.
Eligibility
- Account Required
- Yes
- First Activation Only
- Yes
- Payment Method Required
- false if postpaid not enabled
- Real Name Verification Required
- not documented on international offer page
Primary sources
Before you build with Tencent HY Text Generation Global / Hunyuan Translation
Read the classification narrowly
This record has current first-party evidence for some zero-cost hosted inference. The label 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 region.
Resolve the live model route
This snapshot records 1 model ID. Match the exact ID against the provider's live catalog before using it in code; zero-price routes and aliases can rotate while an older documentation page remains online. No stable base endpoint is published in this record, so use the linked provider documentation to identify the current request URL and protocol.
Confirm account and billing boundaries
An account is required, so public catalog evidence cannot by itself prove the limits, balance, or billing behavior attached to your workspace. The reviewed evidence explicitly says no payment card is required. Re-check the signup flow because eligibility and billing controls can change after the snapshot. The equivalent paid value shown here prices a documented allowance where possible; it is not cash, guaranteed savings, or protection from overage.
Re-read the prompt policy for your plan
This record classifies the reviewed handling as “Partially private”: No international HY Text Generation plan-specific disclosure was verified for prompt/output retention, training, human access, or deletion. Provider policies can distinguish free, paid, enterprise, opted-in, and feature-specific traffic, so verify the governing terms for the exact account and route that will receive your data.
Follow the evidence, then re-check it
The record links 4 first-party sources covering the offer, catalog, limits, pricing, terms, privacy, or adoption evidence available to the audit. Prefer the newest governing document or live catalog when sources disagree, and submit a correction when a provider changes a material term.
Match the quota to the workload shape
Translate the published allowance into the traffic pattern you actually expect instead of comparing headline totals alone. A daily token pool can look generous while a low requests-per-minute or concurrency ceiling blocks interactive bursts; a high request limit can still fail a long-context job when input, output, or per-request tokens are capped. Separate prompt tokens from generated tokens, include retries and tool calls, and test the largest realistic payload. If the provider documents more than one limit window, the tightest window at your peak load is the practical ceiling. Research, experimental, and community access can also carry eligibility or fair-use constraints that cannot be modeled as a simple number.
Plan fallback without changing the rules
A fallback should preserve more than API syntax. Confirm that the substitute route supports the required modality, context length, streaming behavior, structured output, tools, and safety controls, then compare its prompt-retention and training terms. An OpenAI-compatible request shape does not make providers operationally or contractually equivalent. Decide which errors may trigger a retry, cap retry storms, and prevent an exhausted free route from silently switching to a billable model. If deterministic output matters, record the model revision and sampling settings; rotating aliases and free-model pools can change behavior even when the endpoint remains available.
Monitor the offer as a dependency
Capture the model ID, response model field, rate-limit headers, usage fields, latency, HTTP status, and any provider request identifier for each test. Watch for authorization failures, quota exhaustion, catalog removal, policy revisions, and dashboard balance changes as separate failure modes. Re-check the provider’s live catalog and governing pages on a schedule proportionate to the workload’s importance, and keep the dated sources that supported your decision. Free capacity is especially suitable for prototypes, evaluations, fallbacks, and bounded workloads when the application can tolerate change; a production dependency still needs observability, an exit path, and an owner responsible for re-verification.
Test one complete request before scaling
Start with the smallest permitted request using the exact credential, model ID, endpoint, and account type you intend to deploy. Record the HTTP status, response headers, usage fields, latency, and any dashboard balance change. Then exercise the failure path: an invalid model, an exhausted quota, or a rate-limit response should fail clearly without silently switching to a paid route. If the provider supports streaming or tool calls, validate those features separately because a free model can expose a narrower capability set than its paid counterpart. Keep a budget ceiling outside the application whenever billing is possible, and avoid sending sensitive data until the observed route matches the reviewed data agreement.