three.ws Named an OpenAI Select Partner

three.ws has been named an OpenAI Select Partner within the OpenAI Partner Network. The Partner Network is OpenAI's global program for partners building, selling, and delivering AI solutions on OpenAI models and products. three.ws joins it as the 3D layer: the piece that lets an assistant answer with something you can orbit, rig, animate, and stand in your living room.

The gap this fills

Assistants have been excellent at text and images for years and have had almost nothing to say in three dimensions. Ask for a robot mascot and you get a picture of one. That is a fine answer right up to the moment you need to animate it, print it, drop it into a game, or place it on your desk. three.ws exists to make the 3D answer ordinary: a real GLB, generated in the conversation, rendered interactively where the question was asked.

What is live today

three.ws 3D Studio, an MCP connector for ChatGPT. Nine free tools at https://three.ws/api/mcp-studio: text to 3D, text or image to avatar, art-directed mesh generation, auto-rigging, one-call rigged avatars, conversational refinement, and three persona tools that give the assistant a living, lip-syncing body in the panel. No key, no account, no wallet, no cost.
Inline, interactive results. Generations render in a model-viewer widget inside the conversation, with a declared widget CSP so models actually load in real ChatGPT rather than only in permissive test harnesses.
Custom GPT Actions. The same free lane also ships as a REST surface for the "three.ws 3D Studio" custom GPT, with an age-13+ safety gate, for plans without connector support.
One-tap AR. Every generated model carries an AR link: iOS gets a Quick Look USDZ converted on the fly from the GLB, Android gets a Scene Viewer intent, desktop falls back to the WebGL viewer.
Spatial MCP, open and CC0. An open response shape for returning a live 3D scene as a first-class tool result (scene GLB, camera, environment, animation, AR handoff) instead of a bare URL. Every three.ws generator emits it; any renderer can consume it. We would rather the ecosystem share one shape than each ship a private one.

Connect it in one line

Add it as a connector with No authentication and the URL below. From any other MCP client:

curl -s https://three.ws/api/mcp-studio \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Full contract, widget details, and the response shape are in the 3D Studio documentation. The partner page lives at three.ws/openai.

Free means free

The 3D Studio server is operator-funded and exposes 3D generation only: no payment surface, no wallet, no token, nothing to sign up for. The paid, crypto-enabled studio is a separate endpoint at /api/mcp-3d and shares none of that surface. We keep the line hard on purpose, so the free lane stays something anyone can point an assistant at.

What comes next

Wider expression range for generated avatars, and richer persona behaviour in the inline widget
More of the generation pipeline emitted as conformant Spatial MCP artifacts, so 3D results stay portable across clients
Continued work on the open standards side: the response shape, the AR handoff, and the embed component are all open source and stay that way