API Nodes are ComfyUI’s new way of calling closed-source models through API requests, providing ComfyUI users with access to external state-of-the-art AI models without complex API key setup.

​
What are API Nodes?

API Nodes are a set of special nodes that connect to external API services, allowing you to use closed-source or third-party hosted AI models directly in your ComfyUI workflows. These nodes are designed to seamlessly integrate the capabilities of external models while maintaining the open-source nature of ComfyUI’s core.

Currently supported models include:

  • Black Forest Labs: Flux 1.1[pro] Ultra, Flux .1[pro], Flux .1 Kontext Pro, Flux .1 Kontext Max
  • Google: Veo2, Gemini 2.5 Pro, Gemini 2.5 Flash
  • Ideogram: V3, V2, V1
  • Kling: 2.0, 1.6, 1.5 & Various Effects
  • Luma: Photon, Ray2, Ray1.6
  • MiniMax: Text-to-Video, Image-to-Video
  • OpenAI: o1, o1-pro, o3, gpt-4o, gpt-4.1, gpt-4.1-mini, gpt-4.1-nano, DALL·E 2, DALL·E 3, GPT-Image-1
  • PixVerse: V4 & Effects
  • Pika: 2.2
  • Recraft: V3, V2 & Various Tools
  • Rodin: 3D Generation
  • Stability AI: Stable Image Ultra, Stable Diffusion 3.5 Large, Image Upscale
  • Tripo: v1-4, v2.0, v2.5

​
Prerequisites for Using API Nodes

To use API Nodes, the following requirements must be met:

​
1. ComfyUI Version Requirements

Please update your ComfyUI to the latest version, as we may add more API support in the future, and corresponding nodes will be updated, so please keep your ComfyUI up to date.

Please note the distinction between nightly and release versions. We recommend using the nightly version (which is the latest code commit), as the release version may not be updated in a timely manner. This refers to the development version and the stable version, and since we are still rapidly iterating, this document may not be updated promptly, so please pay attention to the version differences.

​
2. Account and Credits Requirements

You need to be logged into your ComfyUI with a Comfy account and have a credit balance of credits greater than 0.

Log in via Settings -> User:

Go to Settings -> Credits to purchase credits

Please refer to the corresponding documentation for account and credits to ensure this requirement:

  • Comfy account: Find the User section in the settings menu to log in.
  • Credits: After logging in, the settings interface will show a credits menu where you can purchase credits. We use a prepaid system, so there will be no unexpected charges.

​
3. Network Environment Requirements

API access requires that your current requests are based on a secure network environment. The current requirements for API access are as follows:

  • The local network only allows access from 127.0.0.1 or localhost, and you can directly use the login function.
  • If you are accessing from a local area network or a website that is not on the whitelist, please log in with an API Key. Please refer to Log in with an API Key.
  • You should be able to access our API service normally (in some regions, you may need to use a proxy service).
  • Access should be carried out in an https environment to ensure the security of the requests.

Accessing in an insecure context poses significant risks, which may result in the following consequences:

  1. Authentication may be stolen, leading to the leakage of your account information.
  2. Your account may be maliciously used, resulting in financial losses.

Even if we open this restriction in the future, we strongly advise against accessing API services through insecure network requests due to the high risks involved.

​
4. Using the Corresponding Nodes

Add to Workflow: Add the API node to your workflow just like you would with other nodes. Run: Set the parameters and then run the workflow.

​
Log in with API Key on non-whitelisted websites

Currently, we have set up a whitelist to restrict the websites where you can log in to your ComfyUI account. If you need to log in to your ComfyUI account on some non-whitelisted websites, please refer to the account management section to learn how to log in using an API Key. In this case, the corresponding website does not need to be on our whitelist.

Account Management

Learn how to log in with ComfyUI API Key

​
Use ComfyUI API Key Integration to call paid model API nodes

Currently, we support accessing our services through ComfyUI API Key Integration to call paid model API nodes. Please refer to the API Key Integration section to learn how to use API Key Integration to call paid model API nodes.

API Key Integration

Please refer to the API Key Integration section to learn how to use API Key Integration to call paid model API nodes

​
Advantages of API Nodes

API Nodes provide several important advantages for ComfyUI users:

  • Access to closed-source models: Use state-of-the-art AI models without having to deploy them yourself
  • Seamless integration: API nodes are fully compatible with other ComfyUI nodes and can be combined to create complex workflows
  • Simplified experience: No need to manage API keys or handle complex API requests
  • Controlled costs: The prepaid system ensures you have complete control over your spending with no unexpected charges

​
Pricing

API Node Pricing

Please refer to the pricing page for the corresponding API pricing

​
About Open Source and Opt-in

It’s important to note that API Nodes are completely optional. ComfyUI will always remain fully open-source and free for local users. API nodes are designed as an “opt-in” feature, providing convenience for those who want access to external SOTA (state-of-the-art) models.

​
Use Cases

A powerful application of API Nodes is combining the output of external models with local nodes. For example:

  • Using GPT-Image-1 to generate a base image, then transforming it into video with a local wan node
  • Combining externally generated images with local upscaling or style transfer nodes
  • Creating hybrid workflows that leverage the advantages of both closed-source and open-source models

This flexibility makes ComfyUI a truly universal generative AI interface, integrating various AI capabilities into a unified workflow, opening up more possibilities

​
FAQs