Client

Every generation node in the KLingAI-API pack - image, video, try-on, effects, lip-sync - has a required client input, and this node is the only thing that produces it. Nothing else in the pack works without one Client node sitting somewhere upstream. It's not generative itself; think of it as the authentication and connection object, closer to a database connection or an API session than a creative tool.

How it works

KLing AI is Kuaishou's cloud image/video service - the AI arm of the company behind the Kwai short-video app, and (per the community's own accounting of the closed-model landscape) squarely in the same "closed, hosted, pay-per-call" category as ByteDance's Seedream and Seedance, just from a different Chinese platform. None of this pack's nodes run locally: they all place a job on KLing's servers and poll for the result. Client is what makes that possible - it takes your credentials, opens the connection, and every downstream node borrows it to make its own authenticated request.

It's also genuinely worth knowing this isn't free to use. One image-to-video user on Reddit, describing a pet-video project built on KLing's API, put the cost at "around $0.50 per call" before switching to open alternatives - so treat every node downstream of Client as something that bills your KLing account per run, not a local, sunk-cost GPU render.

The inputs and outputs that matter

All four fields are required - there's no optional section on this node:

• access_key and secret_key - your KLing AI API credentials, issued from KLing's developer console. Get them before you build anything else; nothing downstream will run without a valid pair.
• poll_interval (default 1) - how often, in seconds, the node checks back with KLing's servers while a job is running. Video jobs especially can take a while server-side; this doesn't speed that up, it just controls how chatty the polling is.
• area - global or china. KLing splits accounts by region, and a key issued for one won't authenticate against the other endpoint - this has to match wherever your account was actually registered.

The output is client, typed KLING_AI_API_CLIENT - wire it into the client input on any generation node in the pack.

Installing it

Comes with the rest of the pack. ComfyUI Manager: search ComfyUI-KLingAI-API, install, restart. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/KwaiVGI/ComfyUI-KLingAI-API
cd ComfyUI-KLingAI-API && pip install -r requirements.txt

The README has a genuinely useful tip here: if you don't want your key sitting in plain text in a workflow JSON you might share or upload somewhere, put it into the pack's config.ini file instead and leave access_key/secret_key blank on the node itself.

Common issues

Almost every failure anywhere in this pack traces back here. Wrong or expired credentials fail every downstream node at once, not just this one. A region mismatch on area is the sneakier version of the same problem - the key works, the node runs, and it still fails, because you registered against the wrong regional endpoint. And since every call downstream costs real money against your KLing account, it's worth confirming your account actually has balance before debugging a workflow that "isn't producing anything" - an empty wallet looks a lot like a broken connection from inside ComfyUI.