Provider: FreedomGPT

Here's a number worth having before you install anything: across the entire r/StableDiffusion + r/comfyui + r/civitai corpus, "FreedomGPT" appears in exactly one thread. This pack's own name appears in zero. So if you found this page, you're probably already someone who has a FreedomGPT key in hand and wants it working in ComfyUI, not someone researching an ecosystem trend.

That's fine. FreedomGPT's pitch is the same pitch the local-model crowd makes - a service that doesn't lecture you about your prompt - delivered as an API instead of a download. It sits next to the relay providers in this pack, and the pack's own README says plainly what it's for: use it with the custom-model chat and image nodes. There is no FreedomGPT family node, because there's no curated list of FreedomGPT models to route.

What the node is

Three fields and an output, no model, no generation:

• api_key - empty resolves to freedomgpt in api_key.json, then FREEDOMGPT_API_KEY. Fail both and the run errors with the message telling you so.
• proxy_url - optional, http://127.0.0.1:7890 or socks5://127.0.0.1:1080.
• timeout - seconds; 0 means no limit.

The output is a provider socket, which you wire into Chat (Custom Model) or Image Generation (Custom Model). Notice there's no base_url field here - unlike the OpenAI Compatible and Google GenAI Compatible providers, this one's endpoint is fixed (chat.freedomgpt.com/api/v1). It's a first-party integration, not a general relay.

Mechanically the pack treats it as its own protocol for both text and images, so the custom-model nodes accept it for both tasks. That's the pack's way of saying: we know this endpoint's shape, we just don't want to maintain a model list for it. Which is honest, and means a brand-new model on their side works the day they ship it, with no pack update.

Install

cd ComfyUI/custom_nodes
git clone https://github.com/yogurt7771/ComfyUI-YogurtNodes
cd ComfyUI-YogurtNodes
pip install -r requirements.txt

Manager works too - search "YogurtNodes" (the display name on the canvas gets a " (Yogurt Nodes)" suffix, so look for "Provider: FreedomGPT (Yogurt Nodes)"). Key file:

{ "freedomgpt": "your-key" }

at custom_nodes/ComfyUI-YogurtNodes/yogurt_nodes/llm/api_key.json. Field beats file beats environment variable, in that order.

Wiring it for real

The custom-model nodes have a default provider - official OpenAI - which is exactly the wrong default to forget about here. Wire the provider socket. If you don't, a text run quietly goes to OpenAI using api_key.json's openai entry, and the worst version of that story is "I tested my local endpoint and got billed."

Two habits worth keeping with a provider this obscure:

Verify the model ID. Nothing in the pack validates it, because it can't. Grab the exact string from the service's docs and paste it into the model_id field; a typo comes back as a server error quoting your string.

Read the error, not the retry. Ten identical failures is not a diagnosis. Leave retry_count at 1 until a call succeeds once.

The honest caveat

Any node whose entire purpose is to carry a credential and phone home is the risky shape of custom node - there's no sandbox, and the one time this category got weaponized in ComfyUI's history was an "LLM" node that stole credentials. That's not a reason to avoid API nodes; it's a reason to install from a pack you can read and to prefer widely used ones. This pack is MIT, open, and readable - but it is also near-invisible in community discussion, so you'll get no crowd-sourced warnings if something changes. That trade is yours to make.

Practically: this is the node you use when you'd rather not send a prompt through the official vendor's filter and the model you want is already available on FreedomGPT's side. If you want the same property without a network hop, a local abliterated 8B behind Ollama does the job for free and offline (the KB's llm-in-comfyui.md makes the case that this is where the local tier earns its keep) - the API route exists for when you want a bigger model than your card can hold.