FIELD GUIDE / TENCENT CLOUD / KLING

Kling Video API on Tencent TokenHub Versus Kling Website Credits: Two Incompatible Price Ledgers

A Kling logo appears in both web-generation products and partner API catalogs, but their usage units and merchant relationships can be different. Tencent’s TokenHub lists model-specific token-per-second prices; those cannot be treated.

A Kling logo appears in both web-generation products and partner API catalogs, but their usage units and merchant relationships can be different. Tencent’s TokenHub lists model-specific token-per-second prices; those cannot be treated as Kling’s own Standard or Pro website membership credits.

Verification scope: Official sources were checked for the 25 October 2026 cutoff. List tariffs and rights apply only to the documented provider, region, tier, exact model and sales channel. This is an editorial draft, not a verified account quote; unknown effective dates remain null.

What Tencent actually sells

Tencent Cloud’s TokenHub price page, updated October 24, 2026, publishes Kling-Video-V3 media rates under Tencent’s regional model catalog. In its listed video-meter example, 1080p without audio consumes 80,000 model tokens per generated second, with a CNY 10 per million-token tariff, equivalent to CNY 0.8 per second. An illustrative five-second completion therefore costs CNY 4 at that listed meter before taxes or other charges. The provider identifies different rates for audio, resolution, reference input and video generation versions, so this example is not a universal Kling “per clip” price.

The native website membership is a different contract

The direct Kling website did not provide a reliably accessible official Standard/Pro regional checkout record in this research pass. Its monthly fee, native credits, free plan grants and rollover rules consequently remain unknown—not zero. No currency conversion converts Tencent API tokens into Kling website credits without a first-party bridge. Purchasing a website membership is not evidence of an included Tencent developer API wallet, just as a Tencent token allocation does not necessarily fund generations on Kling’s own interface.

Make output specifications part of the rate key

Before accepting an API price, retain the exact partner route, model suffix, sound setting, resolution, reference video usage and billed seconds. The first-party schedule identifies Kling-Video-V3, V3-turbo, V3-omni and other variants. A model with sound or motion control can consume different tokens per second from a silent version. If a project requests six-second scenes and only half are accepted, expected accepted-footage cost differs from the raw generated-seconds price. Any assumed rejection rate in a planning example must be explicitly hypothetical or measured in the project.

A credible side-by-side decision

For web workflow evaluation, ask whether members can reuse characters, control references, export at a required resolution and retain permitted commercial rights; obtain the actual checkout terms. For Tencent API integration, verify CNY billing, API access, rate limits and accounting for retries and failed render jobs. Then compare both routes on one deliverable: accepted edited seconds at required resolution, soundtrack, revision count and publication permissions. Avoid presenting Tencent API pricing as a coupon for a native Standard or Pro subscription.

What remains in review

The original WAI-AI10-C0060 inventory entry for Kling direct website credit costs remains review because its exact plan quotas and prices are not verified. This distinct partner-channel article is publishable editorially as a metering explanation with a grounded Tencent rate. A later native plan snapshot should be additive, with its own first-party URL, region and timestamp; it must not overwrite this API evidence or quietly change the channel field.

Decision checklist and limitations

Before purchase or deployment, retain the literal model or plan identifier, payer/merchant, country or cloud region, billing currency, exact usage meter, source URL, checked date, effective date if explicitly supported, and any plan commitment or promotional eligibility. Recalculate from the companion price and quota snapshots rather than assuming that a remembered list tariff will remain unchanged. A credit allowance, maximum input length, published token rate and confirmed billed currency answer different questions; never add them as if they were the same quantity.

When comparing another provider or route, use the same input/output distribution and acceptable result definition. Include unsuccessful attempts, optional tools, storage, tax, payment and human review only when those components are actually measured or supported by an explicit source. Vendor marketing and documentation are not independent product tests. This article makes no claim to have personally tested paid endpoints, purchased plans, or checked account-specific taxes or availability.

Sources & Further Reading

CONTINUE EXPLORINGExplore related files ↗