Load3DConvertAPIKEY

Here's the thing about the ComfyUI-3D-Convert pack: it doesn't convert 3D files on your machine. Every conversion is a round trip to the NSDT cloud API at 3dconvert.nsdt.cloud, and that service is gated by an API key. Load3DConvertAPIKEY is the node that holds that key for you. It takes a string in, prints nothing useful, and hands the same string back out. Like its sibling Load3DFile, it's a pass-through - but a pass-through with a job.

The job is keeping your key in one visible place. The convert node (ConvertTo3DFormat) has its own api_key input, but if you're converting several files in a workflow, or you just don't like pasting credentials deep inside the graph, you wire this node's output into every api_key port and manage the secret in exactly one spot. It's the 3D-conversion equivalent of the API-key loader nodes you see in text-to-speech and image-API packs - boring, deliberate, and quietly useful.

What you set

One required input:

• api_key - your NSDT key, pasted as a multiline string. Here's the gotcha that catches people: the field's default value is the literal text Get your API KEY from: https://3dconvert.nsdt.cloud/. That's a placeholder, not a key. Run a conversion with it still in there and the upload dies with an auth error. Grab a real key from that URL and replace the placeholder before you hit Queue.

The output, also called api_key, is the string you pasted - wire it into ConvertTo3DFormat's api_key input.

Installing and the two things worth knowing

Install is the same as the rest of the pack - ComfyUI Manager (search "ComfyUI-3D-Convert") or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/nsdtcloud3d/ComfyUI-3D-Convert

Then restart ComfyUI. The whole pack's dependency list is a single Requests, so there's nothing heavy to wrangle.

Two things worth knowing before you rely on this:

• The key is mandatory, not optional. The convert node's code bails out and hands you back the original file path if the key is missing - silent failure again. If a conversion "succeeds" without changing anything, check whether a key actually made it through this node.
• Your key travels in the workflow JSON. ComfyUI workflows are plain-text JSON, and this node stores your key as a literal string. If you share a workflow that uses it - and the "workflow included" culture is real - you are sharing your key. Treat it like a password, don't post workflows containing it, and rotate it if you slip up.

This is a tiny utility node, and it's fine being tiny. It won't store your key encrypted, it won't fetch one for you, and it doesn't validate anything. What it does is give you one clean place to paste a credential - which, for a pack whose entire point is a paid-by-usage cloud service, is more structure than you might expect.