KLing Models

2 models

Usage

Last 19 days · 2026-10-23 to 2026-11-21

Tokens

34.6M

Requests

102

Models in use

2 of 2

Tokens per day, stacked by model

010.4M20.7M10-2311-0711-172026-10-23 — 0 tokens2026-10-27 — 0 tokens2026-10-30 — 0 tokens2026-10-31 — 0 tokens2026-11-02 — 0 tokens2026-11-05 — 0 tokens2026-11-06 — 0 tokens2026-11-07 — 3,380,000 tokens kling-v3-omni: 3,380,0002026-11-10 — 0 tokens2026-11-12 — 20,704,970 tokens kling-v3-omni: 18,592,470 kling-video-o1: 2,112,5002026-11-13 — 0 tokens2026-11-14 — 0 tokens2026-11-15 — 1,056,250 tokens kling-video-o1: 1,056,2502026-11-16 — 0 tokens2026-11-17 — 2,112,500 tokens kling-v3-omni: 2,112,5002026-11-18 — 3,168,750 tokens kling-v3-omni: 3,168,7502026-11-19 — 4,225,000 tokens kling-v3-omni: 4,225,0002026-11-20 — 0 tokens2026-11-21 — 0 tokens
  • kling-v3-omni
  • kling-video-o1

Which models that traffic went to

  1. Kling V3 Omni90.9%31.5M
  2. Kling Video O19.1%3.2M

Share of 34.6M tokens.

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 19 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, video, returns video.from $0.0845 / s
kling-video-o1Takes text, vision, video, returns video.from $0.0845 / s

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

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, 984 models across 49 model authors.