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
docs(partners): add the outreach plan that works the prospect list wave by wave, and track the new prospects
nirholas2efe2fae8cb2
diff --git a/docs/partners.md b/docs/partners.mdindex cacb40702..d3cb64db3 100644--- a/docs/partners.md+++ b/docs/partners.md@@ -139,6 +139,7 @@ The page closes with four reasons, useful as the short pitch when someone asks:## Related+- [Partner prospects](./partners/prospects.md) and [the outreach plan](./partners/outreach-plan.md): who we approach next, and how- [Press kit](./press-kit.md): marks, announcement graphics, boilerplate, and the rules for all of it- [Listings and distribution](./listings.md): marketplaces, ecosystem directories, and media partners with per-listing status- [Integrations](./integrations.md): the catalog of ways to put an agent on a site you do not controldiff --git a/docs/partners/opportunities.md b/docs/partners/opportunities.mdindex 76cf8ace1..6785536c7 100644--- a/docs/partners/opportunities.md+++ b/docs/partners/opportunities.md@@ -9,6 +9,9 @@ does not restate the reference docs:- [Publishing program](../publishing-program-2026-09.md) is the content and venue matrix.- [OpenAI, IBM, and NVIDIA growth plan](./openai-ibm-nvidia-growth-plan.md) turns thehighest-value partner opportunities into a 30-day listing and co-marketing sequence.+- [Partner prospects](./prospects.md) is the scored list of new partners from the 2026-10-09+ sweep, and [the outreach plan](./outreach-plan.md) is how it is worked. A prospect moves+ onto this page when it gets its first action.This page is the part those three do not answer: **what is actually stuck, on whom, andwhat unblocks it.**diff --git a/docs/partners/outreach-plan.md b/docs/partners/outreach-plan.mdnew file mode 100644index 000000000..f1d4c8c81--- /dev/null+++ b/docs/partners/outreach-plan.md@@ -0,0 +1,200 @@+# Partnership outreach plan++*Written 2026-10-09 to work the [partner prospects list](./prospects.md). The prospects page+says who; this page says in what order, with what message, and who does each step. The+engineering behind each wave is a set of work orders in the `partners-` campaign+([shared context](../../prompts/finish/_context/partners-00-CONTEXT.md)), so the build can run+in parallel with the conversations.*++## The approach in one paragraph++Lead with what already runs. Almost every strong prospect on the list is something three.ws+already uses, renders, retargets or serves, so the first message is never "we would like to+partner". It is "your work already powers this, here are the numbers, here is what we can do+together". Where we depend on someone's open source and have never given back, the first move+is a contribution or a credit, not a request. Every number quoted comes from the+[30-day proof brief](./proof-brief-2026-10.md), quoted the way it says to.++## The engagement ladder++Every relationship climbs the same rungs. Do not skip one: a commercial ask to a project we+have never credited reads as extraction.++| Rung | What it means | Example |+|---|---|---|+| 1. Use | We run their work in production | TripoSG in the Forge, three-vrm in the avatar stack |+| 2. Credit | A visitor can see that we do | The open-source credits page (order 086), engine attribution in the Forge |+| 3. Contribute | We send fixes, samples or money upstream | A three-vrm pull request, a GitHub Sponsors tier |+| 4. List | We appear in their directory, registry or docs | The LiveKit avatar page, ClawHub, the HACS default store |+| 5. Co-market | A joint post, a case study, a showcase slot | A Tripo launch post when the house lane ships |+| 6. Commercial | Credits, partner pricing, revenue share, a grant | Tripo deal shapes A to C |++## Waves++Each wave starts when the one before it has begun, not when it has finished. Target dates+assume the owner can spend about two hours a week on outreach.++### Wave 0: Tripo (this week)++| Step | Who | Detail |+|---|---|---|+| Reply to Tripo with the draft in [tripo.md](./tripo.md) | Owner | Copy `[email protected]` if the first contact did not come from there |+| Build the v3 house lane behind `TRIPO_API_KEY`, BYOK unchanged | Agent, order 084 | Runnable now; nothing in it waits on the deal |+| First call, using the six questions in the brief | Owner | Start at deal shape A, the 60-day credits pilot |+| Approve the house key once terms are agreed | Owner, order 936 | A platform-paid key onboards a paid API, so it is the owner's call |++**Done when:** a signed pilot, the key on the Cloud Run service, and Tripo running as a house+lane in the Forge with its completion and latency numbers reported back to Tripo from `forge_creations`.++### Wave 1: fix before we pitch, then free listings (weeks 1 and 2)++The cheapest credibility there is, and a precondition for Waves 2 and 3.++| Step | Who | Order |+|---|---|---|+| Move the public animation library off Mixamo clips | Agent | 085 |+| Ship the open-source credits page and in-surface credits (Poly Haven on /objects, engine names in the Forge) | Agent | 086 |+| Build the tool packages and registry entries for the agent tools (AI SDK, LangChain, ADK page, skills index, OpenRouter attribution, Postman collection) | Agent | 093 |+| Open the pull requests and submit the forms for the agent registries | Owner | 938 |+| Start the sponsorships the owner approves | Owner | 937 |+| Re-tag the Sketchfab models uploaded before 2026-10-09 | Owner | 940 |++**Done when:** no "fix before we pitch" item on the prospects page is still open, and the+first ten registry entries are live.++### Wave 2: build to pitch (weeks 2 to 6)++Each of these is a working integration first and a conversation second. A partner says yes to+a demo far more often than to a proposal.++| Integration | Who builds | Who opens the door |+|---|---|---|+| LiveKit avatar plugin and Pipecat service | Agent, order 087 | Owner: plugin pull request and LiveKit Startups application (938, 939) |+| Discord Activity | Agent, order 088 | Owner: app verification and Discovery (939) |+| "Get it printed" through Craftcloud, plus slicer trusted-host patches | Agent, order 089 | Owner: Craftcloud account, Bambu and Prusa pull requests (938, 939) |+| Mocap migration landing for stranded mocap users | Agent, order 090 | Owner: announce it (938) |+| Shopify product-media app | Agent, order 091 | Owner: Partner account and App Store submission (939) |+| VRoid Hub import | Agent, order 092 | Owner: VRoid Hub app approval (939) |+| WordPress, Framer and Webflow embeds | Agent, order 094 | Owner: directory submissions (938) |+| Home Assistant HACS package | Agent, order 095 | Owner: the HACS default pull request and its CI exception (938) |++Engine bridges (Unity, Unreal, Godot) and store publishing (Fab, Unity Asset Store, itch) are+already planned in best3d orders [072](../../prompts/finish/072-best3d-06-engine-bridges.md) and+[935](../../prompts/finish/935-best3d-08-engine-store-publishing.md). The orphaned avatar+campaign is [934](../../prompts/finish/934-best3d-07-orphaned-avatar-campaign.md), with the+three-vrm work and VRM 0.x export in [075](../../prompts/finish/075-best3d-09-three-vrm.md).+This plan does not duplicate them.++### Wave 3: commercial partners (weeks 4 to 10)++Once Wave 2 has something live to show, approach the companies whose products we would put+inside ours on commercial terms.++| Prospect | The ask | Owner action |+|---|---|---|+| Meshy | Platform pricing for a house lane, on the Tripo pattern | Partner form |+| ElevenLabs | The startup grant (pipeline row), then the Commercial Partner Program | Two forms |+| Composio | Toolkit partnership: they build and list the three.ws toolkit | One form |+| Avaturn | Case study and a "works with" badge for users who lost their old avatar provider | Contact form |+| Uthana, Rokoko | Licensed motion data, an integrations listing | Email and form |+| Microsoft | Certified MCP server in Copilot Studio and Microsoft 365 Copilot | Partner Center enrollment; the legacy route closes 2026-10-31 |+| Hitem3D, Rodin, Hunyuan3D | API access and credits for the print-quality and premium lanes | Email |++Any new paid API, even one on credits, is an owner decision before it is wired.++### Wave 4: standards and memberships (quarter)++| Body | The step | Cost |+|---|---|---|+| Khronos Group | Associate membership and 3D Commerce viewer certification for `<agent-3d>` | USD 4,000 minimum a year |+| VRM Consortium | Supporting membership and a listing as a VRM-compatible service | Ask `[email protected]` |+| Blender Development Fund | Bronze corporate membership | EUR 6,000 a year |++## Message templates++Fill every bracket from a verified source. Never send a number the proof brief does not+support, and never claim a relationship that does not exist yet.++### 1. A company whose API or model we already run++> Subject: three.ws runs [product] in production+>+> Hi [name], I run three.ws, an open platform where makers and AI agents create, rig and+> publish 3D. [Product] already powers [surface] for us: [one sentence on how, with the file+> or page a reader can open].+>+> Last month the Forge took [audited number] generation and rigging requests from real makers,+> and agents called our MCP tools [number] times from clients including ChatGPT, Claude and+> Cursor. We would like [the specific ask], and in return we can offer [the specific offer].+>+> Would a 20-minute call next week work? Happy to show it live.++### 2. An open-source project we depend on++Lead with the contribution, not the request. Open the pull request or the sponsorship first,+then post once:++> We build three.ws on [project], which powers [surface]. We just [sent PR #n / started+> sponsoring] and added [project] to our [credits page]. If a showcase or case study would be+> useful to you, we would be glad to write one, and if not, thank you for the work.++### 3. A platform listing or directory++Most of these need no message: follow the intake route on the prospects page exactly, and+put the pull request description or the form answers in the order that prepared them.++### 4. Replying to an inbound approach++Answer within one business day. Show them where their work already appears in three.ws, name+one concrete first step, and propose a call. The [Tripo reply draft](./tripo.md#reply-draft)+is the model.++## Cadence and follow-up++- **Day 0:** the first message, from the owner's own address.+- **Day 5:** one short follow-up adding something new (a demo link, a merged pull request, a+ number).+- **Day 12:** a last note saying the door stays open. Then mark the row `no_reply` in the+ tracker and move on.+- An inbound always beats the plan: drop the current wave for a day to answer it.++## Tracking++- **One row per relationship** in+ [`marketing/growth/opportunities.csv`](../../marketing/growth/opportunities.csv), using its+ existing columns and status words. A prospect moves there when it gets its first action.+- **Re-verify intake routes and numbers** on the day of the first message and update+ `last_verified`.+- **Log every outcome** (sent, replied, call held, declined, signed) in the row's `status` and+ `next_action`, so the [pipeline page](./opportunities.md) stays the single answer to "where+ is this".+- A signed partner gets a card on [the partner page](../partners.md) only once the work is+ live, under that page's framing rules.++## How we measure it++| Measure | Source | Target for the first 60 days |+|---|---|---|+| Live listings and registry entries | The tracker | 20 |+| Partner conversations held | The tracker | 10 |+| Signed partnerships (credits, pricing, grant or co-marketing) | The tracker | 3, Tripo first |+| Generation jobs on partner house lanes | `forge_creations`, grouped by `backend` | Tripo above 10% of High-tier jobs |+| Agent-tool clients | OAuth clients on the MCP servers | From 13 to 25 distinct clients |++## Who does what++| Owner only | Agents |+|---|---|+| Sending any message, reply or email | Building every integration, package and page in orders 084 to 095 |+| Opening any pull request, issue or listing on a third-party site | Preparing the exact pull request text, form answers and screenshots |+| Any spend: sponsorships, memberships, paid keys, boosts | Re-verifying numbers and intake routes before each send |+| Approving a new paid API | Updating the tracker and the pipeline page afterwards |+| Signing anything | Writing the case study or launch post draft |++## Related++- [Partner prospects](./prospects.md): the scored list this plan works.+- [Tripo partnership brief](./tripo.md): Wave 0 in full.+- [Partnership and listing pipeline](./opportunities.md): what is already in flight.+- [30-day proof brief](./proof-brief-2026-10.md): the numbers every message quotes.+- [Partner ecosystem](../partners.md): live partner cards and framing rules.diff --git a/docs/start-here.md b/docs/start-here.mdindex 4669d2e2c..3a9d6a941 100644--- a/docs/start-here.md+++ b/docs/start-here.md@@ -222,6 +222,7 @@ Deeper references that don't fit a track above but answer real questions:- [NVIDIA Inception membership](./nvidia-inception.md): what the platform already runs on NVIDIA silicon and what the program adds on top- [NVIDIA visibility map](./nvidia-visibility-map.md): every NVIDIA surface worth being on (Showcase, GTC, NGC, ACE, the forums, social), the verified intake route for each, and the member benefits nobody has claimed yet- [Big-tech recognition dispatch board](./big-tech-recognition-week.md): every big-tech surface ranked against every other by the odds of a published mention this week, which six are already one action from shipping, and what to stop chasing+- [Partner prospects](./partners/prospects.md): the scored list of companies and open-source projects worth partnering with (2026-10-09 sweep), with the intake route for each, worked by [the outreach plan](./partners/outreach-plan.md); [the Tripo brief](./partners/tripo.md) is the first deal on it- [Partnership and listing pipeline](./partners/opportunities.md): every partnership, marketplace and directory as one decision list, showing what is stuck, on whom, and the single step that unblocks it- [IBM visibility map](./ibm-visibility-map.md): every IBM surface worth being on (the user group, IBM Champions, the Partner Plus Directory, the IBM Cloud catalog, TechXchange), the verified intake route for each, and the two windows that close on a date- [IBM Partner Plus](./partners/ibm-partner-plus.md): the companion audit of the program itself, including the watsonx Orchestrate Agent Catalog listing through Agent Connectdiff --git a/marketing/growth/opportunities.csv b/marketing/growth/opportunities.csvindex 52c110cff..e8f6bd4fa 100644--- a/marketing/growth/opportunities.csv+++ b/marketing/growth/opportunities.csv@@ -53,15 +53,15 @@"P1","16","TensorBlock awesome-mcp-servers listing","new-directory","not_started","PR @three-ws/mcp-server into the 3D or creative category (precedent: PR 2463 merged 2026-09-17)","Owner","2026-09-25","mcp-server","A free 3D MCP server on an 856-star list that merges daily","Merged PR URL","https://github.com/TensorBlock/awesome-mcp-servers","2026-09-18""P1","16","Docker MCP Catalog remote entry","new-directory","not_started","PR a remote-server server.yaml for https://three.ws/api/mcp-studio (no auth; initialize returns 200)","Owner","2026-10-02","api/mcp-studio.js","A no-auth 3D MCP inside Docker Desktop MCP Toolkit","Merged PR URL and catalog page","https://github.com/docker/mcp-registry","2026-09-18""P1","16","awesome-ai-companion embodiment listing","new-directory","not_started","PR agent-3d into Visual Presence and VTuber-Style Companions (precedent: PR 19 merged 2026-09-13)","Owner","2026-09-25","src/element.js","An embeddable 3D body for AI companions in the exact matching section","Merged PR URL","https://github.com/DasterProkio/awesome-ai-companion","2026-09-18"-"P1","16","Vercel AI SDK tools registry","integration-registry","build_required","Ship an AI SDK tool() export for the no-key Forge lane then PR the registry entry per contributing/add-new-tool-to-registry.md","Owner + eng","2026-10-09","packages","A no-key text-to-3D tool listed on ai-sdk.dev","Published package and merged registry PR","https://github.com/vercel/ai","2026-09-18"+"P1","16","Vercel AI SDK tools registry","integration-registry","build_required","Build packages/ai-sdk in order 093, then the owner publishes it and opens the registry PR per contributing/add-new-tool-to-registry.md (938)","Owner + eng","2026-10-30","packages","A no-key text-to-3D tool listed on ai-sdk.dev","Published package and merged registry PR","https://github.com/vercel/ai","2026-10-09""P2","15","kyrolabs awesome-agents listing","new-directory","not_started","PR agent-3d into Frameworks or Tools (precedent: PR 766 merged 2026-09-13)","Owner","2026-09-25","src/element.js","An agent-builder audience on a 2.8k-star list","Merged PR URL","https://github.com/kyrolabs/awesome-agents","2026-09-18""P2","15","ricky0123 vad cool-projects entry","upstream-dependency","not_started","PR three.ws voice avatars into the Cool projects using this library section (one existing entry)","Owner","2026-09-25","src/voice/vad.js","A second showcase entry on a 2k-star dependency","Merged PR URL","https://github.com/ricky0123/vad","2026-09-18"-"P2","15","Zed MCP context-server extension","integration-registry","build_required","Build a thin Zed extension wrapping npx @three-ws/mcp-server then PR it (precedent: PR 6945 merged 2026-07-27)","Owner + eng","2026-10-16","mcp-server","3D generation inside the Zed editor next to pollinations-mcp","Merged PR and extension page","https://github.com/zed-industries/extensions","2026-09-18"+"P2","15","Zed MCP context-server extension","integration-registry","build_required","Zed has said it plans to read MCP servers from the official registry. Recheck when order 093 runs: if it does, the official registry entry covers Zed; if not, build the thin extension and the owner opens the PR (938)","Owner + eng","2026-10-16","mcp-server","3D generation inside the Zed editor next to pollinations-mcp","Merged PR and extension page","https://github.com/zed-industries/extensions","2026-10-09""P2","14","toolsdk MCP registry remote entry","new-directory","not_started","PR a JSON entry for the mcp-studio remote per docs/CONTRIBUTING.md (precedent: PR 518 merged 2026-09-15)","Owner","2026-09-25","api/mcp-studio.js","A machine-readable registry that feeds a gateway product","Merged PR URL","https://github.com/toolsdk-ai/toolsdk-mcp-registry","2026-09-18""P2","14","Jenqyang Awesome-AI-Agents listing","new-directory","not_started","PR one line under Applications or Tools (precedent: PR 498 merged 2026-09-18)","Owner","2026-09-25","src/element.js","A same-day-merging agent list","Merged PR URL","https://github.com/Jenqyang/Awesome-AI-Agents","2026-09-18""P2","14","three.js forum Showcase thread","owned-community","not_started","Owner posts a Forge or agent-3d showcase thread (24 new showcase topics since 2026-09-01; no three.ws thread exists)","Owner","2026-10-02","docs/share-and-embed.md","The canonical three.js builder audience","Live forum thread URL","https://discourse.threejs.org/c/showcase/7","2026-09-18"-"P2","13","LangChain JS tool integration","integration-registry","build_required","Publish a langchain-three-ws package then PR the docs integration (precedent: PR 5632 merged 2026-09-02)","Owner + eng","2026-10-23","packages","Listing in LangChain JS tools beside a same-shape generative-media tool","Published package and merged docs PR","https://github.com/langchain-ai/docs","2026-09-18"-"P2","12","LiveKit Agents avatar plugin","integration-partner","design_decision_required","Decide between a server render lane and a docs ask to list client-rendered avatars","Owner + eng","2026-10-30","src/runtime/livekit-voice.js","An avatar plugin in a 14k-star voice agent framework we already depend on","Recorded decision then merged plugin PR","https://github.com/livekit/agents","2026-09-18"+"P2","13","LangChain JS tool integration","integration-registry","build_required","LangChain now takes integrations through an issue first and closes hand-written PRs automatically. Build the package in order 093, then the owner opens the integration issue (938)","Owner + eng","2026-10-23","packages","Listing in LangChain JS tools beside a same-shape generative-media tool","Accepted integration issue, published package and docs listing","https://github.com/langchain-ai/docs","2026-10-09"+"P2","12","LiveKit Agents avatar plugin","integration-partner","build_required","Decided: client-rendered, no server render lane (livekit/agents PR 5821, merged 2026-07-20, renders on the visitor device and sends motion data). Build in order 087, then the owner opens the plugin PR (938) and applies to LiveKit Startups (939)","Owner + eng","2026-10-30","src/runtime/livekit-voice.js","An avatar plugin in a 14k-star voice agent framework we already depend on","Merged plugin PR and a listing on the LiveKit avatar docs page","https://github.com/livekit/agents","2026-10-09""P0","19","Web3D 2026 Competitions (AI and HAnim tracks)","new-event","not_started","Enter the AI and Web3D and HAnim animation competitions on easychair.org/conferences/?conf=web3d26 before 2026-09-30 23:00 PDT","Owner","2026-09-30","src/animation-retarget.js","Prize and a conference showcase for browser 3D agents at the Web3D consortium's own event","Submission receipt then results page","https://web3d.siggraph.org/","2026-09-18""P0","18","Colosseum Crypto World's Fair","new-event","not_started","Register and confirm in the official rules whether an existing product may enter; submissions due 2026-10-12","Owner","2026-10-12","docs/x402-distribution.md","Solana track prizes and an accelerator interview for x402 agent payments","Submission URL then results","https://colosseum.com/worldsfair","2026-09-18""P0","18","Walk Avatar on Chrome Edge and Firefox stores","owned-install-surface","release_checklist_open","Complete extensions/walk-avatar/RELEASE.md, build the zip, submit to Chrome Web Store then Edge Add-ons then Firefox Add-ons","Owner + eng","2026-10-02","extensions/walk-avatar","An installable browser surface that two published articles already described as live","Three live store URLs","https://chrome.google.com/webstore/devconsole","2026-09-18"@@ -97,3 +97,12 @@"P2","14","ModelScope MCP Square and Postman API Network","new-directory","not_started","List the 3D Studio MCP on ModelScope as local-only and publish a Postman public workspace from the OpenAPI file, then email [email protected]","Owner","2026-10-09","public/.well-known/openapi.yaml","Chinese MCP discovery and the Postman API catalog","Two live listings","https://www.modelscope.cn/mcp","2026-09-18""P2","14","AI Tinkerers chapter demo","new-community","not_started","Apply to the nearest chapter with a live prompt-to-rig-to-embed demo","Owner","2026-10-16","src/element.js","A demo slot in a 133k-member builder community","Demo accepted","https://aitinkerers.org","2026-09-18""P2","14","Microsoft Store and pwa.directory PWA listings","installable-distribution","not_started","Check the Store financial-services policy, package with PWABuilder, submit; submit pwa.directory free","Owner","2026-10-16","vite.config.js","Two install surfaces for the existing PWA","Two live listings","https://pwa.directory/submit","2026-09-18"+"P0","19","Tripo partner key and house lane","new-partner","reply_draft_ready","Owner sends the reply in docs/partners/tripo.md and holds the first call (order 936); order 084 builds the v3 house lane behind TRIPO_API_KEY","Owner + eng","2026-10-12","docs/partners/tripo.md","Tripo in front of every Forge user instead of the few who bring their own key, plus v3, webhooks and rig, splat and segmentation endpoints","Signed pilot, key on the service, Tripo house-lane jobs in forge_creations","https://developers.tripo3d.ai","2026-10-09"+"P1","17","Microsoft Copilot Studio and Microsoft 365 Copilot MCP certification","new-program","not_started","Draft the Partner Center application (order 939) and submit before the legacy route closes 2026-10-31","Owner","2026-10-24","mcp-server","A certified MCP connector in Copilot Studio and Microsoft 365 Copilot","Certified connector listing","https://learn.microsoft.com/en-us/microsoft-copilot-studio/","2026-10-09"+"P1","17","Pipecat community avatar integration","integration-registry","build_required","Build integrations/pipecat in order 087, then the owner opens the community-integration docs PR (938)","Owner + eng","2026-11-06","src/runtime/livekit-voice.js","A 3D avatar service listed among Pipecat community integrations","Merged docs PR","https://github.com/pipecat-ai/pipecat","2026-10-09"+"P1","16","Discord Activity","integration-partner","build_required","Build the Activity in order 088, then the owner completes app verification and Activity Discovery (939)","Owner + eng","2026-11-13","api/gateway/discord.js","A shared 3D Forge and agent inside Discord voice channels","Activity listed in the App Directory","https://discord.com/developers/docs/activities/overview","2026-10-09"+"P1","16","Craftcloud print fulfillment","integration-partner","build_required","Build the get-it-printed button and the Craftcloud adapter in order 089 against the public v5 API","Owner + eng","2026-11-06","api/_lib/print/adapters/contract.js","Live print quotes from 186 shops on every Forge model, with referral revenue","Live quotes on model pages and the first referred order","https://api.craftcloud3d.com/docs","2026-10-09"+"P1","16","Shopify product-media app","installable-distribution","build_required","Build integrations/shopify in order 091, then the owner creates the Partner account and submits to the App Store (939)","Owner + eng","2026-11-27","integrations","Photo to GLB and USDZ product media for Shopify merchants, billed through Shopify","Approved App Store listing","https://shopify.dev/docs/apps","2026-10-09"+"P2","15","VRoid Hub avatar import","integration-partner","build_required","Build /import/vroid in order 092 behind VROID_HUB_* env vars, then the owner applies for app approval (939)","Owner + eng","2026-11-20","src/glb-canonicalize.js","VRoid Hub avatars talking and acting as agents, with their license conditions enforced","Approved app and first real imports","https://developer.vroid.com","2026-10-09"+"P2","15","Home Assistant HACS default store","installable-distribution","build_required","Validate and export the standalone repository in order 095, then the owner creates it and opens the brands and hacs/default PRs (938)","Owner + eng","2026-11-13","home-assistant-integration","three.ws Home installable from the HACS default store","Merged hacs/default PR","https://hacs.xyz/docs/publish/start","2026-10-09"+"P2","14","Composio toolkit partnership","integration-registry","not_started","Owner submits the Composio toolkit form with the text order 093 prepares (938)","Owner","2026-10-30","mcp-server","three.ws tools available to every Composio-connected agent","Live Composio toolkit page","https://composio.dev","2026-10-09"