tencent/hunyuan-3d-smart-topology with the Comfy Router API. Tencent provides the model; Router gives it the shared authentication and request route below.
Quick start
Create a key at platform.comfy.org/profile/api-keys and export it asCOMFY_API_KEY. The Python and TypeScript snippets use the Comfy SDKs (pip install comfy-sdk, npm install @comfyorg/sdk); the cURL snippet is the same call over raw HTTP.
Model ID: tencent/hunyuan-3d-smart-topology
Endpoint: POST https://api.comfy.org/v2/models/tencent/hunyuan-3d-smart-topology
Schema
Input
string
Polygon reduction level.Possible values:
high, medium, lowobject
required
3D file input for smart topology
string
required
3D file format typePossible values:
OBJ, GLBstring (uri)
required
URL of the 3D file to retopologiseFormat:
uristring
Polygon type for the output mesh. Defaults to triangle.Possible values:
triangle, quadrilateralGET /v2/models/tencent/hunyuan-3d-smart-topology/openapi.json, the same document it validates a call against before the request reaches the provider.
Output
Router does not publish an output schema for this model.Examples
Input
Before you ship
Save oneIdempotency-Key for each call and reuse it for retries. Router can hold the connection for up to 10 minutes. The SDKs handle authentication; raw HTTP clients send the headers themselves.
When a request fails, Router sends an X-Comfy-Error-Type response header explaining why. A 422 means Router rejected the input before calling the provider. Download generated assets promptly because result URLs can expire.
Headers
Authentication, idempotency, request IDs, error buckets, retry pacing, spend limits.
Using the Router API
Model discovery, validation errors, retries, and billing.
Limitations
What Router does not do today, and what to use instead.