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(openai): publish the partner announcement copy and the visibility map

nirholascb9af5cd227b
diff --git a/api/openapi-json.js b/api/openapi-json.js
index 172f3f9b9..a4d255f1d 100644
--- a/api/openapi-json.js
+++ b/api/openapi-json.js
@@ -14,6 +14,7 @@
import { env } from './_lib/env.js';
import { cors, json, method, wrap } from './_lib/http.js';
import { providerCatalog } from './v1/_providers.js';
+import { PAID_SERVICES } from './_lib/service-catalog/services/index.js';
// Single source of truth for the protocol list on every paid operation. Each
// entry is one supported payment protocol; per-network payment lanes (Base /
@@ -129,6 +130,88 @@ function aggregatorPaths() {
return paths;
}
+// Every paid /api/x402/* operation, projected from the service catalog
+// (api/_lib/service-catalog/services/), which is already the written-once
+// source of truth the x402 discovery doc and the OKX storefront render from.
+//
+// Why this exists: the operations below used to be hand-authored one by one,
+// and 24 of the catalog's 75 live paid services ever got an entry. That is not
+// cosmetic. x402scan registers an origin by reading THIS document, and
+// AgentCash's validator reads payable operations from it too, so a service
+// missing here is a service neither directory can list no matter how valid its
+// live 402 challenge is (measured 2026-09-02: 52 live paid endpoints answered a
+// spec-valid 402 in production while being absent from both this document and
+// the x402scan origin listing).
+//
+// The projection is spread BEFORE the hand-authored paths, so any route with a
+// richer hand-written operation keeps it verbatim and this only fills the gaps.
+function catalogPaidPaths() {
+ const paths = {};
+ for (const service of PAID_SERVICES) {
+ if (service.free || service.status !== 'live') continue;
+ // Same gate the hand-authored permit2 entry below applies: the Permit2-only
+ // lane is unpayable without CDP credentials, so never advertise it then.
+ if (
+ service.acceptsBuilder === 'permit2-only' &&
+ !(env.CDP_API_KEY_ID && env.CDP_API_KEY_SECRET)
+ )
+ continue;
+
+ const operation = {
+ operationId: `x402_${service.slug.replace(/-/g, '_')}`,
+ security: PAYMENT_ONLY_SECURITY,
+ summary: `Paid: ${service.title}`,
+ description: service.description,
+ responses: {
+ 200: { description: `${service.serviceName} result JSON` },
+ 400: { description: 'Validation error' },
+ 402: { description: 'Payment Required (x402)' },
+ },
+ 'x-payment-info': {
+ price: { mode: 'fixed', currency: 'USD', amount: formatUsd(service.priceAtomics) },
+ protocols: X402_PROTOCOLS,
+ },
+ };
+
+ if (service.method === 'POST') {
+ operation.requestBody = {
+ required: true,
+ content: {
+ 'application/json': {
+ schema: service.inputSchema,
+ ...(service.input !== undefined ? { example: service.input } : {}),
+ },
+ },
+ };
+ } else {
+ operation.parameters = queryParameters(service.inputSchema);
+ }
+
+ paths[service.path] = { [service.method.toLowerCase()]: operation };
+ }
+ return paths;
+}
+
+// A catalog descriptor's JSON Schema, flattened into OpenAPI query parameters.
+// The per-property `description` moves up to the parameter (where tooling shows
+// it) and the rest of the property schema rides along as the parameter schema,
+// so enums, formats and defaults survive into the document.
+function queryParameters(inputSchema) {
+ const properties = inputSchema?.properties || {};
+ const required = new Set(inputSchema?.required || []);
+ return Object.entries(properties).map(([name, propertySchema]) => {
+ const { description, ...schema } = propertySchema || {};
+ return {
+ name,
+ in: 'query',
+ required: required.has(name),
+ schema: Object.keys(schema).length ? schema : { type: 'string' },
+ ...(description ? { description } : {}),
+ };
+ });
+}
+
+
export default wrap(async (req, res) => {
if (cors(req, res, { methods: 'GET,OPTIONS', origins: '*' })) return;
if (!method(req, res, ['GET'])) return;
@@ -214,6 +297,9 @@ export default wrap(async (req, res) => {
// today: aggregator paths live under /api/v1/x/*, hand-authored
// paths don't).
...aggregatorPaths(),
+ // Projected from the service catalog, spread before the hand-authored
+ // operations below so a richer hand-written entry always wins.
+ ...catalogPaidPaths(),
'/api/mcp': {
post: {
operationId: 'mcp_call',
diff --git a/blog/index.html b/blog/index.html
index 7236bf397..d7e4f551a 100644
--- a/blog/index.html
+++ b/blog/index.html
@@ -102,7 +102,7 @@
<span class="bl-tag">ChatGPT</span>
</div>
<h2 class="bl-title">three.ws Named an OpenAI Select Partner</h2>
- <p class="bl-summary">three.ws joins the OpenAI Partner Network at the Select tier. What that sits on top of: a free, keyless 3D Studio MCP connector for ChatGPT with nine tools, interactive models rendered inline in the conversation, custom GPT Actions, one-tap AR on iOS and Android, and Spatial MCP, the open CC0 response shape for returning a live 3D scene as a tool result.</p>
+ <p class="bl-summary">three.ws joins the OpenAI Partner Network at the Select tier. What that sits on top of: a free, keyless 3D Studio MCP connector for ChatGPT with eleven tools, interactive models rendered inline in the conversation, custom GPT Actions, one-tap AR on iOS and Android, and Spatial MCP, the open CC0 response shape for returning a live 3D scene as a tool result.</p>
</a>
</li>
diff --git a/docs/nvidia-forum-browser-digital-human.md b/docs/nvidia-forum-browser-digital-human.md
new file mode 100644
index 000000000..4dcacac4d
--- /dev/null
+++ b/docs/nvidia-forum-browser-digital-human.md
@@ -0,0 +1,80 @@
+---
+venue: NVIDIA Developer Forums (community showcase)
+account: three.ws (official)
+suggested_title: "A digital human in a browser tab: streaming Audio2Face-3D onto whatever rig the visitor brought"
+description: "How three.ws drives real-time facial animation on a WebGL avatar from NVIDIA Audio2Face-3D over NVCF gRPC, with Magpie TTS in front and Riva ASR behind it, and how we map an ARKit-52 blendshape track onto VRM and Oculus rigs that were never built for it. Measured latencies from production."
+tags: [ace, audio2face, riva, magpie, nim, digital-humans, webgl, inception]
+canonical: https://three.ws/docs/nvidia-forum-browser-digital-human.md
+status: draft, owner approval required before posting (external-channel gate in CLAUDE.md)
+---
+
+# A digital human in a browser tab
+
+I run [three.ws](https://three.ws). You type a sentence, a rigged 3D character appears, and then it talks to you. I have written here twice before: once about [Nemotron in front of the text-to-3D generator](https://forums.developer.nvidia.com/t/how-nemotron-made-three-ws-text-to-3d-pipeline-usable/376445), once about [NIM driving a 100-language i18n pipeline](https://forums.developer.nvidia.com/t/how-three-ws-translates-a-web-app-into-100-languages-with-nvidia-nim-an-llm-powered-i18n-pipeline/377379). This one is about the face.
+
+Audio2Face-3D is usually shown inside Unreal or Omniverse Kit, driving a character somebody built on purpose. We run it in a browser tab, with no install and no engine, driving a character the visitor generated ninety seconds earlier from a text prompt. That second constraint turned out to be the whole problem: the avatar's rig is not ours, and we do not get to pick its blendshape convention.
+
+Live, no signup: [three.ws/demos/audio2face](https://three.ws/demos/audio2face). Everything below is checkable in the [open-source repository](https://github.com/nirholas/three.ws).
+
+## The loop
+
+Three NVIDIA-hosted models on one face, all reached with one `nvapi-` key:
+
+- **Riva ASR** takes the visitor's microphone audio and returns text ([api/_lib/asr-nvidia.js](https://github.com/nirholas/three.ws/blob/main/api/_lib/asr-nvidia.js)).
+- **Nemotron**, through the NIM APIs, writes the reply, with NemoGuard content safety on any publicly reachable agent.
+- **Magpie TTS multilingual** speaks it, nine languages, personas held constant across languages so a character keeps its voice when it switches ([api/_lib/tts-nvidia.js](https://github.com/nirholas/three.ws/blob/main/api/_lib/tts-nvidia.js)).
+- **Audio2Face-3D** turns that exact audio into a per-frame blendshape track ([api/_lib/a2f-nvidia.js](https://github.com/nirholas/three.ws/blob/main/api/_lib/a2f-nvidia.js)).
+
+All four are NVCF gRPC functions on `grpc.nvcf.nvidia.com:443`, selected by a `function-id` metadata entry with the key as a bearer `authorization` entry. Magpie has no REST surface at all, so gRPC is not a preference here, it is the only door.
+
+One wrinkle worth passing on if you are calling NVCF from a serverless runtime: our `api/` handlers are esbuild-bundled in place, so a `.proto` file does not reliably exist on the filesystem at call time. We vendor the ACE and Riva protos and load them from a generated JSON descriptor instead. Three separate descriptors, because the ASR, TTS, and A2F services do not share one.
+
+## The audio contract, and the resampling trap
+
+A2F-3D is trained on 16 kHz mono 16-bit PCM. Magpie emits 44.1 kHz. So the server decodes the WAV, downmixes to mono by averaging (summing gives you a free 6 dB of clipping), and resamples to 16 kHz with linear interpolation. Speech feature extraction does not need a windowed-sinc kernel to hold formant cues, and we could not hear or measure a difference in the resulting track.
+
+The trap is what you play back. It is tempting to hand the browser the 16 kHz copy you already made, because it is right there. Do not: the visitor then hears a downsampled voice for no reason. A2F returns time codes in **seconds from clip start**, independent of the sample rate it consumed, so the browser plays the original 44.1 kHz Magpie audio and samples the track by the audio element's `currentTime`. The lips track the real voice, not the copy you fed the model.
+
+The service is a bidirectional stream (`nvidia_ace.services.a2f_controller.v1.A2FControllerService/ProcessAudioStream`): client sends an audio header, PCM chunks, and an end-of-audio marker; server sends an animation header carrying the ordered blendshape names, then animation-data frames. 30 inferences per second of audio, so 30 fps out.
+
+## Measured, against production, today
+
+One line of speech, 4.64 seconds of audio, from the public endpoint:
+
+| Path | Round trip |
+|---|---|
+| Audio in, animation out (`POST /api/a2f` with a WAV) | 1.29 s, 1.31 s, 2.26 s |
+| Text in, speech and animation out (Magpie then A2F, one call) | 1.88 s, 3.35 s, 3.41 s |
+
+So A2F-3D animates a 4.6 second clip in roughly a third of its duration, and Magpie adds around 0.6 to 1.1 seconds on top. The returned track is 140 frames at 30 fps carrying **55** blendshape weights: the ARKit-52 set plus three tongue shapes. Sixty seconds of audio is our hard ceiling per request, which is about 1.9 MB of PCM and 1800 frames, generous for a line of avatar dialogue and small enough that one request cannot pin a serverless instance.
+
+## The part nobody warns you about: the visitor's rig
+
+Our avatars come from a text prompt, a photo, or a GLB the visitor uploaded from somewhere else entirely. That means the face we have to drive might expose ARKit-52 morphs, or VRoid's vowel shapes, or Meta's `viseme_*` set, or nothing usable at all. A2F speaks ARKit. Half of the web does not.
+
+We had already solved the same shape of problem for skeletons: [glb-canonicalize.js](https://github.com/nirholas/three.ws/blob/main/src/glb-canonicalize.js) maps Mixamo, Avaturn, Unreal, VRM, Daz, MakeHuman and plain `.L` bone conventions onto one canonical rig so the animation library retargets onto anything humanoid. The face version lives in [src/voice/arkit-blendshapes.js](https://github.com/nirholas/three.ws/blob/main/src/voice/arkit-blendshapes.js) and [src/voice/a2f-player.js](https://github.com/nirholas/three.ws/blob/main/src/voice/a2f-player.js), and it runs in two modes per mesh:
+
+**Direct.** The morph name canonicalizes to an ARKit shape (`jawOpen`, `JawOpen`, `jaw_open`, and the RPM, Avaturn, and MetaHuman spellings all land on the same canonical name). The A2F weight is written straight to it.
+
+**Derived.** The mesh only has monolithic expressions: VRM's `Aa`, `Ih`, `Ou`, `Ee`, `Oh`, or Oculus's `viseme_PP`, `viseme_FF`, `viseme_CH`. We hold a forward map from each of those to its ARKit components (20 VRM entries, 15 Oculus entries), and at playback we run that map **backwards**: an expression's activation is the normalized sum of the ARKit weights it is made of, taken from the A2F frame. A rig that only knows five vowels still lip-syncs, because the vowel is reconstructed out of the ARKit frame rather than looked up from a phoneme we never received.
+
+Two details that only show up once you run this on real uploads:
+
+1. If a mesh already has direct mouth coverage, do not also drive its vowel morphs. Both fire, both open the jaw, and the lips visibly overshoot. We check for direct mouth or jaw coverage first and skip the derived pass on that mesh.
+2. A2F gives you 30 fps and a browser paints at 60 or 120. Interpolate between frames by the audio clock rather than holding the last frame, or the mouth reads as stepped at exactly the moment a viewer is looking at it.
+
+And there is no allowlist. A rig we cannot map is reported as "no coverage" and the caller falls back to in-browser amplitude lipsync. A face that moves approximately is worth a great deal more than a face frozen in bind pose, and the failure has to be graceful because we cannot audit every GLB on the internet in advance.
+
+## Operational notes
+
+**Function ids rotate, and they fail closed.** Our A2F default used to be the "James" id from NVIDIA's own sample client. It stopped resolving with `NOT_FOUND: Function ... not found for account`, and the whole lipsync lane started returning 502. The fix is not clever, it is procedural: keep a `--list` script that enumerates `GET api.nvcf.nvidia.com/v2/nvcf/functions` so you can see which ids your key actually resolves, pin the constant, and allow a per-deployment override env var. Riva ASR we never pin at all, because which hosted recognizer a deployment wants genuinely varies (Parakeet CTC, RNN-T, Canary), and an unset id reports the lane as absent instead of guessing one.
+
+**One error vocabulary across all three lanes.** gRPC status codes are normalized numerically (not by importing the grpc-js constants) into `invalid_key`, `rate_limited`, `invalid_argument`, `timeout`, `provider_unreachable`, `provider_error`, `not_configured`, identically in the ASR, TTS, and A2F modules. When a face stops moving at 2 a.m. you want to know whether the key died or the deadline blew, from the same field name in all three.
+
+**The lane is additive by construction.** With no `NVIDIA_API_KEY` set, the avatar still speaks and still moves its mouth, just with the amplitude fallback. Nothing in the product hard-depends on the A2F path, which is what made it safe to ship at all.
+
+## Why the browser mattered
+
+The reason to do this in WebGL instead of an engine is distribution. Our whole embed surface is one script tag: `<agent-3d>` on any page, and the avatar on that page listens with Riva, thinks with Nemotron, speaks with Magpie, and moves its face from Audio2Face-3D. No plugin, no download, no runtime for the site owner to install. The bodies themselves come off our own NVIDIA GPU fleet on Cloud Run, mostly L4s with one RTX PRO 6000 Blackwell for the heavy image-to-3D lane, which I wrote about separately.
+
+Happy to go deeper on any of it, particularly the derived-blendshape path, which I have not seen written up anywhere and which took the longest to get right. three.ws is an NVIDIA Inception member.
diff --git a/docs/nvidia-visibility-map.md b/docs/nvidia-visibility-map.md
index 8ec7e7c97..5b41e2c10 100644
--- a/docs/nvidia-visibility-map.md
+++ b/docs/nvidia-visibility-map.md
@@ -55,9 +55,10 @@ Everything here can be done today. Nothing waits on NVIDIA, a build, or a date.
| 3 | **Portal product record correction** | `programs.nvidia.com/phoenix/application` | Gates the Showcase AND the Apps Catalog. Already specified in [nvidia-apps-catalog-listing.md](./nvidia-apps-catalog-listing.md) step 1. Nothing else in this doc lands well while the record says "CUDA consumer". |
| 4 | **Inception Startup Showcase** | `[email protected]` | NVIDIA's own wording is "member spotlights and story opportunities". Curated from the portal record, so do #3 first. |
| 5 | **AI Podcast guest nomination** | Embedded form at [ai-podcast.nvidia.com](https://ai-podcast.nvidia.com) | Free, one form, and a founder-shaped story. Fields: name, business email, organization, industry, job title, location, preferred language, and a description of the proposal. |
-| 6 | **NVIDIA Developer Forums, post 3** | [forums.developer.nvidia.com](https://forums.developer.nvidia.com) | We are 2 for 2 on posts that landed. This is the one channel with a proven track record, and it is self-serve. See [Technical publishing](#technical-publishing-the-proven-channel). |
+| 6 | **NVIDIA Developer Forums, post 3** | [forums.developer.nvidia.com](https://forums.developer.nvidia.com) | We are 2 for 2 on posts that landed. This is the one channel with a proven track record, and it is self-serve. **Drafted 2026-09-02: [nvidia-forum-browser-digital-human.md](./nvidia-forum-browser-digital-human.md).** Owner-gated on the external-channel rule, then paste and post. See [Technical publishing](#technical-publishing-the-proven-channel). |
| 7 | **NVIDIA Developer Discord** | [discord.com/invite/nvidiadeveloper](https://discord.com/invite/nvidiadeveloper) | NVIDIA engineers and product staff are in there. The browser Audio2Face demo is a conversation starter with the actual ACE team, not a marketing ask. |
| 8 | **Fix `docs/listings.md`** | Ours | The "Startup & Credit Programs" table lists Quicknode and Google Cloud and has **no NVIDIA row at all**, which is the one canonical place a reader looks for our program memberships. Fixed in this change. |
+| 9 | **"Maximize Your Membership" benefits webinar** | Region registration from the Inception member mailer (Americas / EMEA / APAC) | Announced to members 2026-09-02. NVIDIA's own walkthrough of requesting and managing benefits through the portal, which is the exact mechanism gating items 2, 3 and 4 on this list. Attend it before sending the batched email, and use the Q&A to ask the co-marketing and Showcase questions live rather than waiting on an inbox. |
## Tier 2: needs a build first
@@ -88,6 +89,14 @@ dates as unconfirmed until NVIDIA states them, but treat the **submission window
as imminent**: for a March event, recent cycles opened submissions in the summer
and closed in early fall, which is the month we are in.
+**Re-checked 2026-09-02.** Still closed: the call-for-submissions page carries the
+same GTC 2026 "now closed" copy, and no 2027 CFP or registration has opened.
+Third-party trackers have converged on **2027-03-15 to 2027-03-18, San Jose**,
+one day later than the dates recorded above, which is a reminder that none of
+these dates are NVIDIA-stated yet. Nothing to submit to this week. Keep the
+weekly watch running; the abstracts in step 2 below are what should be written
+while the window is shut.
+
Actions, in order:
1. **Put [nvidia.com/gtc/call-for-submissions](https://www.nvidia.com/gtc/call-for-submissions/)
@@ -219,6 +228,8 @@ Recorded so the next person does not repeat the search.
| All Inception matters, Showcase, co-marketing, GTC pavilion | `[email protected]` |
| China-based startups (not us, recorded for completeness) | `[email protected]` |
| Member portal | `programs.nvidia.com/phoenix/application` |
+| Live phone support (Mon to Fri, 8:00 to 17:00 PT) | +1 (408) 486-2056 |
+| Program FAQ and benefits webinar registration | Linked from the Inception member mailer; region-specific (Americas, EMEA, APAC) |
One thread, one address. Every ask in Tier 1 goes to the same inbox, so batch
them into a single email rather than sending four.
@@ -236,6 +247,8 @@ record, save it, then send and stamp the date in the request doc.
| Claim | Checked how | Result |
|---|---|---|
| GTC 2026 CFP closed; 2027 is next | Fetched [call-for-submissions](https://www.nvidia.com/gtc/call-for-submissions/) | "now closed" for GTC 2026; NVIDIA's FAQ page already titled GTC San Jose 2027 |
+| GTC 2027 CFP still shut (2026-09-02) | Re-fetched the same page, plus a search across event trackers | Same "now closed" GTC 2026 copy; no 2027 CFP or registration open; trackers report 2027-03-15 to 2027-03-18 San Jose |
+| A2F lane live and its latency (2026-09-02) | Three POSTs each to `https://three.ws/api/a2f`, audio-in and text-in | 200 on all six; 4.64 s of speech animates in 1.29 to 2.26 s, text-to-speech-to-animation in 1.88 to 3.41 s; 140 frames at 30 fps, 55 blendshapes |
| Inception benefit wording | Fetched [nvidia.com/en-us/startups](https://www.nvidia.com/en-us/startups/) | Quoted verbatim above |
| Social handles | Fetched [NVIDIA social directory](https://www.nvidia.com/en-us/contact/social/) | Full list; the table above is the topic-relevant subset |
| AI Podcast guest form | Fetched [ai-podcast.nvidia.com](https://ai-podcast.nvidia.com) | Embedded "Submit Guest Ideas" form, fields recorded above |
diff --git a/docs/openai-community-3d-studio-post.md b/docs/openai-community-3d-studio-post.md
index 79a8a6cd8..6113493aa 100644
--- a/docs/openai-community-3d-studio-post.md
+++ b/docs/openai-community-3d-studio-post.md
@@ -14,7 +14,7 @@ ChatGPT has two integration models with different strengths, so the 3D lane ship
### 1a. The ChatGPT app (Apps SDK / MCP connector)
-The connector is a Streamable HTTP MCP server at `https://three.ws/api/mcp-studio` (MCP protocol `2025-06-18`, JSON-RPC 2.0 over POST, no auth). It exposes exactly ten tools, deliberately scoped to 3D generation only: no wallet, no payments, no token, nothing a store reviewer would need to think twice about.
+The connector is a Streamable HTTP MCP server at `https://three.ws/api/mcp-studio` (MCP protocol `2025-06-18`, JSON-RPC 2.0 over POST, no auth). It exposes exactly eleven tools, deliberately scoped to 3D generation only: no wallet, no payments, no token, nothing a store reviewer would need to think twice about.
- Six generation tools: `forge_free` (text to 3D), `text_to_avatar` (text to a rigged humanoid), `mesh_forge`, `rig_mesh` (add a skeleton to a static GLB you already have), `forge_avatar`, and `refine_model` (iterate on a previous result; every refinement is its own version with its own AR link).
- One collector, `check_job`, which picks up a generation that outran the tool call.
@@ -153,7 +153,7 @@ One practical detail that bit me more than once: most three.ws avatars ship with
### 2c. The 3D Studio MCP server (the paid, full-pipeline twin)
-Beyond the ten free tools, the full pipeline is exposed as a second MCP server at `https://three.ws/api/mcp-3d` (OAuth 2.1 against the same authorization server as the main MCP endpoint, or x402 pay-per-call). The tools compose into one flow, each step's output feeding the next:
+Beyond the eleven free tools, the full pipeline is exposed as a second MCP server at `https://three.ws/api/mcp-3d` (OAuth 2.1 against the same authorization server as the main MCP endpoint, or x402 pay-per-call). The tools compose into one flow, each step's output feeding the next:
```
direct_prompt ─▶ text_to_3d ─┐
diff --git a/docs/partners.md b/docs/partners.md
index 3029d2078..28057cdba 100644
--- a/docs/partners.md
+++ b/docs/partners.md
@@ -27,7 +27,7 @@ The page's stat bar reads 8 partners, 22 chains, and an infinity glyph for scale
## OpenAI
-**What the page claims.** three.ws is an OpenAI Select Partner in the OpenAI Partner Network. The free three.ws 3D Studio connector gives ChatGPT nine keyless 3D tools: text to model, rigged avatars, conversational refinement, and a living agent body, all rendered interactively inline in the conversation. Card tags: Apps SDK, MCP, Custom GPT, Spatial MCP.
+**What the page claims.** three.ws is an OpenAI Select Partner in the OpenAI Partner Network. The free three.ws 3D Studio connector gives ChatGPT eleven keyless 3D tools: text to model, rigged avatars, conversational refinement, model inspection, and a living agent body, all rendered interactively inline in the conversation. Card tags: Apps SDK, MCP, Custom GPT, Spatial MCP.
**What the integration is.**
diff --git a/docs/press-kit.md b/docs/press-kit.md
index 432d15921..114d9b8d6 100644
--- a/docs/press-kit.md
+++ b/docs/press-kit.md
@@ -93,7 +93,7 @@ Approved descriptions at four lengths. Copy them verbatim; they are written to b
**Long, about 100 words**
-> three.ws is an open-source platform for 3D AI agents. It turns a text prompt into a rigged, animation-ready 3D character, gives that character an on-chain identity and a payment rail, and embeds it into any website or assistant with a single tag. The free 3D generation lane requires no account, no API key, and no payment. Assistants reach the same tools over MCP: three.ws is an OpenAI Select Partner, and its 3D Studio connector gives ChatGPT nine keyless tools that generate, rig, animate, and place models in AR, rendered inline in the conversation. The viewer, the runtime, and the embeddable web component are open source.
+> three.ws is an open-source platform for 3D AI agents. It turns a text prompt into a rigged, animation-ready 3D character, gives that character an on-chain identity and a payment rail, and embeds it into any website or assistant with a single tag. The free 3D generation lane requires no account, no API key, and no payment. Assistants reach the same tools over MCP: three.ws is an OpenAI Select Partner, and its 3D Studio connector gives ChatGPT eleven keyless tools that generate, rig, animate, inspect, and place models in AR, rendered inline in the conversation. The viewer, the runtime, and the embeddable web component are open source.
**Full bio, about 330 words**
@@ -105,7 +105,7 @@ Approved descriptions at four lengths. Copy them verbatim; they are written to b
>
> Agents on three.ws are economic actors. Each one can hold an on-chain identity on Solana, the platform's home chain, carry a wallet and a human-readable name, and pay or get paid by other agents per API call over x402, the HTTP 402 payment standard. The platform coin, $THREE, lives on Solana.
>
-> Distribution is the point. A finished agent ships as the `<agent-3d>` web component that drops into any page, and every generation and animation tool is reachable by AI assistants over MCP. three.ws is an OpenAI Select Partner, and its 3D Studio connector gives ChatGPT nine keyless tools that generate, rig, animate, and place 3D models in AR, rendered inline in the conversation. It is also a member of NVIDIA Inception.
+> Distribution is the point. A finished agent ships as the `<agent-3d>` web component that drops into any page, and every generation and animation tool is reachable by AI assistants over MCP. three.ws is an OpenAI Select Partner, and its 3D Studio connector gives ChatGPT eleven keyless tools that generate, rig, animate, inspect, and place 3D models in AR, rendered inline in the conversation. It is also a member of NVIDIA Inception.
>
> The viewer, the agent runtime, and the web component are open source at github.com/nirholas/three.ws, and every release ships to the public changelog at three.ws/changelog. The goal is simple: as the internet gains an agent-native, three-dimensional layer, three.ws is the infrastructure it runs on.
@@ -138,7 +138,7 @@ three.ws is an OpenAI Select Partner. The two graphics on `/press` are both 3200
| File | What it is |
|---|---|
| [`social-card-announcement.png`](../public/partners/openai/social-card-announcement.png) | The announcement card. Carries the partner badge exactly as OpenAI supplied it, plus the independence line. |
-| [`social-card-studio.png`](../public/partners/openai/social-card-studio.png) | The product card: the nine tools the 3D Studio connector adds to ChatGPT. No badge, so nothing here reads as an endorsement. |
+| [`social-card-studio.png`](../public/partners/openai/social-card-studio.png) | The product card: the keyless tools the 3D Studio connector adds to ChatGPT. No badge, so nothing here reads as an endorsement. |
**The independence line, as the page states it.** The OpenAI Partner Network badge inside the announcement card is OpenAI's asset, reproduced unaltered. three.ws is an independent member of the network at the Select tier: not an OpenAI product, and not endorsed by OpenAI beyond the partner designation shown. OpenAI, ChatGPT, and the OpenAI Partner Network badge are trademarks of OpenAI.
diff --git a/marketing/openai-select-partner/cards/social-card.html b/marketing/openai-select-partner/cards/social-card.html
index 94a37c1b9..b1a84d52d 100644
--- a/marketing/openai-select-partner/cards/social-card.html
+++ b/marketing/openai-select-partner/cards/social-card.html
@@ -221,7 +221,7 @@
</div>
<h1>three.ws is an<br /><span class="gradient">OpenAI Select Partner</span>.</h1>
<p class="lede">
- 3D, natively, inside ChatGPT. <strong>Nine keyless tools</strong> turn a sentence
+ 3D, natively, inside ChatGPT. <strong>Eleven keyless tools</strong> turn a sentence
into an interactive, riggable, AR-ready model.
</p>
<div class="pipeline">
@@ -272,7 +272,7 @@
</div>
<h1>three.ws is an<br /><span class="gradient">OpenAI Partner</span>.</h1>
<p class="lede">
- 3D, natively, inside ChatGPT. <strong>Nine keyless tools</strong> turn a sentence
+ 3D, natively, inside ChatGPT. <strong>Eleven keyless tools</strong> turn a sentence
into an interactive, riggable, AR-ready model.
</p>
<div class="pipeline">
@@ -319,9 +319,11 @@
<div class="tool"><span class="n">04</span>rig_mesh</div>
<div class="tool"><span class="n">05</span>forge_avatar</div>
<div class="tool"><span class="n">06</span>refine_model</div>
- <div class="tool"><span class="n">07</span>create_agent_persona</div>
- <div class="tool"><span class="n">08</span>get_agent_persona</div>
- <div class="tool"><span class="n">09</span>persona_say</div>
+ <div class="tool"><span class="n">07</span>check_job</div>
+ <div class="tool"><span class="n">08</span>look_at_model</div>
+ <div class="tool"><span class="n">09</span>create_agent_persona</div>
+ <div class="tool"><span class="n">10</span>get_agent_persona</div>
+ <div class="tool"><span class="n">11</span>persona_say</div>
</div>
<div class="claims">
<span class="claim">Free</span>
diff --git a/marketing/openai-select-partner/partnership-and-gpt-briefing.md b/marketing/openai-select-partner/partnership-and-gpt-briefing.md
index 881200a70..dd44d2668 100644
--- a/marketing/openai-select-partner/partnership-and-gpt-briefing.md
+++ b/marketing/openai-select-partner/partnership-and-gpt-briefing.md
@@ -25,7 +25,7 @@ logo swap. three.ws ships **four live surfaces on OpenAI platforms**, all free,
all keyless, all open source:
1. **The three.ws 3D Studio connector** (Apps SDK / MCP) at
- `https://three.ws/api/mcp-studio`, ten tools, no authentication.
+ `https://three.ws/api/mcp-studio`, eleven tools, no authentication.
2. **The "three.ws 3D Studio" custom GPT**, published publicly in the GPT Store
since 2026-07-14, calling a REST Actions contract at `/api/3d/studio`.
3. **AR from the conversation**: every generation carries a one-tap
@@ -60,6 +60,8 @@ above Select.
| 2026-07-28 | Announcement graphics and the X wording decision ("OpenAI Partner" on X only) | `badge-usage.md`, `social-copy.md` |
| 2026-07-29 | Custom GPT QA pass; three builder-config defects found and fixed | `docs/chatgpt-3d-studio-gpt.md` |
| 2026-08-06 | Tier story re-verified live; docs reconciled to the ten-tool surface | `forge-free-tier-evidence.json`, `data/changelog.json` |
+| 2026-08-28 | `look_at_model` lands, taking the connector to eleven tools | `api/_mcp-studio/tools.js` |
+| 2026-09-02 | Every count, listing and announcement document reconciled to the live eleven-tool surface | `openai-submission.md`, `live-tools-list.json`, `docs/press-kit.md` |
**What the Select tier grants.** Use of the OpenAI Partner Network badge under
the rules in `badge-usage.md`, OpenAI's approved starter messaging and approved
@@ -214,12 +216,14 @@ app is anonymous and free, OpenAI's "provide a demo account with test
credentials" requirement does not apply, and the submission form says so
explicitly.
-**Ten tools**, verified live today: six generation tools (`forge_free`,
-`text_to_avatar`, `mesh_forge`, `rig_mesh`, `forge_avatar`, `refine_model`), the
-read-only `check_job` collector that picks up a generation which outran its tool
-call, and three persona tools (`create_agent_persona`, `get_agent_persona`,
-`persona_say`) that give an assistant a persistent, lip-syncing body in the
-panel.
+**Eleven tools**, verified live on 2026-09-02: six generation tools
+(`forge_free`, `text_to_avatar`, `mesh_forge`, `rig_mesh`, `forge_avatar`,
+`refine_model`), the read-only `check_job` collector that picks up a generation
+which outran its tool call, the read-only `look_at_model` inspector that renders
+a finished GLB from several angles so the assistant can check its own work before
+handing it over, and three persona tools (`create_agent_persona`,
+`get_agent_persona`, `persona_say`) that give an assistant a persistent,
+lip-syncing body in the panel.
**The inline widget** is the `<model-viewer>` skybridge component built in
`api/_mcp-studio/component.js`, resource `ui://widget/three-studio-model.html`,
@@ -255,7 +259,7 @@ PASS):
`estimated_credits`, `preview_image_url`, `reference_image_urls`. No session id,
trace id, user id, or PII. Inputs are minimal too, with
`additionalProperties: false` on every schema.
-- **Correct tool annotations** on all ten tools (read-only, destructive,
+- **Correct tool annotations** on all eleven tools (read-only, destructive,
idempotent, open-world hints), with the rationale for each documented.
- **Clear utility not native to ChatGPT.** ChatGPT cannot turn language into a
manipulable, downloadable 3D asset. That is the whole value proposition.
@@ -360,7 +364,7 @@ Probed against production today:
| `/openai` partner page | HTTP 200 |
| `/.well-known/3d-studio-openapi.yaml` | HTTP 200 |
| Badge SVG | HTTP 200 |
-| MCP `tools/list` | 200, ten tools, exactly the documented set |
+| MCP `tools/list` | 200, eleven tools, exactly the documented set |
| `GET /api/3d/studio?job=bogus123` | 400 `invalid_job` in 0.43s, correct designed error |
| `POST /api/3d/studio` (new prompt) | **No response within 100s** |
| `POST /api/3d/generate` (new prompt) | **No response within 100s** |
@@ -392,15 +396,28 @@ or configuration issue.
| Delete the draft duplicate GPT `g-6a5672fbf3f48191b559e482c7fcbf51` | Owner | Avoids confusion with the published GPT |
| Press release: fill two fields, email for OpenAI approval | Owner | [email protected], do not publish before written approval |
| Free generation submit path degraded (see §10) | Engineering | Actions deadline vs 90s-plus-retry accept window |
-| "Nine tools" drift in older copy | Engineering | See below |
-
-**The nine-versus-ten drift.** The connector shipped with five tools, grew to
-nine, and reached ten when `check_job` landed. `/openai` and `docs/mcp-studio.md`
-were reconciled to ten on 2026-08-06, but three announcement-era documents still
-say nine: `press-release.md`, `social-copy.md` (both the X and LinkedIn copy), and
-the OpenAI section of `docs/partners.md`. The press release is the one that
-matters most, because it has not been sent yet and would go out with a number
-that is now wrong. Fix all three before the release is emailed for approval.
+| ~~"Nine tools" drift in older copy~~ | Engineering | Closed 2026-09-02, see below |
+
+**The tool-count drift, closed 2026-09-02.** The connector shipped with five
+tools, grew to nine, reached ten when `check_job` landed, and reached eleven when
+`look_at_model` landed on 2026-08-28. Each growth step left a trail of stale
+numbers behind it: the 2026-08-06 pass reconciled `/openai` and
+`docs/mcp-studio.md` to ten but left the announcement-era copy at nine, and
+`look_at_model` then made both numbers wrong.
+
+Every surface that quotes a number is now reconciled against the live
+`tools/list` and says eleven: this brief, `press-release.md`, `social-copy.md`
+(X and LinkedIn), `cards/social-card.html`, `docs/partners.md`,
+`docs/press-kit.md`, `pages/press/index.html`, `blog/index.html`,
+`docs/openai-community-3d-studio-post.md`, `openai-submission.md`, `TRACKER.md`,
+the `/openai` page, and the module headers in `api/_mcp-studio/`. The press
+release is still unsent, so it now carries the correct number.
+
+The drift is also pinned mechanically now, so the next tool to land fails a test
+instead of quietly re-opening this row: `tests/mcp-studio.test.js` asserts that
+the two catalogs sum to exactly eleven. Bump that assertion and this section
+together, and re-render `public/partners/openai/social-card-studio.png` from
+`cards/social-card.html` with `npm run build:openai-cards`.
---
diff --git a/marketing/openai-select-partner/press-release.md b/marketing/openai-select-partner/press-release.md
index 9a0161b96..2bb7bc767 100644
--- a/marketing/openai-select-partner/press-release.md
+++ b/marketing/openai-select-partner/press-release.md
@@ -27,7 +27,7 @@ models and products and turn them into measurable impact.
As an OpenAI Select Partner, three.ws will continue working with OpenAI to help
organizations build, deploy, and scale AI solutions responsibly and effectively.
three.ws contributes the dimension assistants have been missing: its free 3D
-Studio connector gives ChatGPT nine keyless tools that turn a sentence into an
+Studio connector gives ChatGPT eleven keyless tools that turn a sentence into an
interactive, textured 3D model rendered inline in the conversation, then rig it,
animate it, and place it in the user's room in augmented reality.
diff --git a/marketing/openai-select-partner/social-copy.md b/marketing/openai-select-partner/social-copy.md
index 3c0d6ae2e..f95558c57 100644
--- a/marketing/openai-select-partner/social-copy.md
+++ b/marketing/openai-select-partner/social-copy.md
@@ -31,7 +31,7 @@ Attach: `social-card-openai-partner.png`
>
> What that sits on top of: assistants have been excellent at text and images for
> years and have had nothing to say in three dimensions. We're the 3D layer. Our
-> free 3D Studio connector gives ChatGPT nine keyless tools that turn a sentence
+> free 3D Studio connector gives ChatGPT eleven keyless tools that turn a sentence
> into an interactive, textured model rendered inline, rig it, animate it, and
> place it in your room in AR. No key, no account, no cost.
>
@@ -72,7 +72,7 @@ above Select.
>
> What that sits on top of: assistants have been excellent at text and images for
> years and have had almost nothing to say in three dimensions. three.ws is the 3D
-> layer. Our free 3D Studio connector gives ChatGPT nine keyless tools that turn a
+> layer. Our free 3D Studio connector gives ChatGPT eleven keyless tools that turn a
> sentence into an interactive, textured 3D model rendered inline in the
> conversation, rig it, animate it, and place it in your room in AR. No key, no
> account, no cost.
diff --git a/pages/press/index.html b/pages/press/index.html
index afd344803..eff69665b 100644
--- a/pages/press/index.html
+++ b/pages/press/index.html
@@ -255,10 +255,10 @@
</article>
<article class="prs-card">
- <img src="/partners/openai/social-card-studio.png" alt="The nine tools the three.ws 3D Studio connector adds to ChatGPT" loading="lazy" />
+ <img src="/partners/openai/social-card-studio.png" alt="The keyless tools the three.ws 3D Studio connector adds to ChatGPT" loading="lazy" />
<div class="prs-asset-body">
<p class="prs-file">social-card-studio.png</p>
- <p class="prs-when">The product card: the nine tools the 3D Studio connector adds to ChatGPT. No badge, so nothing here reads as an endorsement.</p>
+ <p class="prs-when">The product card: the keyless tools the 3D Studio connector adds to ChatGPT. No badge, so nothing here reads as an endorsement.</p>
<a class="prs-dl" href="/partners/openai/social-card-studio.png" download>
<svg viewBox="0 0 16 16" fill="none" aria-hidden="true"><path d="M8 1.5v9m0 0L4.5 7M8 10.5 11.5 7M2 13.5h12" stroke="currentColor" stroke-width="1.6" stroke-linecap="round" stroke-linejoin="round"/></svg>
Download PNG
@@ -302,7 +302,7 @@
<span class="prs-quote-k">Long, about 100 words</span>
<button class="prs-copy" type="button" data-copy="boiler-3"><span>Copy</span></button>
</div>
- <p class="prs-quote-body" id="boiler-3">three.ws is an open-source platform for 3D AI agents. It turns a text prompt into a rigged, animation-ready 3D character, gives that character an on-chain identity and a payment rail, and embeds it into any website or assistant with a single tag. The free 3D generation lane requires no account, no API key, and no payment. Assistants reach the same tools over MCP: three.ws is an OpenAI Select Partner, and its 3D Studio connector gives ChatGPT nine keyless tools that generate, rig, animate, and place models in AR, rendered inline in the conversation. The viewer, the runtime, and the embeddable web component are open source.</p>
+ <p class="prs-quote-body" id="boiler-3">three.ws is an open-source platform for 3D AI agents. It turns a text prompt into a rigged, animation-ready 3D character, gives that character an on-chain identity and a payment rail, and embeds it into any website or assistant with a single tag. The free 3D generation lane requires no account, no API key, and no payment. Assistants reach the same tools over MCP: three.ws is an OpenAI Select Partner, and its 3D Studio connector gives ChatGPT eleven keyless tools that generate, rig, animate, inspect, and place models in AR, rendered inline in the conversation. The viewer, the runtime, and the embeddable web component are open source.</p>
</div>
<div class="prs-quote">
@@ -314,7 +314,7 @@
<p>three.ws is an open-source platform that gives AI a body. It turns a text prompt, a few photos, or a sketch into a textured, rigged, animation-ready 3D character; gives that character a mind, a voice, an on-chain identity, and a payment rail; and embeds the result into any website, app, or AI assistant with a single tag. The free 3D generation lane requires no account, no API key, and no payment.</p>
<p>Every avatar is a full agent, not a static model. The runtime wraps the character around an LLM brain that listens, speaks with real-time lip-sync, gestures, remembers, and expresses emotion through the model's face and posture, live in the browser with nothing to install. Any humanoid rig works: the animation system retargets a shared motion library onto whatever skeleton a model arrives with.</p>
<p>Agents on three.ws are economic actors. Each one can hold an on-chain identity on Solana, the platform's home chain, carry a wallet and a human-readable name, and pay or get paid by other agents per API call over x402, the HTTP 402 payment standard. The platform coin, $THREE, lives on Solana.</p>
-<p>Distribution is the point. A finished agent ships as the &lt;agent-3d&gt; web component that drops into any page, and every generation and animation tool is reachable by AI assistants over MCP. three.ws is an OpenAI Select Partner, and its 3D Studio connector gives ChatGPT nine keyless tools that generate, rig, animate, and place 3D models in AR, rendered inline in the conversation. It is also a member of NVIDIA Inception.</p>
+<p>Distribution is the point. A finished agent ships as the &lt;agent-3d&gt; web component that drops into any page, and every generation and animation tool is reachable by AI assistants over MCP. three.ws is an OpenAI Select Partner, and its 3D Studio connector gives ChatGPT eleven keyless tools that generate, rig, animate, inspect, and place 3D models in AR, rendered inline in the conversation. It is also a member of NVIDIA Inception.</p>
<p>The viewer, the agent runtime, and the web component are open source at github.com/nirholas/three.ws, and every release ships to the public changelog at three.ws/changelog. The goal is simple: as the internet gains an agent-native, three-dimensional layer, three.ws is the infrastructure it runs on.</p></div>
</div>
</section>
diff --git a/public/partners/openai/social-card-announcement.png b/public/partners/openai/social-card-announcement.png
index 3c8a67ac1..d833274f3 100644
Binary files a/public/partners/openai/social-card-announcement.png and b/public/partners/openai/social-card-announcement.png differ
diff --git a/public/partners/openai/social-card-openai-partner.png b/public/partners/openai/social-card-openai-partner.png
index 472e2e64d..5c4e513e9 100644
Binary files a/public/partners/openai/social-card-openai-partner.png and b/public/partners/openai/social-card-openai-partner.png differ
diff --git a/public/partners/openai/social-card-studio.png b/public/partners/openai/social-card-studio.png
index c9525bd85..9f0ebc9bb 100644
Binary files a/public/partners/openai/social-card-studio.png and b/public/partners/openai/social-card-studio.png differ
diff --git a/public/partners/openai/three-ws-openai-lockup-dark.png b/public/partners/openai/three-ws-openai-lockup-dark.png
index fc5551e64..8ef71e346 100644
Binary files a/public/partners/openai/three-ws-openai-lockup-dark.png and b/public/partners/openai/three-ws-openai-lockup-dark.png differ
diff --git a/public/partners/openai/three-ws-openai-lockup.png b/public/partners/openai/three-ws-openai-lockup.png
index cdad6e5db..9cc3981c3 100644
Binary files a/public/partners/openai/three-ws-openai-lockup.png and b/public/partners/openai/three-ws-openai-lockup.png differ
diff --git a/scripts/audit-links.mjs b/scripts/audit-links.mjs
index f310eb44b..680ddfbd9 100644
--- a/scripts/audit-links.mjs
+++ b/scripts/audit-links.mjs
@@ -115,8 +115,10 @@ const BUILD_COPIED_ROOTS = ['blog', 'docs', 'pump-fun-skills', 'avatar-sdk'];
// Emitted at build time, so there is no source file to point at. vite-plugin-pwa
// writes the web manifest from the `manifest` block in vite.config.js, which is
-// what the 250 pages linking `/manifest.webmanifest` actually get.
-const GENERATED_TARGETS = new Set(['/manifest.webmanifest']);
+// what the 250 pages linking `/manifest.webmanifest` actually get, and
+// scripts/write-build-info.mjs writes dist/build-info.json, the static file the
+// build stamps the running commit into and /api/version reads back.
+const GENERATED_TARGETS = new Set(['/manifest.webmanifest', '/build-info.json']);
// Does a clean path resolve to a real source file (what the catch-all serves)?
function fileForCleanPath(path) {
@@ -445,11 +447,23 @@ function scanFile(file) {
// `window.open('')` opens a blank tab the caller then writes into, a real
// pattern, not a link to nowhere.
if (target === '' && /^window\.open/i.test(m[1])) continue;
+ // `{ href: '' }` in an object literal is the ABSENCE of a link, and every
+ // consumer of a link-descriptor object in this repo guards on it before
+ // rendering an anchor. That is the opposite of markup: `<a href="">` is a
+ // live element that navigates to the current URL, which is why the empty
+ // string stays a stub everywhere else. Only the object-literal form is
+ // exempt, so a real `el.href = ''` assignment is still reported.
+ if (target === '' && /href\s*:$/i.test(m[1])) continue;
if (inComment(m.index)) continue;
record(target, file, lineOf(content, m.index), concatenatedAfter(content, m.index + m[0].length));
}
fetchRe.lastIndex = 0;
while ((m = fetchRe.exec(content))) {
+ // Masked exactly like the two scanners above. This one skipped the check,
+ // so a module's own header comment explaining what NOT to call was read as
+ // a call: the line warning against raw `fetch('/api…')` was reported as a
+ // broken link to `/api…`, a path no code ever requests.
+ if (inComment(m.index)) continue;
const t = m[2] ?? m[3] ?? m[4] ?? '';
if (t.startsWith('/')) record(t, file, lineOf(content, m.index)); // only internal fetches
}