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(tripo): refresh brief with 2026-10-23 pricing and forge_creations counts, and draft the joint launch post for the owner

nirholasc0e5d5dcf1a9
diff --git a/docs/partners/tripo.md b/docs/partners/tripo.md
index c6fbdb58e..c219798cf 100644
--- a/docs/partners/tripo.md
+++ b/docs/partners/tripo.md
@@ -166,6 +166,48 @@ description of what shipped:
---
+## Refresh, 2026-10-23
+
+What was re-checked on this date. Anything not listed here is unchanged from the 2026-10-09
+draft above.
+
+| Item | 2026-10-23 reading | How |
+|---|---|---|
+| Tripo API pricing | Unchanged: text to 3D 10 to 20 credits, image to 3D 20 to 30, auto-rig 25, retarget 10 per animation, 1 credit = USD 0.01 | [developers.tripo3d.ai](https://developers.tripo3d.ai) fetched today |
+| API surface | v3 endpoint (`/v3/generation/text-to-model`), model `v3.1-20260211`. Listed models: H3.1, P2.0 (native quad), AI Texture, Segmentation V2 | Same page. It has no changelog or dated entries, so nothing newer than the model list can be reported |
+| Announcements since 2026-10-09 | None found. A web search surfaced no October 2026 Tripo announcement; the latest items were July 2026 funding coverage and the March 2026 H3.1 and P1.0 launch. Third-party sources disagree on some details, so those press items stay labelled as press | Web search, not an official Tripo source |
+| House key on the service | **Still absent.** `node scripts/read-service-env.mjs '^TRIPO' --names` finds no `TRIPO*` variable on `three-ws-api` | Cloud Run service env |
+| Order 084 | Closed (no `084` file in `prompts/finish`) | `ls prompts/finish` |
+
+### Tripo-family jobs, `forge_creations`, internal jobs excluded
+
+Read with a read-only SELECT against production on 2026-10-23.
+
+Last 30 days, by backend and status:
+
+| Lane | Finished | Failed |
+|---|---|---|
+| TripoSG, self-hosted (open weights) | 134 | 92 |
+| Tripo API, user's own key | 2 | 0 |
+
+Per calendar month, all Tripo-family backends:
+
+| Month | Jobs |
+|---|---|
+| 2026-07 | 32 |
+| 2026-08 | 81 |
+| 2026-09 | 99 |
+| 2026-10 (through the 23rd) | 190 |
+
+July and August match the 2026-10-09 table. September reads 99 here against 101 earlier; the
+cause was not investigated, so treat the earlier figure as the one that went into the draft.
+This query excludes `internal` rows but not the `forge_seed_jobs` catalog seeders, so for the
+wider usage claim use the audited 12,373 September figure in the
+[proof brief](./proof-brief-2026-10.md). The conclusion is unchanged: the open-weight lane
+grows each month and the paid lane is nearly unused (2 jobs).
+
+---
+
## Reply draft
Send from the owner's account to the person who reached out, copying
diff --git a/marketing/growth/submissions/tripo-launch-post.md b/marketing/growth/submissions/tripo-launch-post.md
new file mode 100644
index 000000000..f779d01c2
--- /dev/null
+++ b/marketing/growth/submissions/tripo-launch-post.md
@@ -0,0 +1,61 @@
+# Tripo x three.ws joint launch post: DRAFT FOR THE OWNER
+
+**Status: draft only. Not sent, not agreed with Tripo.** Do not publish until (1) Tripo has
+replied and agreed to co-market, (2) `TRIPO_API_KEY` is on the `three-ws-api` service, and
+(3) a production Tripo house-lane job has completed. As of 2026-10-23 none of those is true:
+no `TRIPO*` variable exists on the service, and the only paid-lane jobs in the last 30 days
+were 2 finished jobs on users' own keys. Sending or posting is the owner's step.
+
+Written only from facts checked on 2026-10-23. Sources are in
+[docs/partners/tripo.md](../../../docs/partners/tripo.md). Bracketed fields are for the owner
+to fill from the pilot once it has run; leave a bracketed field out rather than guess it.
+
+## Verified facts this post may use
+
+| Fact | Source |
+|---|---|
+| three.ws runs Tripo's v3.1 model (`v3.1-20260211`) as a Forge lane on the v3 API with signed webhooks | `api/_providers/tripo.js`, `api/forge/webhook/tripo.js` |
+| TripoSG runs self-hosted for sketch-to-3D and as the last photo failover rung; TripoSR is a rung in the free chain. Both are MIT licensed | `workers/model-triposg`, `workers/model-triposr`, Tripo's repos |
+| Last 30 days: 134 TripoSG jobs finished and 92 failed; 2 Tripo API jobs, both finished | `forge_creations`, internal jobs excluded, read 2026-10-23 |
+| Forge took 12,373 generation and rigging requests in September 2026 | audited figure, [proof brief](../../../docs/partners/proof-brief-2026-10.md) |
+| MCP servers handled 13,898 tool calls in September at 99.4% handler success from 13 distinct clients | proof brief |
+| Tripo API prices: text to 3D 10 to 20 credits, image to 3D 20 to 30, auto-rig 25, retarget 10 per animation, at USD 0.01 per credit | developers.tripo3d.ai, 2026-10-23 |
+
+Do not use: Tripo's user or funding figures (press or Tripo's own claims, unverified), any
+completion-rate or latency comparison between Tripo and other engines (no such data has been
+produced), or any deal term (none agreed).
+
+## Post draft
+
+**Title:** Tripo is now a built-in engine in the three.ws Forge
+
+Tripo already ran in three places inside three.ws: the v3.1 model as a Forge lane, TripoSG
+behind our sketch-to-3D tool, and TripoSR in the free photo-to-3D chain. Until now the v3.1
+lane only worked if you pasted your own Tripo API key.
+
+[Today it is a built-in engine on the High tier, and you can pick it by name. No key needed;
+it bills to your three.ws credits like our other engines.]
+
+What you get:
+
+- Text and image to 3D on Tripo's latest model, delivered through the v3 API with signed
+ webhooks, so jobs finish the moment Tripo says they are done.
+- [Auto-rigging with Tripo's rig endpoint: the output drives our universal retargeter, so any
+ Tripo character can play the animation library.]
+- The same engine through MCP, so agents in ChatGPT, Claude, Cursor and other clients can ask
+ for a Tripo model in a single tool call.
+
+We also keep running TripoSG and TripoSR in production, and we are glad to credit the Tripo
+research team for releasing both under MIT.
+
+[Pilot result, from the order 084 report: N jobs, completion rate X%, median time Y seconds.
+Fill from `forge_creations` after the pilot; omit if the pilot has not produced it.]
+
+Try it: [link to the Forge with the Tripo engine selected].
+
+## Notes for Tripo's review
+
+- Ask Tripo how they want the name written in the engine picker and in exports (call question
+ 5 in the brief) before publishing.
+- Each bracketed sentence describes something that is true only after the key lands. If the
+ key does not land, publish nothing.