meshy-openclaw
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseMeshy 3D — Generation + Printing
Meshy 3D — 生成与打印
Directly communicate with the Meshy AI API to generate and print 3D assets. Covers the complete lifecycle: API key setup, task creation, exponential backoff polling, downloading, multi-step pipelines, and 3D print preparation with slicer integration.
直接与Meshy AI API交互,生成并打印3D资产。覆盖完整生命周期:API密钥设置、任务创建、指数退避轮询、文件下载、多步骤流程,以及集成切片器的3D打印准备。
SECURITY MANIFEST
安全声明
Environment variables accessed:
- — API authentication token sent in HTTP
MESHY_API_KEYheader only. Never logged, never written to any file exceptAuthorization: Bearerin the current working directory when explicitly requested by the user..env
External network endpoints:
- — Meshy AI API (task creation, status polling, model/image downloads)
https://api.meshy.ai
File system access:
- Read: /
.envin the current working directory only (API key lookup).env.local - Write: in the current working directory only (API key storage, only on user request)
.env - Write: in the current working directory (downloaded model files, metadata)
./meshy_output/ - Read: files explicitly provided by the user (e.g., local images passed for image-to-3D conversion), accessed only at the exact path the user specifies
- No access to home directories, shell profiles, or any path outside the above
Data leaving this machine:
- API requests to include the
api.meshy.aiin the Authorization header and user-provided text prompts or image URLs. No other local data is transmitted. Downloaded model files are saved locally only.MESHY_API_KEY
All paths below are relative to this skill's own directory (the directory containing this SKILL.md). Resolve them before running.
| Resource | When to use |
|---|---|
| Bundled CLI for every Meshy API call (create / poll / download / record / …) |
| Detect installed slicers; open a model file in a slicer |
| Fix OBJ coordinate system, scale, and origin for slicers |
| reference.md | Full API reference: every parameter, response schema, error code |
| references/setup.md | API key setup — read when Step 0 finds no key |
| references/pipelines.md | Generation recipes: exact payloads + script calls per endpoint |
| references/printing.md | Print pipeline walkthroughs: slicer detection, analyze/repair, white model, multicolor, Creative Lab |
| references/troubleshooting.md | Error recovery trees and task failure messages |
访问的环境变量:
- — API认证令牌,仅在HTTP
MESHY_API_KEY头中发送。绝不会被记录,仅当用户明确请求时,才会写入当前工作目录下的Authorization: Bearer文件。.env
外部网络端点:
- — Meshy AI API(任务创建、状态轮询、模型/图像下载)
https://api.meshy.ai
文件系统访问权限:
- 读取:仅当前工作目录下的/
.env文件(用于查找API密钥).env.local - 写入:仅当前工作目录下的文件(仅在用户请求时存储API密钥)
.env - 写入:当前工作目录下的文件夹(用于保存下载的模型文件和元数据)
./meshy_output/ - 读取:用户明确提供的文件(例如用于图像转3D转换的本地图像),仅访问用户指定的精确路径
- 无权访问主目录、shell配置文件或上述路径以外的任何位置
离开本地机器的数据:
- 发送至的API请求会在Authorization头中包含
api.meshy.ai,以及用户提供的文本提示或图像URL。不会传输其他本地数据。下载的模型文件仅保存在本地。MESHY_API_KEY
以下所有路径均相对于本技能的目录(包含此SKILL.md的目录)。运行前请先解析路径。
| 资源 | 使用场景 |
|---|---|
| 用于所有Meshy API调用的捆绑CLI(创建/轮询/下载/记录/…) |
| 检测已安装的切片器;在切片器中打开模型文件 |
| 修复OBJ坐标系、缩放比例和原点,适配切片器 |
| reference.md | 完整API参考:所有参数、响应 schema、错误代码 |
| references/setup.md | API密钥设置 — 当步骤0未找到密钥时阅读 |
| references/pipelines.md | 生成方案:每个端点的精确负载+脚本调用方式 |
| references/printing.md | 打印流程指南:切片器检测、分析/修复、单色模型、多色模型、创意实验室 |
| references/troubleshooting.md | 错误恢复流程和任务失败提示信息 |
IMPORTANT: First-Use Session Notice
重要提示:首次使用会话通知
When this skill is first activated in a session, inform the user:
All generated files will be saved toin the current working directory. Each project gets its own folder (meshy_output/) with model files, textures, thumbnails, and metadata. History is tracked in{YYYYMMDD_HHmmss}_{prompt}_{id}/.meshy_output/history.json
This only needs to be said once per session.
当本技能在会话中首次激活时,需告知用户:
所有生成的文件将保存至当前工作目录下的文件夹。每个项目会有独立的文件夹(meshy_output/),包含模型文件、纹理、缩略图和元数据。历史记录保存在{YYYYMMDD_HHmmss}_{prompt}_{id}/中。meshy_output/history.json
此提示每个会话只需告知一次。
IMPORTANT: File Organization
重要提示:文件组织规则
All downloaded files MUST go into a structured directory in the current working directory. Do NOT scatter files randomly.
meshy_output/- Each project:
meshy_output/{YYYYMMDD_HHmmss}_{prompt_slug}_{task_id_prefix}/ - Chained tasks (preview → refine → rig) reuse the same
project_dir - Track tasks in per project, and global
metadata.jsonhistory.json - Auto-download thumbnails alongside models
The bundled CLI implements this: , , and subcommands.
project-dirrecordthumbnail所有下载的文件必须存入当前工作目录下结构化的目录。请勿随意分散文件。
meshy_output/- 每个项目路径:
meshy_output/{YYYYMMDD_HHmmss}_{prompt_slug}_{task_id_prefix}/ - 链式任务(预览→优化→绑定骨骼)复用同一个
project_dir - 在每个项目的和全局
metadata.json中跟踪任务history.json - 自动下载模型对应的缩略图
捆绑CLI已实现此逻辑:包含、和子命令。
project-dirrecordthumbnailIMPORTANT: Shell Command Rules
重要提示:Shell命令规则
Use only standard POSIX tools. Do NOT use , , , /.
rgfdbatexaeza仅使用标准POSIX工具。禁止使用、、、/。
rgfdbatexaezaIMPORTANT: Run Long Tasks Properly
重要提示:正确运行长时任务
Meshy generation takes 1–5 minutes. Run each as a single Bash call and let it finish — the bundled CLI prints unbuffered progress in real time. Tasks sitting at 99% for 30–120s is normal finalization — do NOT interrupt. Pass a larger for heavy tasks instead of retrying.
poll--timeoutMeshy生成任务耗时1-5分钟。将每个作为单个Bash命令运行并等待完成 — 捆绑CLI会实时输出无缓冲的进度信息。任务停留在99%达30-120秒属于正常的最终处理阶段 — 请勿中断。对于重型任务,应设置更大的参数而非重试。
poll--timeoutIMPORTANT: Never Rebuild Bundled Scripts
重要提示:切勿重构捆绑脚本
scripts/meshy_task.pycreate_taskpoll_taskdownloadget_project_dirrecord_tasksave_thumbnailsys.path.insert(0, "<this skill's scripts dir>")from meshy_task import ...scripts/meshy_task.pycreate_taskpoll_taskdownloadget_project_dirrecord_tasksave_thumbnailsys.path.insert(0, "<本技能的scripts目录>")from meshy_task import ...Step 0: API Key Detection (ALWAYS RUN FIRST)
步骤0:API密钥检测(必须首先执行)
Only the current session environment and / in the current working directory are checked. Never scan home directories or shell profile files.
.env.env.localbash
python3 scripts/meshy_task.py check-env仅检查当前会话环境和当前工作目录下的/文件。绝不扫描主目录或shell配置文件。
.env.env.localbash
python3 scripts/meshy_task.py check-envDecision After Detection
检测后的决策
- → Proceed to Step 1.
READY: key=... - → Go to Step 0a.
READY: NO_KEY_FOUND - → Run
PYTHON_REQUESTS: MISSING.pip install requests
- → 进入步骤1。
READY: key=... - → 进入步骤0a。
READY: NO_KEY_FOUND - → 运行
PYTHON_REQUESTS: MISSING。pip install requests
Step 0a: API Key Setup (Only If No Key Found)
步骤0a:API密钥设置(仅当未找到密钥时执行)
Follow references/setup.md: create a key at https://www.meshy.ai/settings/api (Pro plan required), verify it against , and optionally persist it to in the current project (auto-added to ).
GET /openapi/v1/balance.env.gitignore遵循references/setup.md:在https://www.meshy.ai/settings/api创建密钥(需Pro计划),通过`GET /openapi/v1/balance.env.gitignore`)。
验证密钥,可选择将其持久化到当前项目的文件(会自动添加到Step 1: Confirm Plan With User Before Spending Credits
步骤1:消耗积分前与用户确认方案
CRITICAL: Before creating any task, present the user with a cost summary and wait for confirmation:
I'll generate a 3D model of "<prompt>" using the following plan:
1. Preview (mesh generation) — 20 credits
2. Refine (texturing with PBR) — 10 credits
3. Download as .glb
Total cost: 30 credits
Current balance: <N> credits
Shall I proceed?For multi-step pipelines (text-to-3d → rig → animate), show the FULL pipeline cost upfront.
Note: Rigging automatically includes walking + running animations at no extra cost. Only add(3 credits) for custom animations beyond those.Animate
关键:创建任何任务前,需向用户展示成本摘要并等待确认:
我将按照以下方案生成“<prompt>”的3D模型:
1. 预览(网格生成) — 20积分
2. 优化(添加PBR纹理) — 10积分
3. 下载为.glb格式
总成本:30积分
当前余额:<N>积分
是否继续?对于多步骤流程(文本转3D→绑定骨骼→制作动画),需提前展示完整流程的成本。
注意:绑定骨骼会自动包含行走+跑步动画,无需额外付费。仅当需要自定义动画时,才需添加(3积分)。Animate
Intent → API Mapping
用户需求→API映射
| User wants to... | API | Endpoint | Credits |
|---|---|---|---|
| 3D model from text | Text to 3D | | 5–20 (preview) + 10 (refine) |
| 3D model from one image | Image to 3D | | 5–30 |
| 3D model from multiple images | Multi-Image to 3D | | 5–30 |
| New textures on existing model | Retexture | | 10 |
| Change mesh format/topology | Remesh | | 5 |
| Convert a model to other formats (no remesh) | Convert | | 1 |
| Rescale a model to real-world size | Resize | | 1 |
| Generate fresh UVs (GLB, ≤40k faces) before external texturing | UV Unwrap | | 5 |
| Add skeleton to character (textured humanoid only) | Auto-Rigging | | 5 |
| Animate a rigged character | Animation | | 3 |
Browse animations to pick an | Animation Library (public, no API key) | | 0 |
| 2D image from text (recommended pre-step before image-to-3d) | Text to Image | | 3 / 6 / 9 / 9 |
| Optimize/edit a 2D image (recommended pre-step before image-to-3d) | Image to Image | | 3 / 6 / 9 / 12 |
| Photo → styled physical product (figure/lamp/keychain/fridge-magnet) | Creative Lab | | 6 + 30 |
| Check FDM printability | Analyze Printability | | 0 (free) |
| Repair non-manifold/degenerate-face/hole topology | Repair Printability | | 10 |
| Multi-color 3D print | Multi-Color Print | | 10 (+ generation) |
| 3D print a model (white) | → See 3D Printing Workflow section | — | 20 |
| Check credit balance | Balance | | 0 |
| 用户需求 | API类型 | 端点 | 积分 |
|---|---|---|---|
| 从文本生成3D模型 | 文本转3D | | 5–20(预览)+10(优化) |
| 从单张图像生成3D模型 | 图像转3D | | 5–30 |
| 从多张图像生成3D模型 | 多图像转3D | | 5–30 |
| 为现有模型添加新纹理 | 重新纹理 | | 10 |
| 更改网格格式/拓扑结构 | 重新网格化 | | 5 |
| 将模型转换为其他格式(不重新网格化) | 格式转换 | | 1 |
| 将模型缩放至真实世界尺寸 | 调整大小 | | 1 |
| 在外部纹理处理前生成新UV(GLB格式,面数≤40k) | UV展开 | | 5 |
| 为角色添加骨骼(仅带纹理的人形角色) | 自动绑定骨骼 | | 5 |
| 为绑定骨骼的角色制作动画 | 动画生成 | | 3 |
浏览动画以选择 | 动画库(公开,无需API密钥) | | 0 |
| 从文本生成2D图像(图像转3D前推荐的前置步骤) | 文本转图像 | | 3/6/9/9 |
| 优化/编辑2D图像(图像转3D前推荐的前置步骤) | 图像转图像 | | 3/6/9/12 |
| 照片→风格化实体产品(手办/灯具/钥匙扣/冰箱贴) | 创意实验室 | | 6+30 |
| 检查FDM打印可行性 | 打印可行性分析 | | 0(免费) |
| 修复非流形/退化面/孔洞拓扑结构 | 打印修复 | | 10 |
| 多色3D打印 | 多色打印 | | 10(+生成成本) |
| 3D打印模型(单色) | → 查看3D打印工作流章节 | — | 20 |
| 检查积分余额 | 余额查询 | | 0 |
Step 2: Execute the Workflow
步骤2:执行工作流
All generation endpoints return , NOT the model — you MUST poll. NEVER read from the POST response.
{"result": "<task_id>"}model_urlsEvery workflow is a sequence of calls to the bundled CLI — do not write your own API code:
scripts/meshy_task.py| Subcommand | Purpose |
|---|---|
| Step 0 environment report |
| Current credit balance |
| Create a task; prints the new task ID |
| Poll to completion; saves the task JSON into the project dir |
| One-shot status / progress / face_count check |
| Stream-download a model file |
| Create + print the project folder path |
| Update |
| Save the project thumbnail |
| Pre-rigging polycount gate |
Follow the matching recipe in references/pipelines.md: Text to 3D (preview → refine), Image to 3D, Multi-Image to 3D, Retexture, Remesh, Convert / Resize / UV Unwrap, Auto-Rigging + Animation (textured humanoid + t-pose + face-count gate; look up in the public catalog), Text/Image to Image.
action_id2D Optimization Pre-Step (strongly recommended): prefer the image-to-3d route over direct text-to-3d — for a text-only request, first make a design image via (; characters: + ), then 3D-ify. For low-quality reference images, clean up first via . 3–9 extra credits typically buy a noticeable quality bump. Skip when the user provides a clean studio shot, and always skip for Creative Lab products (they stylize internally).
/openapi/v1/text-to-imagenano-banana-progenerate_multi_view: truepose_mode/openapi/v1/image-to-image所有生成端点返回,而非模型 — 必须进行轮询。绝不要从POST响应中读取。
{"result": "<task_id>"}model_urls所有工作流均通过调用捆绑CLI 的子命令序列实现 — 请勿自行编写API代码:
scripts/meshy_task.py| 子命令 | 用途 |
|---|---|
| 步骤0的环境报告 |
| 查询当前积分余额 |
| `create --endpoint E (--payload JSON \ | --payload-file F)` |
| 轮询至任务完成;将任务JSON保存到项目目录 |
| 单次查询状态/进度/面数 |
| `download (--url U \ | --task-json F [--format FMT]) --output PATH` |
| 创建并输出项目文件夹路径 |
| 更新 |
| `thumbnail --project-dir D (--url U \ | --task-json F)` |
| 绑定骨骼前的多边形数量检查 |
遵循references/pipelines.md中的对应方案:文本转3D(预览→优化)、图像转3D、多图像转3D、重新纹理、重新网格化、转换/调整大小/UV展开、自动绑定骨骼+动画(带纹理的人形角色+T姿势+面数检查;从公开目录中查找)、文本/图像转图像。
action_id推荐的2D优化前置步骤:优先选择图像转3D路线而非直接文本转3D — 对于纯文本请求,先通过生成设计图(使用;角色类设置 + ),再转换为3D。对于低质量参考图像,先通过清理。额外花费3-9积分通常能显著提升质量。当用户提供清晰的工作室照片时可跳过此步骤,创意实验室产品则始终跳过(内部已做风格化处理)。
/openapi/v1/text-to-imagenano-banana-progenerate_multi_view: truepose_mode/openapi/v1/image-to-image3D Printing Workflow
3D打印工作流
IMPORTANT: When the user's request involves 3D printing, use this section for the ENTIRE workflow — including model generation. Do NOT run the generation workflows above and then come here. This section controls and other print-specific parameters from the start.
target_formatsTrigger when the user mentions: print, 3d print, slicer, slice, bambu, orca, prusa, cura, multicolor, multi-color, 3mf, figurine, miniature, statue, physical model, desk toy, phone stand.
重要提示:当用户请求涉及3D打印时,全程遵循本节流程 — 包括模型生成。 请勿先运行上述生成工作流再转到本节。本节从一开始就控制和其他打印特定参数。
target_formats当用户提及以下关键词时触发:print、3d print、slicer、slice、bambu、orca、prusa、cura、multicolor、multi-color、3mf、figurine、miniature、statue、physical model、desk toy、phone stand。
Decision: White Model vs Multicolor
决策:单色模型 vs 多色模型
- Detect installed slicers first:
python3 scripts/slicers.py detect - Ask the user: "White model (single-color) or multicolor?"
- If multicolor: check for multicolor-capable slicer (OrcaSlicer, Bambu Studio, Creality Print, Elegoo Slicer, Anycubic Slicer Next), ask max_colors (1-16, default 4) and max_depth (3-6, default 4), confirm cost: 40 credits (+10 if repair is needed)
- (Recommended) After generation, run a printability analysis (, FREE). Run
POST /openapi/v1/print/analyze(10 credits) only if status = error.POST /openapi/v1/print/repair
Then follow the full walkthroughs in references/printing.md:
- White Model Pipeline (20 credits): generate untextured () → download OBJ →
target_formats: ["obj"](Y-up→Z-up, scale to mm, center, bottom at Z=0) → open in slicerscripts/fix_obj.py - Multicolor Pipeline (40 credits): generate + texture (refine/retexture REQUIRED) → multi-color API → download 3MF → open in multicolor slicer. The multi-color API outputs 3MF directly — no coordinate conversion, no needed at generation.
target_formats - Creative Lab (36 credits): photo → (6) →
prototype(30) → textured GLB, ready to print; multicolor viabuild.model_url - Print-quality checklist (wall thickness, overhangs, base stability, …) is in references/printing.md.
Key rules: always detect slicer first and report; always run the FREE analyze for production/functional prints; repair only on (or when quality matters); repair does NOT preserve textures (repair → re-texture → multicolor); if OBJ is unavailable, download GLB and import manually; after opening in a slicer, remind the user to check print settings (layer height, infill, supports).
errorwarning- 首先检测已安装的切片器:
python3 scripts/slicers.py detect - 询问用户:“单色模型(单颜色)还是多色模型?”
- 若选择多色:检查是否支持多色的切片器(OrcaSlicer、Bambu Studio、Creality Print、Elegoo Slicer、Anycubic Slicer Next),询问最大颜色数(1-16,默认4)和最大深度(3-6,默认4),确认成本:40积分(如需修复额外+10积分)
- (推荐) 生成后运行打印可行性分析(,免费)。仅当状态为error时运行**
POST /openapi/v1/print/analyze**(10积分)。POST /openapi/v1/print/repair
然后遵循references/printing.md中的完整指南:
- 单色模型流程(20积分):生成无纹理模型()→下载OBJ→运行
target_formats: ["obj"](Y轴向上转Z轴向上、缩放至毫米单位、居中、底部对齐Z=0)→在切片器中打开scripts/fix_obj.py - 多色模型流程(40积分):生成+纹理(必须优化/重新纹理)→调用多色API→下载3MF→在多色切片器中打开。多色API直接输出3MF格式 — 无需坐标转换,生成时无需设置。
target_formats - 创意实验室流程(36积分):照片→(6积分)→
prototype(30积分)→带纹理的GLB,可直接打印;通过build实现多色打印。model_url - 打印质量检查清单(壁厚、悬垂、底座稳定性等)见references/printing.md。
核心规则:始终先检测切片器并报告;对于量产/功能型打印,始终运行免费的分析;仅在时修复(或对质量有要求时在时修复);修复不会保留纹理(修复→重新纹理→多色);若无法获取OBJ,下载GLB并手动导入;在切片器中打开后,提醒用户检查打印设置(层高、填充率、支撑等)。
errorwarningStep 3: Report Results
步骤3:报告结果
After task succeeds:
- Downloaded file paths and sizes
- Task IDs (for follow-up: refine, rig, retexture)
- Available formats (list keys)
model_urls - Credits consumed + current balance (task JSON has ; run
consumed_credits)balance - Suggested next steps:
- Preview done → "Want to refine (add textures)?"
- Model done → "Want to rig this character?"
- Rigged → "Want to apply a custom animation?"
- Any textured model → "Want to 3D print this? Multicolor printing is available!"
- Any model → "Want to 3D print this?"
任务成功后:
- 下载文件的路径和大小
- 任务ID(用于后续操作:优化、绑定骨骼、重新纹理)
- 可用格式(列出的键)
model_urls - 消耗的积分+当前余额(任务JSON包含;运行
consumed_credits查询)balance - 建议后续操作:
- 预览完成 → “是否需要优化(添加纹理)?”
- 模型完成 → “是否需要为该角色绑定骨骼?”
- 绑定骨骼完成 → “是否需要应用自定义动画?”
- 任何带纹理的模型 → “是否需要3D打印此模型?支持多色打印!”
- 任何模型 → “是否需要3D打印此模型?”
Error Recovery
错误恢复
On any failure, follow references/troubleshooting.md: HTTP status handling (401/402/422/429/5xx), retry policy, and known task messages. The bundled CLI auto-reports the current balance on 402 and exits non-zero with the server's error message on failure.
FAILED遇到任何失败时,遵循references/troubleshooting.md:HTTP状态处理(401/402/422/429/5xx)、重试策略,以及已知的任务提示信息。捆绑CLI会在402状态时自动报告当前余额,并在失败时以非零状态码退出并输出服务器的错误信息。
FAILEDKnown Behaviors & Constraints
已知行为与限制
- 99% stall: Normal finalization (30–120s). Do NOT interrupt.
- Asset retention: Files deleted after 3 days (non-Enterprise). Download immediately.
- PBR maps: Must set explicitly.
enable_pbr: true - Refine: Works with ,
meshy-5, ormeshy-6— pick the same family as your preview for consistency. 10 credits regardless of model. (latestis retired → 400.)meshy-4 - Deprecated params: no longer affects output;
symmetry_modeis ignored by Meshy-6; useart_styleinstead of the oldpose_modeflag; useis_a_t_pose(texture_resolution/"2k"/"4k") instead of"8k"; on image-to-3d usehd_texture(withmodel_type: "smart-topology") instead of the deprecatedai_model: "meshy-t2". Smart Topology is image-to-3d only — Text to 3D and Multi-Image to 3D don't have it."lowpoly" - Rigging needs textures: rig the textured task (text-to-3d refine, or image-to-3d with ) — untextured meshes are unsupported, so a mesh-only preview fails. Also: bipedal humanoid only, ≤300k faces via
should_texture: true, and ainput_task_idmodel must face +Z.model_url - Inspect before downloading: pass on image-to-3d / multi-image-to-3d and read
multi_view_thumbnails: true(front/right/back/left, 512×512 PNG) instead of pulling a 50–200 MB GLB just to check the result. ~3s extra latency.thumbnail_urls - Never hardcode : fetch
action_id(public, no key,GET https://api.meshy.ai/web/public/animations/resourcesto narrow) and match the user's intent against?category=/name. IDs are notcategory— the catalog includes1..N,-2,-1.0 - : Every task GET response includes
consumed_credits— read it to report the real credits spent rather than estimating. Aconsumed_creditstask reportsFAILED(credits are refunded), so a transient failure can be retried without re-approving the spend.0 - Rigging: Humanoid bipedal only, polycount ≤ 300,000 (enforced by ).
check-faces - Printing formats: White model → OBJ with . Multicolor → 3MF from Multi-Color Print API. Always detect slicer first.
scripts/fix_obj.py - Download format: Ask the user which format they need before downloading. GLB (viewing), OBJ (printing), 3MF (multicolor), FBX (games), USDZ (AR). Do NOT download all formats.
- 3MF for multicolor: Multi-Color Print API outputs 3MF directly — no need to request 3MF from generate/refine. For non-print use cases needing 3MF, pass in
"3mf".target_formats - Timestamps: All API timestamps are Unix epoch milliseconds.
- 停留在99%:属于正常的最终处理阶段(30-120秒)。请勿中断。
- 资产保留期限:文件在3天后删除(非企业版)。请立即下载。
- PBR贴图:必须显式设置。
enable_pbr: true - 优化:适用于、
meshy-5或meshy-6— 为保持一致性,请选择与预览相同的系列。无论模型如何,均需10积分。(latest已停用→返回400错误。)meshy-4 - 已弃用参数:不再影响输出;
symmetry_mode被Meshy-6忽略;使用art_style替代旧的pose_mode标志;使用is_a_t_pose(texture_resolution/"2k"/"4k")替代"8k";图像转3D时使用hd_texture(搭配model_type: "smart-topology")替代已弃用的ai_model: "meshy-t2"。Smart Topology仅适用于图像转3D — 文本转3D和多图像转3D不支持此参数。"lowpoly" - 绑定骨骼要求:需为带纹理的任务(文本转3D的优化结果,或设置的图像转3D结果)绑定骨骼 — 无纹理网格不被支持,因此仅含网格的预览任务会失败。此外:仅支持双足人形角色,通过
should_texture: true传入的模型面数≤300k,且input_task_id对应的模型必须朝向+Z轴。model_url - 下载前预览:在图像转3D/多图像转3D时设置,读取
multi_view_thumbnails: true(前/右/后/左视图,512×512 PNG),无需下载50-200MB的GLB即可查看结果。仅增加约3秒延迟。thumbnail_urls - 切勿硬编码:调用
action_id(公开,无需密钥,可通过GET https://api.meshy.ai/web/public/animations/resources筛选),根据用户需求匹配?category=/name。ID并非category— 目录包含1..N、-2、-1等值。0 - :每个任务的GET响应均包含
consumed_credits— 读取此值以报告实际消耗的积分,而非估算。失败任务的consumed_credits为consumed_credits(积分已退还),因此临时失败的任务可重试,无需重新确认花费。0 - 绑定骨骼限制:仅支持双足人形角色,多边形数量≤300,000(由强制执行)。
check-faces - 打印格式:单色模型→通过处理后的OBJ。多色模型→多色打印API输出的3MF。始终先检测切片器。
scripts/fix_obj.py - 下载格式:下载前询问用户所需格式。GLB(查看用)、OBJ(打印用)、3MF(多色打印用)、FBX(游戏用)、USDZ(AR用)。请勿下载所有格式。
- 多色打印用3MF:多色打印API直接输出3MF — 无需从生成/优化请求中获取3MF。对于非打印场景需要3MF格式的,在中传入
target_formats。"3mf" - 时间戳:所有API时间戳均为Unix时间戳(毫秒)。
Execution Checklist
执行检查清单
- Ran API key detection (, Step 0) — checked env var and
check-env/.envonly.env.local - API key verified (never printed in full)
- Presented cost summary and got user confirmation
- Composed the workflow from bundled script calls (never retyped the helpers)
- Followed the matching recipe in references/pipelines.md or references/printing.md
- Reported file paths, formats, task IDs, and balance
- Suggested next steps
- 已执行API密钥检测(,步骤0)— 仅检查环境变量和
check-env/.env文件.env.local - API密钥已验证(从未完整打印)
- 已展示成本摘要并获得用户确认
- 通过捆绑脚本调用组合工作流(从未重新编写辅助函数)
- 遵循了references/pipelines.md或references/printing.md中的对应方案
- 已报告文件路径、格式、任务ID和余额
- 已建议后续操作
Additional Resources
额外资源
For the complete API endpoint reference including all parameters, response schemas, and error codes, read reference.md.
如需包含所有参数、响应schema和错误代码的完整API端点参考,请阅读reference.md。",