Kwaivgi Kling V3.0 Std Text To Video (Channel Edition)

This is the text-to-video node you'll probably reach for first in BizyAirPlus's Kling lineup: the Standard tier, which is Kling V3.0's quality-per-credit sweet spot. Pro is flashier, but for iterating on ideas, previsualizing shots, or generating b-roll, Std gets you 80% of the quality for a fraction of the cost - and since every request here is metered, that math is the whole game.

What it is

Like every BizyTRD_Kling_* node, this is a cloud call through BizyAirPlus rather than a local model. Kling is Kuaishou's closed video model, so "running it" means renting it. The display name tags this one "Channel Edition," meaning BizyAir's own channel to Kling - you don't need a Kling account, just a BizyAir API key from bizyair.ai. You write a prompt, it comes back with a video, and nothing heavier than an HTTP request ever touches your GPU.

How it works

Text-to-video with Kling V3.0 Std is exactly the pipeline you'd expect: the cloud encodes your prompt, the model samples a sequence of frames, and - because V3 generates native audio - you get a clip with sound, not silent footage you'll have to fake-sync later. You don't get sampler knobs, schedulers, or CFG sliders. The remote generation is a black box with a bill. What you do control is the prompt, the duration, the aspect ratio, and the seed.

Inputs that matter

• prompt - the entire creative input. Write action and camera over time ("slow push-in, rain on the window, neon reflections"). Kling is a strong prompt-follower; reward it with specifics.
• duration - 3–15 seconds, default 5. Std holds quality at moderate lengths fine; push to 15 and motion can soften.
• aspect_ratio - default 16:9; pick portrait for vertical social cuts.
• seed - -1 is random; set a fixed value to make a take reproducible.
• sound - default on; flip it off when you're going to score the video yourself.

api_config overrides the endpoint and key per request; skip_error turns failures into placeholders so one dead request doesn't abort a long queue.

Outputs

video goes to your SaveVideo or preview. request_id is the cloud job's ID for support/billing queries. urls is a string of direct links to the rendered files - grab the MP4 straight from there if you want it outside the graph.

Installing

Via ComfyUI Manager (search "BizyAirPlus") or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/siliconflow/BizyAirPlus.git
cd BizyAirPlus
python -m pip install -r requirements.txt

Restart ComfyUI, click the BizyAirPlus button to turn it ON, and enter your API key when prompted. It's stored in ~/.BizyAirPlus/apikey.ini or read from BIZYAIR_API_KEY. No model downloads, ever - the pack pulls bizyair-cloudberry and bizytrd from PyPI at startup.

Where people get burned

Cost discipline. These are credit-metered cloud calls and the community is vocal about it - Kling's newer tiers can run over a dollar for a few seconds at 1080p, and Std is where you go to not do that. Keep duration short while you iterate, lock seeds when you find a take, and remember sound costs render time even when you don't want audio. If a job just dies, check the key first, then the console - it's almost always credentials or the network, not your graph.