Kling Omni¶

Overview¶

Kling Omni, stored under kling-video-o1, is the broadest Kling variant. It adds video-to-video style and multimodal reference use cases on top of the usual text and image entry points. Kling’s official developer materials present the platform as a next-generation creative API for image and video generation with support for models, callbacks, polling, and motion-oriented controls. For portal readers, the useful mental model is that Kling billing in this codebase is parameter-driven: duration, mode, input type, and model tier all matter.

API base URL¶

https://api-singapore.klingai.com

Example payload¶

{
  "model_name": "kling-video-o1",
  "prompt": "Transform the source clip into a glossy ad-style reveal",
  "aspect_ratio": "16:9",
  "duration": 8,
  "cfg_scale": 0.5,
  "mode": "pro",
  "image": "https://example.com/reference-1.jpg",
  "video": "https://example.com/source.mp4"
}

Our Current Pricing¶

Kling video billing is parameter-based. The activity does not wait for a provider usage record; instead it computes cost from duration, mode, resolution, input type, and model multiplier.

Base price per second:

std -> 0.05 USD/sec
pro -> 0.12 USD/sec

Resolution multipliers:

480p -> 0.8
720p -> 1.0
1080p -> 1.5
4k -> 2.5

Input multipliers:

text        -> 1.00
image       -> 1.00
multi-image -> 1.15
video       -> 1.25
chisel      -> 1.10

Model multipliers:

kling-v2-5-turbo -> 1.0
kling-v1-6       -> treated operationally like the standard Kling family unless you override it in your own rate card
kling-v2-6       -> 1.0
kling-v3         -> 1.3
kling-video-o1   -> 1.8
unknown          -> 1.0

Implemented formula:

raw_cost =
  ceil(duration_seconds) *
  base_price_per_second(mode) *
  resolution_multiplier(resolution) *
  input_multiplier(input_type) *
  model_multiplier(model)

final_cost_usd = clamp(round(raw_cost, 2), 0.01, 10.00)

A small but important implementation detail is that the current activity path passes 720p into the cost function, so even if the external model can conceptually produce higher output, the repo’s current internal cost path charges as though the request is in the 720p tier unless that code is changed.

To calculate cost safely, derive input_type from the request envelope you persist. A payload with no references is text; one reference frame is usually image; multiple stills become multi-image; source-video driven jobs become video. Then compute the bill line from the normalized request rather than from the polling result. That gives you stable billing even when the provider returns only task status.

Vendor Pricing¶

Credits are purchased in packages, and different discounts may be applied. The following rates are based on Standard listed prices (no discounts).

Mode	Input Type	Credit Points (per 1s)	Price per second (USD)
Standard	With video input	0.9	$0.126
Standard	Without video input	0.6	$0.084
Pro	With video input	1.2	$0.168
Pro	Without video input	0.8	$0.112

Actually the Kling Omni request from app for 10s video results in Pro mode usage and 8 credit points deduced.