☁️BizyAir Switch Server Endpoint

What it is

This is a plumbing node, not a creative one - it points every other BizyAir node in your workflow at a different backend URL. Most people using this pack will never need to touch it; the default endpoint just works. It exists for the cases where it doesn't: BizyAir support asking you to switch endpoints while debugging an issue, a regional routing problem, or testing against a staging environment before a production run.

How it works

Drop it in your workflow and pick an endpoint from the dropdown; from that point forward, requests from BizyAir's cloud nodes route to whichever server you selected instead of the default. It doesn't process any data itself - it has no image, text, or model inputs, and it produces no outputs. Its entire job is a side effect: changing where the rest of your BizyAir nodes send their API calls.

Inputs and outputs that matter

There's exactly one input, endpoint, a two-way choice between BizyAir's staging server (https://bizyair-api-st.siliconflow.cn/x/v1) and its production server (https://bizyair-api.siliconflow.cn/x/v1). That's it - no image, model, or text sockets, because this node isn't part of your generation pipeline at all, it's configuring the pipeline around it.

There are no outputs. The node is marked as an output node in the technical sense - meaning it's allowed to be a dead end in the graph with nothing wired downstream of it - but that's a structural detail, not a signal that it produces meaningful data. Its effect is entirely in what it does to the environment other nodes execute in, not in anything you'd connect a wire to.

Installing it

Install through ComfyUI Manager (search "BizyAir") or git clone https://github.com/siliconflow/BizyAir.git into custom_nodes, then restart. You'll still need a BizyAir API key set up before anything in this pack - including whichever endpoint you point it at - actually works.

Common issues

If your BizyAir nodes suddenly stop authenticating or start failing after you've dropped this node into a workflow, check whether it's accidentally set to the staging endpoint (bizyair-api-st) - that's meant for testing, not day-to-day generation, and your production API key and account state may not apply there the same way. If you don't remember adding this node at all and things have started behaving oddly, it's worth searching your graph for it specifically - a stray copy left over from troubleshooting or a downloaded workflow is an easy thing to miss, since it produces no visible output and can sit quietly changing where every other BizyAir node in the graph talks to. For normal use, the simplest fix for most people is just not including this node at all and letting BizyAir's default endpoint handle things.