细节精修

You know the look: a rendered product that's technically fine but flat. The brushed-metal machining marks read as a blur, the wood grain is a suggestion, and the client keeps saying "make it pop." Locally you'd reach for a detailer node - crop the region, upscale, re-diffuse - or a sharpening pass and fight with masks. This node does the specialized version of that for exactly two material families: metal and wood. It's the "detail polish" node for product photographers who don't want to babysit an inpainting loop.

How it works

It's one POST to the pack's gateway with the model id detail-jin, your image base64'd, plus the material type you're polishing. The server re-renders the surface detail - machining marks, brushed texture, grain, knots - and returns a cleaned-up image. Under the hood this is the same "give the region its own high-detail pass" idea that local detailers use, except you don't pick the region: you pick the material, and the model decides where the detail belongs. That's the whole pitch, and it's also the limitation.

The inputs that matter

• input_image (IMAGE) - your product render or photo.
• Polished_type (enum) - this is the knob that matters: 金属&木纹 (metal & wood), 木纹 (wood grain only), or 金属 (metal only). The defaults are Chinese, which is fine - you'll get used to it. Pick the material you actually shot; telling it "metal" on a wooden table gets you table detail.
• num_images (INT, 1–2, default 1) - how many variants to request. The node accepts up to 2, so if you're indecisive this is a cheap way to get a couple of takes in one run.
• seed (INT, default 0) - reproducibility, with the pack's usual small offset before it hits the API.

One output: output, a normal IMAGE. Wire it to a save node and you're done.

Installing it

Standard pack install - this is one node in comfyui-MJAPI-party. ComfyUI Manager, search "mojieapi_party", install, restart:

cd ComfyUI/custom_nodes
git clone https://github.com/MoJIeAIGC/comfyui-MJAPI-party.git

Then register at mojieaigc.com and put your key in config.ini at the pack root (leave BASE_URL = https://www.mojieaigc.com/v1/completions untouched):

[API]
KEY = your_api_key
BASE_URL = https://www.mojieaigc.com/v1/completions

Restart again. Nothing to download; the dependencies are the standard numpy/torch/pillow/requests set.

Common issues

• Error image with text in it. That's the pack's error reporting - the API message is baked into the returned picture. Usually a missing key or an empty credit balance.
• Over-sharpened, crunchy output. This is a generative polish, so it can overdo it on already-clean renders. Back off by giving it a slightly blurrier source or just run it once instead of chaining it. If you need surgical control over where the detail goes, the pack's DetailPhotoNode (mask-based) is the better pick - this one is for whole-surface material polish.
• It's a cloud call. Your product image leaves the machine and each run is metered. For a single hero shot that's fine; for a batch of 200 renders, the per-image cost and the latency (up to a 20-minute timeout in the code) add up fast.