Practical overview
When it fits
Use it when you have ComfyUI installed and want supported provider calls in your workflows to use your own API credentials instead of a proxy credit system.
Who it is for
- ComfyUI users who want to connect image-generation workflows to supported vendor APIs with their own credentials.
- Developers who want to manage API keys through ComfyUI's interface, a configuration file, or pass.
Documented uses
- Route supported ComfyUI requests directly to a provider using a personal API key.
- Configure provider credentials through the ComfyUI interface, a JSON file, or pass-managed paths.
- Use Tencent Hunyuan 3D credentials in the formats specified for its signed request flow.
Requirements & limits
The project is an open-source repository under the MIT license. The README says no ComfyUI or Comfy.org account is needed for the extension's direct API use; vendor credentials are still required.
- It is a ComfyUI custom node, so it extends an existing ComfyUI setup rather than serving as a standalone generator.
- Provider availability depends on the extension's supported providers and the user's vendor credentials.
- Credential handling options include local values, pass paths, and a JSON configuration file.
- The README describes local asset storage rather than uploads to intermediary servers.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install the custom node and configure provider keys
Add ComfyUI API Liberation to an existing ComfyUI installation and enter provider credentials through its interface.
Before you start
- An existing ComfyUI installation
- API credentials for the provider you plan to configure
Steps
From the ComfyUI custom_nodes directory, clone https://github.com/holo-q/comfy-api-liberation.git.
Restart ComfyUI.
Select API Keys in the toolbar and enter the provider keys.
Expected outcome
The extension is installed and the configured provider credentials are available to its supported direct API routing.
Guide limitations
- The guide documents installation and credential setup, not a specific workflow or generation procedure.
- Provider credentials and access are managed by the respective vendors.
Configure credentials with pass
Keep provider secrets in the pass password store and configure the extension with their paths.
Before you start
- ComfyUI with the extension installed
- The pass password manager
- Provider credentials
Steps
Add credentials to pass, for example with
pass insert ai/openai.In ComfyUI's API Keys interface, switch the relevant provider row from key to pass.
Enter the matching path, such as
ai/openai.
Expected outcome
The extension stores the pass path and resolves the secret at request time with `pass show `.
Guide limitations
- The password store must contain the referenced secret.
- This guide covers credential configuration rather than running a ComfyUI workflow.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 16 October 2026
- Original website title
- holo-q/comfy-api-liberation · Official homepage title · retained in its source language

