☁️BizyAir Load Checkpoint

This is the node everyone's BizyAir graph starts from, and it looks almost exactly like ComfyUI's stock "Load Checkpoint" - pick a model, get back a model, a CLIP, and a VAE. The difference is where the checkpoint actually lives. A normal Load Checkpoint node reads a multi-gigabyte .safetensors file off your disk. This one doesn't touch your disk at all: ckpt_name is a dropdown populated from SiliconFlow's BizyAir cloud catalog, and when you run the graph, the model runs on their servers, not your GPU. That's the entire premise of the pack - "run ComfyUI anywhere, without worrying about hardware" - and this loader is where that promise starts.

What you're actually picking. BizyAir's catalog spans the usual suspects and then some: SD 1.5, SDXL, SD 3.5, Flux, Kolors, CogView4, and whatever else SiliconFlow has onboarded, going by their changelog (they add new base models to the catalog on a near-weekly cadence). You never download any of it - you just pick a name and the cloud does the rest. There's also a model_version_id text field, which is for a narrower case: if you've uploaded or been shared a custom model through BizyAir's model-hosting feature (their own LoRA/checkpoint sharing system, separate from the built-in catalog), you paste its version ID here instead of picking from the dropdown. Leave it blank to just use ckpt_name.

Outputs: model, clip, and vae, typed BIZYAIR_MODEL, BIZYAIR_CLIP, BIZYAIR_VAE - deliberately not the plain MODEL/CLIP/VAE that ComfyUI's stock loader emits. This is the load-bearing detail for the whole pack: because the types are namespaced, ComfyUI's graph validator won't let you cross-wire a BizyAir output into a stock node's input, or vice versa. Once you start a chain here, everything downstream - your conditioning nodes, your sampler, your guider - has to be a BizyAir node too, all the way to wherever you finally decode back to a plain IMAGE. Think of it less as "a checkpoint loader" and more as "the door into an entirely separate, cloud-hosted sub-graph" that happens to live inside your local ComfyUI canvas.

Installing it: the whole pack comes as one unit - search "BizyAir" in ComfyUI Manager and install, or git clone https://github.com/siliconflow/BizyAir.git into custom_nodes and restart, or comfy node install bizyair via the Comfy CLI. There's no separate download step for this specific node. What does need a separate step is authentication: the README is blunt about it - "make sure to set your API KEY for the first time use." Click through the node's login prompt, register a BizyAir account, and set your key before you try to run anything. Without it, this loader (and every node downstream of it) just fails.

Common trip-ups. If this loader's dropdown shows nothing to pick, or errors out, check your API key first - an unauthenticated session can't fetch the catalog. If you inherited a workflow that has this node in it and you don't remember installing BizyAir yourself, you're not imagining things: older versions of ComfyUI Manager occasionally auto-installed BizyAir when a workflow referenced a missing node it guessed belonged to the pack, which understandably spooked people who didn't know what it was. It's a legitimate commercial node pack from SiliconFlow, not malware - but if you don't want a cloud dependency sitting in your graph, it's safe to uninstall from Manager. And remember the type-boundary rule above: swap this in for a stock checkpoint loader mid-workflow and you'll get disconnected wires, not a working hybrid graph.