Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

docs(forge): document the Tripo house lane and add its changelog entry

nirholas74c8c1e7674e
diff --git a/CHANGELOG.md b/CHANGELOG.md
index d17f0bbca..e9e93aa52 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -23,6 +23,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Scene Studio: an Agent tab that edits your open scene by prompt, plus a TSL node material editor**: Scene Studio's sidebar grows two tabs. Agent is a chat panel that reads the open scene and drives it with the same real editor.execute(Command) calls the toolbar and menus use (free, keyless, rate-limited model via POST /api/scene/agent): add a primitive or a Forge-generated object, move/rotate/scale a named object, recolor a material. Every mutating prompt pushes a numbered version (a scene snapshot plus a viewport screenshot); clicking an earlier version restores it as one more undoable edit, so a bad restore is one Ctrl+Z away like any other mistake. Nodes is a dropdown-wired TSL (Three.js Shading Language) material graph editor for the selected object: build a graph from UV, time, color, texture, and math nodes as a reorderable card list, no canvas or wires to route, and apply it to swap in a real node material through the same undo-able command path. Fixed along the way: restoring a version used to append the snapshot's objects on top of the current scene instead of replacing them (SetSceneCommand, the vendored editor's own scene-import command, only ever adds); and the site-wide corner-stack widget could sit on top of the Agent tab's version-restore buttons and eat the click, now suppressed while the studio is open. (`/scene`) `[feature, fix]`
- **Text-to-motion gets a second GPU backend: MoMask, selectable per request**: The self-hosted text-to-motion worker behind the Animation Studio and POST /api/forge-motion now runs two independent generation backends on the same GPU lane: MDM (Motion Diffusion Model, MIT), the existing default, and MoMask (EricGuo5513/momask-codes, MIT), a residual-VQ tokenizer plus masked and residual transformer that publishes a lower HumanML3D FID (0.045 vs. T2M-GPT's 0.141). Pass model: "momask" to /infer or /api/forge-motion to route a prompt through it instead; omit it and MDM keeps answering as before. Both backends converge on the same (T,22,3) HumanML3D position format and the same shared decode math, so a MoMask clip previews, retargets, and exports exactly like an MDM one. The two projects ship conflicting top-level `utils` packages; the worker resolves that at load time so either backend can be warmed in the same container without the other's modules leaking in. MoMask's checkpoints are staged to production storage and the worker is wired to load them; the first on-GPU deploy and a real in-house benchmark against MDM are tracked as the next step. (`/pose`) `[feature, infra]`
- **Three new engine bridges: Unity, Godot, and Unreal, one prompt to a mesh in your editor**: A shared contract (specs/ENGINE_BRIDGE.md) and three real, independent implementations: a Unity UPM package that imports with glTFast, a Godot addon that imports with Godot's own native GLTFDocument, and an Unreal plugin that imports through Unreal's Interchange glTF pipeline. Each one calls only the public Forge API (POST /api/forge to submit, GET /api/forge?job=<id> to poll, a plain HTTPS GET to download), the same free-first routing and anonymous x-forge-client auth every other Forge caller gets, with the same four import settings (generate_colliders, import_materials, scale, destination) mapped onto each engine's own equivalent. A dropdown and a Generate button in each editor: type a prompt, get a mesh dropped into your scene. (`/docs/engine-bridges`) `[feature, sdk]`
+- **Tripo house lane: v3 API, house key, signed webhooks, and engine-version attribution**: The Tripo integration moved off the legacy v2 API onto v3 (openapi.tripo3d.com/v3): dedicated endpoints per capability, a unified input field, and a unified error envelope. Setting TRIPO_API_KEY turns Tripo from a bring-your-own-key engine into a High-tier house default billed to $THREE credits, with the BYOK path and the engine list unchanged when the variable is unset. A finished job can complete by poll or by Tripo's own signed webhook (api/forge/webhook/tripo.js), which verifies Tripo-Webhook-Signature and claims Tripo-Webhook-Delivery so a retried delivery cannot double-complete a job; polling stays the fallback. Every Tripo result, BYOK or house key, now names the exact model version it ran on in the submit, poll, and gallery responses and in the exported GLB's own metadata, and a new npm run forge:tripo reports the lane's own completion rate and median latency by day. (`/docs/forge`) `[feature, infra]`
## 2026-10-11
diff --git a/data/changelog.json b/data/changelog.json
index af0714b4b..98f50417f 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -11,6 +11,16 @@
"improvement"
]
},
+ {
+ "date": "2026-10-12",
+ "title": "Tripo house lane: v3 API, house key, signed webhooks, and engine-version attribution",
+ "link": "/docs/forge",
+ "summary": "The Tripo integration moved off the legacy v2 API onto v3 (openapi.tripo3d.com/v3): dedicated endpoints per capability, a unified input field, and a unified error envelope. Setting TRIPO_API_KEY turns Tripo from a bring-your-own-key engine into a High-tier house default billed to $THREE credits, with the BYOK path and the engine list unchanged when the variable is unset. A finished job can complete by poll or by Tripo's own signed webhook (api/forge/webhook/tripo.js), which verifies Tripo-Webhook-Signature and claims Tripo-Webhook-Delivery so a retried delivery cannot double-complete a job; polling stays the fallback. Every Tripo result, BYOK or house key, now names the exact model version it ran on in the submit, poll, and gallery responses and in the exported GLB's own metadata, and a new npm run forge:tripo reports the lane's own completion rate and median latency by day.",
+ "tags": [
+ "feature",
+ "infra"
+ ]
+ },
{
"date": "2026-10-12",
"title": "Companion presence: sustained mood, emoji-driven expression, an LLM gesture tool, active-listening nods, and real multi-language lip-sync",
diff --git a/docs/forge.md b/docs/forge.md
index c77bd2fab..16a765c2d 100644
--- a/docs/forge.md
+++ b/docs/forge.md
@@ -43,6 +43,35 @@ Each backend declares which paths it serves, whether it needs a bring-your-own-k
- **Meshy 6**, **Tripo v3.1**, **Rodin (Hyper3D)**, BYOK geometry-first engines with quad topology and a real poly target. You supply your own key.
- **Stable Fast 3D** (Stability, BYOK) and **Replicate (your account)** (BYOK), single-image reconstruction lanes.
+### The Tripo house lane
+
+Tripo v3.1 runs two ways. Paste your own key and it is a BYOK engine like Meshy or Rodin,
+billed to nothing of ours. Set `TRIPO_API_KEY` on the deployment and the same lane becomes
+a High-tier default and an explicit "Tripo" engine choice, billed to $THREE credits like
+the other house lanes; leave the variable unset and routing and the engine list are exactly
+what they were before it existed. The provider speaks Tripo's v3 REST API
+(`openapi.tripo3d.com/v3`): dedicated endpoints per capability, a unified `input` field, and
+the unified `{code, message, suggestion, request_id}` error envelope.
+
+A finished job can complete two ways. The client polls `GET /api/forge?job=<id>` the same
+as any other async lane, or Tripo's own signed webhook (`api/forge/webhook/tripo.js`)
+delivers the result first; the receiver verifies `Tripo-Webhook-Signature`, claims
+`Tripo-Webhook-Delivery` so a retried delivery cannot double-complete a job, and finishes
+it the same way a poll would. Polling always still works, so a missing or misconfigured
+webhook degrades to the slower path, never a stuck job.
+
+Every Tripo result, BYOK or house key, names the exact model version it ran on
+(`TRIPO_MODEL_VERSION`, or the provider's current default) in the submit, poll, and gallery
+responses, and in the exported GLB's own `asset.extras.engine`/`engineVersion` metadata, so
+a model you download still says which engine and version made it after the gallery entry is
+gone. `npm run forge:tripo` reports the house lane's own health, completion rate and median
+latency by day, scoped to `backend = 'tripo'`, separately from `npm run forge:funnel`'s
+all-backend numbers.
+
+See [the Tripo partner note](./partners/tripo.md) for the partnership context and what is
+and is not wired yet (low-poly/quad game-ready preset and Smart Segmentation are built on
+self-hosted GCP workers instead; no live Tripo splat endpoint exists to wire).
+
### Free-first routing with live health
Routing (`resolveBackendIdWithHealth`) walks an ordered list of every free lane that could serve the request on this deployment, most preferred first: the tier's named free engine, then the per-path fallback chain (our own GPU workers, then the free external Spaces, then the free NVIDIA lane as the final health-gated safety net). Draft and Standard name our self-host TRELLIS worker; High names our self-host Hunyuan3D worker. The free NVIDIA NIM lane is never a named default: reconstructing straight from a truncated prompt with no photoreal reference is the realism hole this ordering closes, so it trails as the final health-gated fallthrough (and stays explicitly selectable). A subject classifier reorders the two self-host PBR lanes for hard-surface versus organic prompts. Every entry is env-gated, so the list degrades cleanly on partial deployments.
diff --git a/docs/partners/tripo.md b/docs/partners/tripo.md
index aed6cd740..196e3ab72 100644
--- a/docs/partners/tripo.md
+++ b/docs/partners/tripo.md
@@ -23,8 +23,8 @@ low-poly, splats, segmentation).
| Latest round | Series B/B+, about RMB 3B (about USD 446M), 2026-09-01, led by Matrix Partners China with game publishers as strategic investors | Press (36kr, DealStreetAsia), not a filing |
| Earlier 2026 rounds | USD 50M Series A (March), about USD 200M A+/A++ (June), USD 150M A3 (July) | Press |
| Users | 6.5M creators, about 90K developers, about 100M models | Tripo's own figures, not independently verified |
-| API | v3 at `openapi.tripo3d.ai/v3`, with a published v2-to-v3 migration guide | [developers.tripo3d.ai](https://developers.tripo3d.ai) |
-| API pricing | 1 credit = USD 0.01. Text to 3D 10 (untextured) or 20 (textured); image or multiview 20 or 30; HD texture +10; quad +5; auto-rig 25; retarget 10 per clip; rig check free | developers.tripo3d.ai, checked 2026-10-09 |
+| API | v3 at `openapi.tripo3d.com/v3`, with a published v2-to-v3 migration guide | [developers.tripo3d.com](https://developers.tripo3d.com) |
+| API pricing | 1 credit = USD 0.01. Text to 3D 10 (untextured) or 20 (textured); image or multiview 20 or 30; HD texture +10; quad +5; auto-rig 25; retarget 10 per clip; rig check free | developers.tripo3d.com, checked 2026-10-09 |
| Enterprise route | "custom volumes, dedicated support, or SLA guarantees" via **[email protected]** | Tripo's official pricing page |
| Affiliate program | 30% recurring for 12 months on Tripo's own terms page; a third-party affiliate network lists different terms | Confirm on the call |
@@ -48,7 +48,8 @@ Verified in this repository and in production on 2026-10-09.
| Surface | Where | What it does |
|---|---|---|
-| Tripo v3.1 API lane, bring-your-own-key | [`api/_providers/tripo.js`](../../api/_providers/tripo.js), tier entry in [`api/_lib/forge-tiers.js`](../../api/_lib/forge-tiers.js) | Text and image to 3D on model `v3.1-20260211`, over the **legacy v2** endpoint `api.tripo3d.ai/v2/openapi`. Only runs when the user pastes their own key; the key link in the Forge points at `platform.tripo3d.ai/api-keys` |
+| Tripo v3.1 API lane, bring-your-own-key or house key | [`api/_providers/tripo.js`](../../api/_providers/tripo.js), tier entry in [`api/_lib/forge-tiers.js`](../../api/_lib/forge-tiers.js) | Text and image to 3D on model `v3.1-20260211`, on the **v3** endpoint `openapi.tripo3d.com/v3`. Runs on a pasted user key, or on `TRIPO_API_KEY` when the platform sets one (a High-tier default and an explicit "Tripo" engine choice, billed to $THREE credits); the BYOK key link in the Forge points at `platform.tripo3d.ai/api-keys` |
+| Signed webhook receiver | [`api/forge/webhook/tripo.js`](../../api/forge/webhook/tripo.js) | Verifies `Tripo-Webhook-Signature`, claims `Tripo-Webhook-Delivery` for idempotency, and completes a job the same way polling does; registering the endpoint URL in Tripo's dashboard and setting `TRIPO_WEBHOOK_SECRET` are the owner's last step |
| TripoSG, self-hosted | [`workers/model-triposg`](../../workers/model-triposg/) | The sketch-to-3D lane, and the last automatic failover rung for photo jobs ([forge failover](../forge.md)) |
| TripoSR, self-hosted and hosted | [`workers/model-triposr`](../../workers/model-triposr/) (the fast lane in the avatar pipeline controller), plus a rung in the free Hugging Face Spaces chain ([`api/_providers/huggingface.js`](../../api/_providers/huggingface.js)) | The fast path, at about 3 seconds of GPU time per mesh, and part of the free photo-to-3D failover chain |
@@ -137,12 +138,31 @@ engineering item we ship for it is kept whichever way the deal goes.
## Engineering, ready to run
-The integration work is a work order, so it can be built before the deal is signed and
-switched on by one environment variable when it is:
-[`084-partners-01-tripo-v3-house-lane.md`](../../prompts/finish/084-partners-01-tripo-v3-house-lane.md).
-It keeps the BYOK path exactly as it is today and adds the house key behind `TRIPO_API_KEY`,
-which does not exist on the production service yet (checked 2026-10-09). Putting a
-platform-paid key there is the owner's decision, because it onboards a paid API.
+The integration work is a work order,
+[`084-partners-01-tripo-v3-house-lane.md`](../../prompts/finish/084-partners-01-tripo-v3-house-lane.md),
+and most of it is built and tested, not just planned:
+
+- **v3 migration**: done. The provider speaks the v3 REST API end to end (dedicated
+ endpoints per capability, the unified `input`/task-id model, the unified error envelope).
+- **House key**: done. `TRIPO_API_KEY` makes Tripo a High-tier default and an explicit
+ engine choice, billed to $THREE credits like the other house lanes; with the variable
+ unset, behavior is unchanged. It does not exist on the production service yet (checked
+ 2026-10-09), so flipping it on is the owner's decision: it onboards a paid API.
+- **Signed webhooks**: done. Polling stays the fallback.
+- **Auto-rig**: done. `rig({spec:'mixamo'})` output canonicalizes through
+ `glb-canonicalize.js`'s existing Mixamo mapping and drives the universal retargeter,
+ the same as any other humanoid rig.
+- **Low-poly/quad game-ready preset and Smart Segmentation**: the provider methods exist
+ (`decimate()`, `segment()` in `api/_providers/tripo.js`) but are not dispatched from any
+ endpoint. Both capabilities already run on self-hosted GCP workers in production
+ (`workers/remesh` for game-ready, with FBX export and PBR re-bake Tripo's endpoint does
+ not do; `workers/segment` + PartCrafter/HoloPart for parts, order `070-best3d-04`), which
+ the owner's standing GCP-first directive prefers over an equivalent paid third-party lane.
+ Wiring Tripo here would add a strictly narrower alternative, not new capability; revisit
+ if the partnership itself makes Tripo's version the one worth shipping.
+- **Splat**: no live Tripo endpoint exists to wire (checked again 2026-10-12). The splat
+ stage (`docs/splat.md`) has no Tripo-backed path; this is the "early access" item in the
+ proposal above, not something we can build today.
---
diff --git a/public/changelog-recent.json b/public/changelog-recent.json
index 5f7c8fa93..ca3ac260f 100644
--- a/public/changelog-recent.json
+++ b/public/changelog-recent.json
@@ -1,11 +1,11 @@
{
- "generated_at": "2026-10-12T22:34:26.899Z",
+ "generated_at": "2026-10-12T23:40:53.561Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
"url": "https://three.ws"
},
- "total": 4047,
+ "total": 4048,
"complete": false,
"full_feed": "/changelog.json",
"entries": [
@@ -158,6 +158,17 @@
"sdk"
]
},
+ {
+ "date": "2026-10-12",
+ "type": "update",
+ "title": "Tripo house lane: v3 API, house key, signed webhooks, and engine-version attribution",
+ "summary": "The Tripo integration moved off the legacy v2 API onto v3 (openapi.tripo3d.com/v3): dedicated endpoints per capability, a unified input field, and a unified error envelope. Setting TRIPO_API_KEY turns Tripo from a bring-your-own-key engine into a High-tier house default billed to $THREE credits, with the BYOK path and the engine list unchanged when the variable is unset. A finished job can complete by poll or by Tripo's own signed webhook (api/forge/webhook/tripo.js), which verifies Tripo-Webhook-Signature and claims Tripo-Webhook-Delivery so a retried delivery cannot double-complete a job; polling stays the fallback. Every Tripo result, BYOK or house key, now names the exact model version it ran on in the submit, poll, and gallery responses and in the exported GLB's own metadata, and a new npm run forge:tripo reports the lane's own completion rate and median latency by day.",
+ "link": "/docs/forge",
+ "tags": [
+ "feature",
+ "infra"
+ ]
+ },
{
"date": "2026-10-11",
"type": "launch",
@@ -1540,16 +1551,6 @@
"tags": [
"launch"
]
- },
- {
- "date": "2026-10-09",
- "type": "launch",
- "title": "Docs · Workbench",
- "summary": "How the Workbench runs a photo through an editable workflow of real GPU nodes, edits the result in the viewport, exports GLB, OBJ, STL or PLY, and how scripts call the same pipeline.",
- "link": "/docs/workbench",
- "tags": [
- "launch"
- ]
}
]
}
diff --git a/public/changelog.json b/public/changelog.json
index f8492b3d0..d92cb4b6e 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-10-12T22:34:26.876Z",
+ "generated_at": "2026-10-12T23:40:53.539Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -155,6 +155,17 @@
"sdk"
]
},
+ {
+ "date": "2026-10-12",
+ "type": "update",
+ "title": "Tripo house lane: v3 API, house key, signed webhooks, and engine-version attribution",
+ "summary": "The Tripo integration moved off the legacy v2 API onto v3 (openapi.tripo3d.com/v3): dedicated endpoints per capability, a unified input field, and a unified error envelope. Setting TRIPO_API_KEY turns Tripo from a bring-your-own-key engine into a High-tier house default billed to $THREE credits, with the BYOK path and the engine list unchanged when the variable is unset. A finished job can complete by poll or by Tripo's own signed webhook (api/forge/webhook/tripo.js), which verifies Tripo-Webhook-Signature and claims Tripo-Webhook-Delivery so a retried delivery cannot double-complete a job; polling stays the fallback. Every Tripo result, BYOK or house key, now names the exact model version it ran on in the submit, poll, and gallery responses and in the exported GLB's own metadata, and a new npm run forge:tripo reports the lane's own completion rate and median latency by day.",
+ "link": "/docs/forge",
+ "tags": [
+ "feature",
+ "infra"
+ ]
+ },
{
"date": "2026-10-11",
"type": "launch",
diff --git a/public/changelog.xml b/public/changelog.xml
index f342c1d02..4f85a41f3 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -118,6 +118,14 @@
<category>feature</category>
<description>A shared contract (specs/ENGINE_BRIDGE.md) and three real, independent implementations: a Unity UPM package that imports with glTFast, a Godot addon that imports with Godot's own native GLTFDocument, and an Unreal plugin that imports through Unreal's Interchange glTF pipeline. Each one calls only the public Forge API (POST /api/forge to submit, GET /api/forge?job=&lt;id&gt; to poll, a plain HTTPS GET to download), the same free-first routing and anonymous x-forge-client auth every other Forge caller gets, with the same four import settings (generate_colliders, import_materials, scale, destination) mapped onto each engine's own equivalent. A dropdown and a Generate button in each editor: type a prompt, get a mesh dropped into your scene.</description>
</item>
+ <item>
+ <title>Tripo house lane: v3 API, house key, signed webhooks, and engine-version attribution</title>
+ <link>https://three.ws/docs/forge</link>
+ <guid isPermaLink="false">2026-10-12:Tripo house lane: v3 API, house key, signed webhooks, and engine-version attribution</guid>
+ <pubDate>Mon, 12 Oct 2026 12:00:00 GMT</pubDate>
+ <category>feature</category>
+ <description>The Tripo integration moved off the legacy v2 API onto v3 (openapi.tripo3d.com/v3): dedicated endpoints per capability, a unified input field, and a unified error envelope. Setting TRIPO_API_KEY turns Tripo from a bring-your-own-key engine into a High-tier house default billed to $THREE credits, with the BYOK path and the engine list unchanged when the variable is unset. A finished job can complete by poll or by Tripo's own signed webhook (api/forge/webhook/tripo.js), which verifies Tripo-Webhook-Signature and claims Tripo-Webhook-Delivery so a retried delivery cannot double-complete a job; polling stays the fallback. Every Tripo result, BYOK or house key, now names the exact model version it ran on in the submit, poll, and gallery responses and in the exported GLB's own metadata, and a new npm run forge:tripo reports the lane's own completion rate and median latency by day.</description>
+ </item>
<item>
<title>Classic Home</title>
<link>https://three.ws/classic</link>
diff --git a/public/features.json b/public/features.json
index 966bc2cbe..021d181dd 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-10-12T22:34:26.862Z",
+ "generated_at": "2026-10-12T23:40:53.524Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",