跳转到主要内容
Translation Task Breakdown Okay, here’s the workflow for this MDX documentation translation, simplified Chinese. Let’s make sure I’m crystal clear on this. First, I need to translate all textual content. That means headings, paragraphs, list items, and card titles/descriptions, the works. But there are exceptions; I have to leave code blocks, inline code snippets, URLs, API endpoints/paths, variable names, technical identifiers, component names (like <Card>), and parameter names untouched. I need to meticulously maintain the original MDX structure and formatting. Line breaks and spacing are crucial, as is preserving the markdown syntax. I also need to make sure to keep common technical terms in English – things like “API,” “SDK,” “token,” etc. The tone needs to be professional and technical throughout. Finally, I only return the translated text; the original MDX structure is not included in the response. Alright, let’s look at the specific examples given. For the Frontmatter:
  • title: "Create 3D Model" becomes title: "创建 3D 模型".
  • openapi: "POST /v1/3d/generations" remains unchanged.
  • description: "Creates a 3D model generation task" becomes description: "创建一个 3D 模型生成任务".
Then, the Intro Paragraph:
  • “Generate 3D models from text or images using Tripo3D and other providers. This is an asynchronous API.” becomes “使用 Tripo3D 和其他提供商从文本或图像生成 3D 模型。这是一个异步 API。”
Following that, for Headings:
  • ## Request Body becomes ## 请求体
  • ## Response becomes ## 响应
Now, regarding ParamFields and ResponseFields:
  • model: “Model to use (e.g., tripo3d-v2.5, tripo3d-v2).” becomes “要使用的模型（例如 tripo3d-v2.5，tripo3d-v2）。”
  • prompt: “Text description of the 3D model to generate.” becomes “要生成的 3D 模型的文本描述。”
  • image: “Base64-encoded image for image-to-3D generation.” becomes “用于图像转 3D 生成的 Base64 编码图像。”
  • image_url: “URL of image for image-to-3D generation.” becomes “用于图像转 3D 生成的图像 URL。”
  • format: “Output format: glb, fbx, obj, or usdz.” becomes “输出格式：glb、fbx、obj 或 usdz。”
  • quality: “Quality level: draft, standard, or high.” becomes “质量等级：draft、standard 或 high。”
  • style: “Style preset for the model.” becomes “模型的风格预设。”
  • seed: “Seed for reproducible generation.” becomes “用于可复现生成的种子。”
  • user: “A unique identifier for the end-user.” becomes “终端用户的唯一标识符。”
  • id: “Task ID for polling status.” becomes “用于轮询状态的任务 ID。”
  • status: “Task status: pending, processing, completed, or failed.” becomes “任务状态：pending、processing、completed 或 failed。”
  • created: “Unix timestamp of task creation.” becomes “任务创建的 Unix 时间戳。”
Finally, the Code Blocks (RequestExample, ResponseExample): these are to be kept as is. Okay, let’s double-check. I did not translate any parameter names. I also kept “API”, “3D”, “Base64”, “URL”, “Unix” in English. The MDX structure is being meticulously preserved. Excellent. Now I just need to apply this logic to the rest of the document.

​
title: “创建 3D 模型” openapi: “POST /v1/3d/generations” description: “创建一个 3D 模型生成任务”

使用 Tripo3D 和其他提供商从文本或图像生成 3D 模型。这是一个异步 API。

​
请求体

​
model
string
默认值:"tripo3d-v2.5"
要使用的模型（例如 tripo3d-v2.5，tripo3d-v2）。
​
prompt
string
必填
要生成的 3D 模型的文本描述。
​
image
string
用于图像转 3D 生成的 Base64 编码图像。
​
image_url
string
用于图像转 3D 生成的图像 URL。
​
format
string
默认值:"glb"
输出格式：glb、fbx、obj 或 usdz。
​
quality
string
默认值:"standard"
质量等级：draft、standard 或 high。
​
style
string
模型的风格预设。
​
seed
integer
用于可复现生成的种子。
​
user
string
终端用户的唯一标识符。

​
响应

​
id
string
用于轮询状态的任务 ID。
​
status
string
任务状态：pending、processing、completed 或 failed。
​
created
integer
任务创建的 Unix 时间戳。
curl -X POST "https://api.lemondata.cc/v1/3d/generations" \
  -H "Authorization: Bearer sk-your-api-key" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "tripo3d-v2.5",
    "prompt": "A detailed medieval castle with towers",
    "format": "glb",
    "quality": "high"
  }'

{
  "id": "3d_abc123",
  "status": "pending",
  "created": 1706000000,
  "model": "tripo3d-v2.5"
}