ComfyUI Node: 🔑 Seedance 2.0 API Key

🔑 Seedance 2.0 API Key:

The Seedance2ApiKey node is designed to streamline the authentication process for users of the Seedance 2.0 video generation nodes within the ComfyUI environment. By storing your MuAPI API key in this node, you can effortlessly connect it to any Seedance 2.0 node, eliminating the need to repeatedly input your API key for each operation. This node automatically reads the API key from its configuration or from a pre-configured file, ensuring a seamless and efficient workflow. Its primary goal is to simplify the user experience by centralizing API key management, thereby reducing the potential for errors and enhancing productivity.

🔑 Seedance 2.0 API Key Input Parameters:

api_key

The api_key parameter is a string input that allows you to manually specify your MuAPI API key if it is not already configured in the system. This key is essential for authenticating your requests to the Seedance 2.0 API, enabling you to access the various video generation features offered by the platform. If left empty, the node will attempt to read the API key from a configuration file located at ~/.muapi/config.json, which can be set up using the muapi auth configure command. This flexibility ensures that you can either provide the key directly or rely on a pre-configured setup for convenience.

🔑 Seedance 2.0 API Key Output Parameters:

This node does not produce any direct output parameters. Its primary function is to provide the necessary authentication credentials to other Seedance 2.0 nodes, facilitating their operation without requiring additional input from the user.

🔑 Seedance 2.0 API Key Usage Tips:

• Ensure that your API key is correctly configured in the ~/.muapi/config.json file to avoid having to manually input it each time you use a Seedance 2.0 node.
• Use the muapi auth configure command to set up your API key in the configuration file, which will be automatically detected by the Seedance2ApiKey node.

🔑 Seedance 2.0 API Key Common Errors and Solutions:

"request_id required."

• Explanation: This error occurs when a request_id is not provided for a Seedance 2.0 operation that requires it.
• Solution: Ensure that you provide a valid request_id when using nodes that require this parameter, as it is essential for identifying the specific request you are working with.

"Invalid API Key"

• Explanation: This error indicates that the API key provided is incorrect or not authorized to access the Seedance 2.0 services.
• Solution: Double-check your API key for accuracy and ensure it is correctly configured in the ~/.muapi/config.json file or provided directly in the node. If the issue persists, contact MuAPI support for assistance.