☁️BizyAir Kling O1 Text To Video

What it is

The plainest of this pack's Kling video nodes: a straight text prompt in, a video out, on Kling's newer O1 tier. No reference frames, no negative prompt, no variant count - just prompt, duration, and aspect ratio. If you want the most direct possible route from an idea to a clip using Kuaishou's model, this is it. The other Kling video nodes in this pack add keyframes, reference images, or editing capability on top of the same underlying model family; this one is the baseline.

Same access model as every other node in this pack's External APIs section: it's a wrapper around Kling's actual closed API, billed through your existing BizyAir account instead of a separate subscription.

The inputs that matter

• prompt - describe the scene and its motion. Since there's no reference image or negative prompt here to help steer the result, the prompt is carrying the entire load - be specific about subject, setting, camera behavior, and pacing.
• duration - 5 or 10 seconds.
• aspect_ratio - 16:9, 9:16, or 1:1.

Outputs: video, and bizyair_model_name, reporting kling-o1 as the resolved backend model for this endpoint.

How to install it

ComfyUI Manager: search "BizyAir," install, restart. Manual clone:

cd ComfyUI/custom_nodes
git clone https://github.com/siliconflow/BizyAir.git

A BizyAir API key is required. Kling has no offline mode whatsoever - this node exists purely to be a thin client for the hosted service.

Common issues

Motion doesn't match what you had in mind. With no reference frame to anchor the result, this node depends entirely on the prompt for both content and motion - if the output drifts from your intent, the fix is almost always a more specific prompt (explicit camera direction, explicit subject action) rather than a settings change, since there aren't many other settings to change.

Wanting more control than this node offers. If you find yourself wishing you could anchor the clip to a specific starting or ending image, that's the O1 image-to-video node elsewhere in this pack's Kling section - it accepts a first frame and optionally a last frame for keyframe interpolation, which this text-only node doesn't support at all.

Cost adds up on repeated generations. Since there's no reference image constraining the output, text-to-video tends to need more iteration to land on a satisfying result than image-anchored generation does - budget for a few tries, and check your account balance before running a long batch.

Job fails with no clear cause. Check your API key and credits first; that covers most opaque failures on this pack's API nodes well before a genuinely malformed prompt does.