3D Generation Partner Integration#

Two 3D generation partners — Tripo and Rodin — are defined in the comfy-cli OpenAPI spec but are deliberately excluded from the comfy generate CLI surface. Their endpoints live in the proxy spec as released API nodes, but no user-facing CLI commands exist for them.

OpenAPI Spec Definitions#

Both partners are defined in comfy_cli/command/generate/spec/openapi.yml (accessed via spec.py):

Tripo (/proxy/tripo/v2/openapi/…) exposes four endpoints, each marked x-excluded: true 1:

• GET /proxy/tripo/v2/openapi/task/{task_id} — poll task status (tripoGetTask) 2
• POST /proxy/tripo/v2/openapi/upload — upload a reference image for 3D generation (tripoUploadFile) 3
• POST /proxy/tripo/v2/openapi/task — create a 3D generation task (tripoCreateTask) 4
• GET /proxy/tripo/v2/openapi/user/balance — query account balance (tripoGetBalance) 5

Rodin (/proxy/rodin/api/v2/…) exposes three endpoints, all marked x-excluded: true:

• POST /proxy/rodin/api/v2/rodin — create a 3D generation task (rodinGenerate3DAsset) 6
• POST /proxy/rodin/api/v2/status — check generation status (rodinCheckStatus) 7
• POST /proxy/rodin/api/v2/download — get download URL list for generated assets (rodinDownload) 8

How Exclusion Works#

The CLI's endpoint registry is inclusion-based: only endpoints explicitly listed in _ENDPOINT_ALLOWLIST in spec.py are surfaced to users. Neither Tripo nor Rodin appears in that list, so neither is reachable via comfy generate.

The x-excluded: true marker in the OpenAPI YAML is not read by spec.py — it is metadata for external tooling (e.g., documentation generation or API gateway config). Filtering is driven purely by absence from _ENDPOINT_ALLOWLIST. No entry in the _ALIASES dictionary maps to either partner either.

3D Mesh Output Format Handling#

The spec defines rich 3D mesh output schemas for Tripo:

• TripoStandardFormat: glb, fbx
• TripoConvertFormat: GLTF, USDZ, FBX, OBJ, STL, 3MF 9
• TripoTextureFormat: BMP, DPX, HDR, JPEG, OPEN_EXR, PNG, TARGA, TIFF, WEBP 10

Rodin's output is simpler, parameterized by:

• RodinMeshModeType: Quad or Raw 11
• RodinQualityType: extra-low, low, medium, high 12
• RodinMaterialType: PBR or Shaded 13
• RodinTierType: Regular, Sketch, Detail, Smooth 14

3D output URLs (.gltf, .glb, .obj, .fbx) are treated identically to image or video URLs by the polling layer. The _MEDIA_EXTS tuple in poll.py includes .gltf, .glb, .obj, and .fbx alongside image/video extensions, so any 3D mesh URL surfaced in a completed job's response body will be collected into PollResult.image_urls using the same _extract_urls walker 15. There is no special-cased 3D output path.

No Polling Adapters for 3D Partners#

The _POLL_SPECS registry in poll.py 16 contains entries for every active video/image partner (Kling, Luma, Runway, MiniMax, etc.), but neither Tripo nor Rodin has a PollSpec entry. If either partner were added to _ENDPOINT_ALLOWLIST in the future, a matching PollSpec would also need to be added (or a BFL-style self-polling URL returned on creation).