Meshy - API Key

The least exciting node in this pack is the one you can't skip. MeshyAPIKey doesn't generate anything, doesn't call the API, doesn't even check that your key works. It's a glorified text field that hands your API key to the other Meshy nodes. But every generation node in ComfyUI-Meshy demands an APIKEY input on a wire, and this is the only thing that produces it - so it's the first node you'll drop on the canvas, and the one you'll quietly forget about until a workflow you shared comes back to bite you.

How it works

Nothing to reverse-engineer here. The node exposes a single required input, api_key, a multiline string whose default value is literally a reminder: "Get your API KEY from: https://www.meshy.ai/api". Its one output, api_key, carries the APIKEY type. Wire that output into the api_key input on Meshy Text to 3D (Preview), Meshy Text to 3D (Refine), or Meshy Image to 3D and you're done. No network calls, no validation, no storage - it's a pass-through that exists so the other nodes have a clean, typed input to connect to.

That means the error handling you might expect here lives elsewhere. A bad key won't complain at this node; the generation node will get a 401 when it actually talks to Meshy and print Authentication failed. Please check your API key. to the console. Same story for a key with no credits left.

The trap nobody warns you about

Your API key is text, and ComfyUI embeds the full workflow JSON in the PNG metadata of every image it saves. Export a workflow PNG with your key wired in and share it, and you've just published your key - Meshy keys are tied to your account and your credits. Treat this node's contents like a password: never paste a real key into a workflow you'll upload anywhere, and if you've already done it, rotate the key at your Meshy dashboard. It's the most "remember to change your SSH key after a breach" moment in the pack.

Installing

This is a dependency-light pack - there are no model downloads at all, because everything runs on Meshy's servers. Install it the normal way:

cd ComfyUI/custom_nodes
git clone https://github.com/Kazama-Suichiku/ComfyUI-Meshy
pip install -r ComfyUI-Meshy/requirements.txt

then restart ComfyUI. Or, easier, use ComfyUI Manager and search for "ComfyUI-Meshy". Note the pack is brand new - a single initial commit from late 2025 - so if Manager's registry hasn't picked it up yet, the manual clone above is the reliable route. The requirements.txt is just numpy, Pillow, requests, torch, and pyhocon; only pyhocon is unusual, and it's used to parse the pack's own config file.

What can go wrong

Mostly nothing, because this node does so little. The classic failure is pasting the key with a stray space or newline from a copy-paste, so if you get 401s, check the raw text before blaming Meshy. Get your key from https://www.meshy.ai/api, sign up if you haven't, and make sure the account has credits - generation costs them, and this node will happily accept a key that can't afford anything.