KLing Models

2 modelsGeneral models from $2.00/M input

Usage

Last 7 days · 2026-08-05 to 2026-08-11

Tokens

111M

Requests

81

Models in use

2 of 2

Tokens per day

044M88M08-052026-08-05 — 13,736,000 tokens2026-08-06 — 0 tokens2026-08-07 — 3,168,750 tokens2026-08-08 — 1,056,250 tokens2026-08-09 — 88,016,750 tokens2026-08-10 — 5,281,250 tokens2026-08-11 — 0 tokens

Which models that traffic went to

  1. kling-v3-omni100.0%111M

Share of 111M tokens. 1 models with traffic report no token counts and cannot be ranked here, including kling-video-o1 — they are in the request view.

The two views disagree on purpose: a model can take a large share of the calls and a small share of the tokens — many short requests — or the reverse. Which one matters depends on whether your cost is driven by call volume or by prompt length. Measured on AIHubMix over the last 7 days, counting the 2 model IDs listed on this page; traffic routed through upstream-specific IDs that are not in the public catalog is not included.

All 2 KLing Models

Open in model list
KLing models on AIHubMix with input and output modalities, context length, maximum output, price per million tokens including cache read and cache write rates, and measured throughput and latency.
Modalities
kling-v3-omniTakes text, vision, returns video.$2.00$2.00/M
kling-video-o1Takes text, vision, returns video.$2.00$2.00/M

Prices are USD per million tokens; cache read and cache write are the rates for prompt-cache hits and for writing a prompt into the cache. Throughput and latency are measured on AIHubMix — the same figures the model detail page shows — not vendor claims. A dash means the catalog does not publish that field for that model, which is not the same as the model not supporting it.

KLing on AIHubMix

Which KLing model should I start with?

kling-v3-omni at $2.00/M input — the cheapest entry here that declares a token price. Move up to kling-video-o1 when answer quality matters more than cost.

Why are there several entries for the same model?

Because each row is a route you can call, not a model release. Some IDs name an upstream (azure-, alicloud-, cc-), and some differ only in capitalisation, kept so older integrations keep working.

The catalog does not carry a field saying which of those a given row is, so this page does not sort them into buckets it would have to invent. Every row shows that route’s own price, context and speed — compare those directly, and open a model to see the upstreams that serve it.

Do I need a separate KLing account?

No. One AIHubMix key covers every model on this page, and switching between them is a change to the model string — billing, rate limits, and logs stay in one place.

Start calling KLing in one line

One key, one endpoint, 844 models across 35 providers.