--- title: "Tencent Hunyuan free inference" description: "1M tokens for new accounts; it does not recur. See verified limits, model IDs, privacy terms, and primary sources for Tencent Hunyuan." canonical_url: "https://freeinferencing.com/provider/tencent_hunyuan/" md_url: "https://freeinferencing.com/provider/tencent_hunyuan.md" last_updated: "2026-09-19" --- # Tencent Hunyuan > 1M tokens for new accounts; it does not recur. ## Classification - **Directory:** Current - **Free access:** One-time trial - **Status:** Current trial - **Confidence:** High - **Payment card:** No - **Account:** Required - **Equivalent paid value:** Up to CN¥10.30 once - **API endpoint:** `https://api.hunyuan.cloud.tencent.com/v1` ## Models mentioned - `Hunyuan-a13b` - `Hunyuan-role-latest` - `Hunyuan-translation` - `Hunyuan-translation-lite` - `Tencent-HY-Vision-1.5-Instruct` - `Hunyuan-turbos-vision` - `Hunyuan-t1-vision` - `Hunyuan-turbos-vision-video` - `Hunyuan-embedding` ## Limits and terms ```yaml activation_tokens: 1000000 separate_embedding_tokens: 1000000 expires_after_years: 1 recurrence: false default_concurrency: 5 exhausted_behavior: Does not auto-switch to paid unless postpaid is explicitly enabled. ``` ## What happens to your prompts? **Partially private.** Hunyuan free-tier retention, training, improvement, and operator-access commitments were not verified. 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 Hunyuan API under Tencent Cloud account, privacy, and product agreements; policy location varies by region/language. prompt_retention: No service-specific free-tier prompt retention duration was verified from the reviewed Hunyuan documentation. response_retention: not_documented ordinary_logging: Tencent Cloud collects account, security, billing, and usage records; inference-content logging was not clearly documented. model_training: No current Hunyuan API commitment excluding free-tier inputs or outputs from training was verified. product_improvement: General cloud/service improvement uses may apply; content scope is not clear enough to characterize. human_or_operator_access: not_documented subprocessors_and_routing: Tencent Cloud and its service providers process requests in selected regions; model/product terms can differ. deletion_controls: General account and privacy controls exist, but no API-request deletion or TTL was found. caveat: The product documentation establishes API use and quota, not a complete inference-data contract; obtain the applicable regional Tencent Cloud agreement before sensitive use. ``` ## Eligibility ```yaml account_required: true real_name_verification_required: true payment_method_required: false_if_postpaid_not_enabled ``` ## API compatibility and modalities - **Compatibility:** OpenAI Compatible - **Modalities:** Embeddings, Image / vision, Video - **Geography:** China ## Before you build with Tencent Hunyuan ### 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, High confidence, No payment-card status, and the plan-specific sources below. ### Resolve the live model route The snapshot records 9 model IDs. 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 Hunyuan free-tier retention, training, improvement, and operator-access commitments were not verified. 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 6 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 - [Free resource package](https://cloud.tencent.com/document/product/1729/97731): Official Docs - [API access](https://cloud.tencent.com/document/product/1729/111007): Official Docs - [Migration and current aliases](https://cloud.tencent.com/document/product/1729/131925): Official Docs - [Tencent organization on Hugging Face (Hunyuan first-party model family)](https://huggingface.co/tencent): Official Repository - [tencent/Hunyuan3D-2 model card with all-time download count](https://huggingface.co/tencent/Hunyuan3D-2): Official Repository - [Tencent Hunyuan product overview on Tencent Cloud](https://cloud.tencent.com/document/product/1729/104753): Official Docs ## Sitemap See the full [semantic sitemap](/sitemap.md) for every page and markdown mirror.