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.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
feat(ibm): build the Agent Connect listing pack and the IBM co-marketing kit
nirholasf6574814622e
diff --git a/docs/partners/ibm-partner-plus.md b/docs/partners/ibm-partner-plus.mdindex 146581e0d..b42d55e73 100644--- a/docs/partners/ibm-partner-plus.md+++ b/docs/partners/ibm-partner-plus.md@@ -94,7 +94,7 @@ engineering. So BYOL first, paid listing later if the volume justifies the paper| Supported auth (OAuth2 without Dynamic Client Registration, API key, bearer, basic, key-value) | **Satisfied with no code change.** Our OAuth advertises a `registration_endpoint`, but it also supports `client_secret_basic` and `client_secret_post`, so IBM gets a pre-registered static client and never touches DCR || Test credentials that stay valid through onboarding | We can mint these; they must be tracked so they are not rotated mid-review || Setup documentation plus at least one use case | Have it: [`docs/mcp-3d-studio.md`](../mcp-3d-studio.md), [`docs/mcp-studio.md`](../mcp-studio.md) |-| Square icon, max 200x200 | Producible from the existing brand kit in [`marketing/brand`](../../marketing/brand) |+| Listing icon | **Built and verified.** IBM requires SVG only, transparent background, under 200 KB, legible at 48x48. A PNG fails validation. Shipped at `public/partners/ibm/three-ws-agent-connect-icon.svg` || `APP_ID` from the IBM Ecosystem team | **The only true blocker.** Obtained by emailing `[email protected]` || IBM Cloud account, Concierge access | Owner action |@@ -177,13 +177,22 @@ IBM's ecosystem team something new to co-market.**Engineering (unblocked, no external dependency):**-1. Build `marketing/ibm-partner-plus/` to the shape of `marketing/openai-select-partner/`:- README, badge rules, social copy, and the no-endorsement language carried over verbatim.-2. Produce the 200x200 square listing icon from the brand kit.-3. Write the listing copy and the single required use case, reusing- [`docs/mcp-3d-studio.md`](../mcp-3d-studio.md).-4. Provision and document a durable IBM QA credential, flagged so rotation does not kill it- mid-review.+Done on 2026-09-10, all of it in [`marketing/ibm-partner-plus/`](../../marketing/ibm-partner-plus/README.md):++1. The kit itself, built to the shape of `marketing/openai-select-partner/`, with the+ no-endorsement rules carried over.+2. The catalog icon, `public/partners/ibm/three-ws-agent-connect-icon.svg`. IBM's spec is+ SVG with a transparent background, so the shipped 3D Studio mark could not be reused+ as-is: its dark rounded background plate is the exact thing the guidelines reject.+3. The full submission pack in+ [`agent-connect-listing.md`](../../marketing/ibm-partner-plus/agent-connect-listing.md):+ every Concierge field, the required use case, and the verified support, EULA, and+ documentation URLs.+4. The QA credential requirements, including the rotation trap that would silently fail+ IBM's connection test during the 3-week release window.++Held until the listing is live: the announcement copy in+[`social-copy.md`](../../marketing/ibm-partner-plus/social-copy.md).**Explicitly not doing:** the infrastructure resale incentive, IBM Software Quoting, andthe Confluent track. None of them are reachable from a Build track partner and none of themdiff --git a/marketing/README.md b/marketing/README.mdindex 77963fddd..b77b86779 100644--- a/marketing/README.md+++ b/marketing/README.md@@ -5,6 +5,7 @@ Campaign assets for three.ws announcements and distribution: video scripts and r| Campaign | Description || --- | --- || [huggingface-article](huggingface-article/post.md) | The X thread announcing the second Hugging Face community article and thanking every program and partner named in it, with the tagging rules each one requires. |+| [ibm-partner-plus](ibm-partner-plus/README.md) | The IBM Partner Plus kit: the Agent Connect BYOL submission pack for listing the 3D Studio MCP server in the watsonx Orchestrate Agent Catalog, the catalog icon, the claims we may and may not make, and held announcement copy. || [imessage-video](imessage-video/README.md) | A 9:16 vertical video of a fake iMessage thread that lands the AR Forge and OpenAI collaboration beats, built for X, TikTok, and Reels. || [nvidia-inception](nvidia-inception/README.md) | The NVIDIA Inception announcement pack: paste-ready X, LinkedIn, and Telegram copy for a membership that was never announced, plus the badge and no-endorsement rules. || [openai-select-partner](openai-select-partner/README.md) | The OpenAI Select Partner announcement pack: draft press release, approved social copy, badge assets, and the usage rules that govern them. |diff --git a/marketing/ibm-partner-plus/README.md b/marketing/ibm-partner-plus/README.mdnew file mode 100644index 000000000..890a7e81e--- /dev/null+++ b/marketing/ibm-partner-plus/README.md@@ -0,0 +1,36 @@+# IBM Partner Plus kit++Assets and copy for three.ws as an **IBM Business Partner**, and the submission pack for+listing the three.ws 3D Studio MCP server in the **watsonx Orchestrate Agent Catalog**+through IBM Agent Connect.++This kit exists because IBM co-marketing kept being improvised per event while OpenAI,+NVIDIA, and QuickNode each had a standing pack. The benefits audit that produced it is+[`docs/partners/ibm-partner-plus.md`](../../docs/partners/ibm-partner-plus.md).++| File | What it is | Status |+| --- | --- | --- |+| [`agent-connect-listing.md`](agent-connect-listing.md) | The Agent Connect BYOL submission pack: every Concierge field filled in, the required use case, the QA credential plan | Ready to submit once IBM issues the `APP_ID` |+| [`badge-usage.md`](badge-usage.md) | What marks exist, what we may and may not claim, and the no-endorsement language that is mandatory | Ready |+| [`social-copy.md`](social-copy.md) | Paste-ready X, LinkedIn, and Telegram copy for the catalog listing going live | Hold until the listing is live |++## The listing icon++IBM's catalog icon spec is **SVG only, transparent background, under 200 KB**, and it must+read at 48x48. A PNG fails validation.++| Asset | Repo path | Public URL |+| --- | --- | --- |+| Catalog icon | `public/partners/ibm/three-ws-agent-connect-icon.svg` | `https://three.ws/partners/ibm/three-ws-agent-connect-icon.svg` |++It is the shipped 3D Studio mark (`public/three-ws-mcp-icon.svg`) with the dark rounded+background plate removed and the frame tightened to the cube, because that plate is exactly+what IBM's guidelines reject. Verified: 1,059 bytes, alpha 0 at the corner, legible at 48x48+on both white and `#161616`. Do not substitute the original; it will fail validation.++## Read this before writing any IBM-facing copy++Every framing rule in [`docs/ibm.md`](../../docs/ibm.md) applies to everything in this kit,+and [`badge-usage.md`](badge-usage.md) restates the ones that get broken most often. The+short version: three.ws is an IBM Business Partner, that is a designation and not an+endorsement, and the public `/api/ibm/*` showcase is never presented as partnership work.diff --git a/marketing/ibm-partner-plus/agent-connect-listing.md b/marketing/ibm-partner-plus/agent-connect-listing.mdnew file mode 100644index 000000000..27c69717d--- /dev/null+++ b/marketing/ibm-partner-plus/agent-connect-listing.md@@ -0,0 +1,174 @@+# Agent Connect: BYOL listing submission pack++Everything needed to list the three.ws 3D Studio MCP server in the **IBM watsonx+Orchestrate Agent Catalog**, filled in and verified. When the `APP_ID` arrives, this is a+transcription job into IBM Concierge, not a drafting job.++**Path: BYOL, not paid.** BYOL skips IBM approval and the tax, banking, and payout+paperwork, and it requires "your own license validation and management system", which our+x402 per-call settlement and OAuth scopes already are. Rationale in+[`docs/partners/ibm-partner-plus.md`](../../docs/partners/ibm-partner-plus.md).++---++## Step 0: the one blocking email++Send to **[email protected]**. Allow 2 to 3 business days.++> **Subject:** MCP APP_ID Request - three.ws+>+> Company name: three.ws+> MCP server name: three.ws 3d studio+> Submission type: BYOL+>+> Brief description: A remote MCP server that turns text prompts, images, and video into+> textured, rigged, animation-ready 3D models and returns them as inline interactive+> artifacts. Also performs remeshing, retexturing, segmentation, optimisation, and+> automatic rigging on existing models.+>+> We are an existing IBM Business Partner running IBM Granite on watsonx.ai in production.++Save the `APP_ID` from the reply. If it is ever lost, the same address retrieves it given+the server name.++---++## Step 1 and 2: the Concierge fields++### The naming trap, read before typing++Display Name accepts **lowercase `a-z`, digits, space, `/`, `(`, `)`, `.`, `-` only.**+No capitals. "three.ws 3D Studio" fails validation. Use the lowercase form below exactly.++| Field | Value |+| --- | --- |+| License type | **Create BYOL listing** |+| Product type | **MCP Server** |+| Display name | `three.ws 3d studio` |+| Name (programmatic) | auto-derived, read-only |+| Version | `1.0.0` |+| Change log | `Initial catalog listing.` |+| Domain tags (1 to 3) | **Productivity** (primary), **Sales**, **Research** |+| Language support | English |+| Application ID | the `APP_ID` from step 0 |+| Application Name | `three.ws` |+| Application icon | `public/partners/ibm/three-ws-agent-connect-icon.svg` |+| Server endpoint URL | `https://three.ws/api/mcp-3d` |+| Transport | **Streamable HTTP** |+| Authentication schema | **OAuth2** (pre-registered static client, see below) |++Domain tag reasoning: Productivity is the honest primary, since this is creative+production tooling. Sales covers product and storefront visualisation. Research covers+`capture_scene` reconstruction and the model inspection tools.++### Description (paste as-is)++> three.ws 3D Studio turns a sentence, an image, or a video into a textured,+> animation-ready 3D model, and returns it as an interactive artifact inline in the+> conversation rather than as a link to download later.+>+> Generate with text_to_3d or image_to_3d at draft, standard, or high fidelity, and poll+> generation_status until the GLB is ready. Reconstruct a real physical space from a video+> with capture_scene. Add a humanoid skeleton to any model with auto_rig_model, then drive+> it with apply_animation and pose_model from a shared clip library that works across+> Mixamo, VRM, Daz, MakeHuman, Avaturn, and custom Blender rigs without manual retargeting.+>+> Refine existing assets in place: remesh_model, retexture_model, retexture_region,+> stylize_model, segment_model, and generate_material. Analyse and ship them with+> inspect_model, optimize_model, and preview_3d. Persist a result as a durable named asset+> with save_avatar.+>+> Every generated model is a standard GLB that opens in any 3D tool and embeds on any web+> page. Licensing and billing are handled directly by three.ws.++### Authentication: why OAuth2 works with no code change++IBM supports **OAuth2 without Dynamic Client Registration**. Our authorisation server at+`https://three.ws/.well-known/oauth-authorization-server` does advertise a+`registration_endpoint`, but it also supports `client_secret_basic` and+`client_secret_post`, so IBM is issued a **pre-registered static client** and never+exercises DCR. Nothing needs to be built or changed for this listing.++Relevant scopes for the connector, from the published metadata: `avatars:read`,+`avatars:write`, `profile`, `offline_access`.++### Related links++| Link | Required | URL | Verified |+| --- | --- | --- | --- |+| Support | yes | `https://three.ws/support` | 200 |+| Terms and Conditions | yes | `https://three.ws/legal/eula` | 200 |+| Documentation | no | `https://three.ws/docs/mcp-3d-studio` | 200 |++All three checked live on 2026-09-10. The general legal index is `https://three.ws/legal`+(200) if IBM prefers the hub over the EULA directly.++---++## The required use case, for IBM QA++IBM asks for setup documentation plus at least one use case they can test. This is it, and+it exercises generation, rigging, and animation in one pass so a single run proves the+server end to end.++**"Produce a rigged, walking 3D character for a product page from one sentence."**++1. `text_to_3d` with prompt `a friendly robot shop assistant, clean white and orange+ panels, standing pose`, tier `standard`.+2. `generation_status` with the returned `job_id`, polled until it returns a GLB URL and+ an inline `<model-viewer>` artifact.+3. `auto_rig_model` on that GLB URL, which adds a humanoid skeleton.+4. `list_animations` to enumerate the clip library.+5. `apply_animation` with the rigged model and the `walk` clip.+6. `preview_3d` on the result to render it inline.++**Expected outcome:** a downloadable GLB that walks when previewed, produced from a single+sentence with no 3D software and no manual rigging. Typical wall time is a few minutes,+dominated by step 1.++---++## QA credentials: the thing that quietly breaks onboarding++IBM requires **persistent test credentials that stay valid for the whole onboarding+window**, which runs to 3 weeks of release pipeline after publish. A routine rotation+during that window silently fails IBM's connection test and reads on their side as a+broken listing.++Requirements for the credential issued to IBM:++- A dedicated OAuth client, not a reused internal one, so it can be revoked alone.+- Scoped to `avatars:read`, `avatars:write`, `profile`, `offline_access` and nothing wider.+- Exempt from routine rotation for the onboarding window, and tracked wherever rotations+ are scheduled so nobody expires it by housekeeping.+- Recorded with the issue date and the IBM contact it went to.++Never paste the secret into this file, the listing form notes, or a commit. It goes to IBM+through the Concierge connection form only.++---++## Step 3: publish, then wait++BYOL publishes without IBM approval, but it still enters the watsonx Orchestrate release+pipeline: **up to 3 weeks** before the listing appears in the catalog. Updates take the+same path, so batch changes rather than shipping them one at a time.++**Do not announce the listing until it is actually visible in the catalog.** The copy in+[`social-copy.md`](social-copy.md) is held for exactly this reason.++---++## Post-publish++- Builders discover the server in the catalog and add it to their agents themselves.+- They configure connections using the OAuth2 schema above.+- We validate licensing and handle billing directly; IBM does not meter BYOL usage.+- We provide first-line support for the server. The support URL above is the entry point.+- Adoption is reported back through IBM Ecosystem team reports; ask for them.++## Open item++The catalog icon is committed at `public/partners/ibm/three-ws-agent-connect-icon.svg` but+its public URL 404s until the next production deploy. Concierge takes a file upload rather+than a URL, so this does not block submission, but deploy before pointing IBM at the link.diff --git a/marketing/ibm-partner-plus/badge-usage.md b/marketing/ibm-partner-plus/badge-usage.mdnew file mode 100644index 000000000..4a7c83b0f--- /dev/null+++ b/marketing/ibm-partner-plus/badge-usage.md@@ -0,0 +1,61 @@+# IBM marks and claims: what we may say++Unlike the OpenAI pack, this one starts with a warning rather than a badge, because the+asset situation is different and easy to get wrong.++## We do not hold an IBM Business Partner badge in this repo++There is no IBM-supplied partner mark checked in. The file that looks like one is not one:++| File | What it actually is |+| --- | --- |+| `public/ibm-partner-logo.png` | **Ours, not IBM's.** The three.ws cube plus wordmark, 462x132, prepared at a size suited to IBM's surfaces. It contains no IBM mark. |++The IBM Partner Plus mark for Business Partners is distributed through IBM's partner+portal under IBM's own trademark guidelines. If a deck or a page needs it, get it from the+portal and follow the terms attached to it there. **Do not redraw the IBM 8-bar logo, do+not pull it off a web page, and do not generate an approximation of it.** The 8-bar is one+of the most tightly governed marks in the industry.++The one existing co-branded asset is `docs/media/ibm-x-threews-lockup.png`, produced for+the community blog post it is referenced from. Treat it as scoped to that use.++## The claims, ranked from safe to forbidden++**Safe, and verifiable today:**++- "three.ws is an IBM Business Partner."+- "three.ws agents can run on IBM Granite foundation models, served through IBM watsonx.ai."+- "three.ws runs a user group on IBM Community."++**Safe once the catalog listing is actually live, and not one day before:**++- "The three.ws 3D Studio MCP server is available in the IBM watsonx Orchestrate Agent Catalog."++**Forbidden, always:**++- Any phrasing that implies IBM endorses, certifies, recommends, or validates three.ws.+ Business Partner is a designation, not an endorsement.+- Presenting the public `/api/ibm/*` showcase as an IBM product or a partnership+ deliverable. It is an independent set of developer tools built on IBM's publicly+ available Granite models.+- Describing the `@three-ws/ibm-watsonx-mcp` npm connector as an IBM release. It is+ community-built; IBM neither operates nor endorses it.+- Referring to the dedicated three.ws page on the IBM domain, or linking it, until IBM+ ships it. As of the last update to [`docs/ibm.md`](../../docs/ibm.md) it is not live.+- "Strategic partnership" as a technical claim. It appears in syndicated press coverage,+ and a headline does not upgrade the framing on our own surfaces.++## The independence line++Any asset that places a three.ws mark near an IBM mark carries this, or wording that says+the same thing:++> three.ws is an IBM Business Partner. IBM does not endorse three.ws, and three.ws is not+> an IBM product.++## Where the rules come from++[`docs/ibm.md`](../../docs/ibm.md) is the source of truth and wins any conflict with this+file. It keeps three things deliberately distinct, and no asset in this kit may blur them:+the public showcase, the hosted watsonx.ai integration, and the open-source connector.diff --git a/marketing/ibm-partner-plus/social-copy.md b/marketing/ibm-partner-plus/social-copy.mdnew file mode 100644index 000000000..de5b94ff0--- /dev/null+++ b/marketing/ibm-partner-plus/social-copy.md@@ -0,0 +1,85 @@+# Catalog listing announcement copy++**Hold everything on this page until the listing is visibly live in the watsonx Orchestrate+catalog.** BYOL publishes without IBM approval but still takes up to 3 weeks through the+release pipeline, and announcing against a listing nobody can open is the one way to make+a genuine win look like vapour.++Every post here follows [`badge-usage.md`](badge-usage.md): Business Partner is a+designation, never an endorsement, and no IBM mark is attached to any of it.++---++## X++**Primary:**++> three.ws 3D Studio is now in the IBM watsonx Orchestrate Agent Catalog.+>+> Any agent an enterprise builds there can now generate a textured, rigged,+> animation-ready 3D model from one sentence, and get it back as something you can rotate,+> not a link to download later.+>+> Add it from the catalog. No 3D software, no rigging.++**Thread post 2, the capability:**++> What it does once connected:+>+> text or image to a textured GLB+> video to a reconstructed 3D space+> automatic humanoid rigging on any model+> a shared animation library that retargets across Mixamo, VRM, Daz, Avaturn and custom rigs+> remesh, retexture, segment, optimise+>+> All of it inline in the conversation.++**Thread post 3, the point:**++> The reason this matters: enterprise agents have been able to describe a product forever.+> Now one can hand you the product, rigged and walking, inside the same conversation where+> you asked for it.+++> **three.ws 3D Studio is now available in the IBM watsonx Orchestrate Agent Catalog.**+>+> Enterprise teams building agents in watsonx Orchestrate can add the three.ws 3D Studio+> MCP server directly from the catalog and give those agents a capability they have not+> had: turning a sentence, an image, or a video into a textured, rigged,+> animation-ready 3D model, returned as an interactive object rather than a download link.+>+> Connected agents can generate models at draft through high fidelity, reconstruct a real+> physical space from a video, add a humanoid skeleton to any model automatically, and+> drive it from a shared animation library that retargets across Mixamo, VRM, Daz,+> Avaturn, and custom Blender rigs with no manual work. Existing assets can be remeshed,+> retextured, segmented, and optimised in place.+>+> Everything it produces is a standard GLB that opens in any 3D tool and embeds on any web+> page, so the output belongs to the customer rather than to us.+>+> three.ws is an IBM Business Partner and runs IBM Granite on watsonx.ai in production.+> IBM does not endorse three.ws, and three.ws is not an IBM product.+>+> Available now in the catalog.++## Telegram++> three.ws 3D Studio just landed in the IBM watsonx Orchestrate Agent Catalog.+>+> Enterprise teams building agents on watsonx Orchestrate can now plug in 3D generation+> directly: a sentence in, a rigged and animated model out, inline.+>+> Same engine you already use on three.ws. New front door, and a large one.++---++## Wording rules for anything not on this page++- "Available in the IBM watsonx Orchestrate Agent Catalog" is accurate once live.+ "Certified by IBM", "IBM-approved", and "in partnership with IBM" are not. BYOL listings+ publish without IBM approval, so an approval claim is false on its face.+- Lead with what the customer can now do, not with the logo they will recognise.+- Never attach an IBM mark. See [`badge-usage.md`](badge-usage.md).+- The LinkedIn post carries the independence line because it names the partnership. Any+ post that names the partnership carries it too.diff --git a/public/partners/ibm/three-ws-agent-connect-icon.svg b/public/partners/ibm/three-ws-agent-connect-icon.svgnew file mode 100644index 000000000..9679f184f--- /dev/null+++ b/public/partners/ibm/three-ws-agent-connect-icon.svg@@ -0,0 +1,21 @@+<svg xmlns="http://www.w3.org/2000/svg" width="200" height="200" viewBox="10 10 44 44" role="img" aria-label="three.ws 3D Studio">+ <defs>+ <linearGradient id="top" x1="32" y1="10" x2="32" y2="32" gradientUnits="userSpaceOnUse">+ <stop offset="0" stop-color="#7DD3FC"/>+ <stop offset="1" stop-color="#38BDF8"/>+ </linearGradient>+ <linearGradient id="left" x1="14" y1="22" x2="32" y2="54" gradientUnits="userSpaceOnUse">+ <stop offset="0" stop-color="#2563EB"/>+ <stop offset="1" stop-color="#1E40AF"/>+ </linearGradient>+ <linearGradient id="right" x1="50" y1="22" x2="32" y2="54" gradientUnits="userSpaceOnUse">+ <stop offset="0" stop-color="#0EA5E9"/>+ <stop offset="1" stop-color="#0369A1"/>+ </linearGradient>+ </defs>+ <g stroke="#0B0E13" stroke-width="1.25" stroke-linejoin="round">+ <path d="M32 11 L51 21.5 L32 32 L13 21.5 Z" fill="url(#top)"/>+ <path d="M13 21.5 L32 32 L32 53 L13 42.5 Z" fill="url(#left)"/>+ <path d="M51 21.5 L32 32 L32 53 L51 42.5 Z" fill="url(#right)"/>+ </g>+</svg>