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(submissions): close B3 on measurement, so the OpenAI row stops reading as blocked

nirholasd203ed848cf0
diff --git a/docs/partners/opportunities.md b/docs/partners/opportunities.md
index 73a35ed5b..0ae675946 100644
--- a/docs/partners/opportunities.md
+++ b/docs/partners/opportunities.md
@@ -44,7 +44,7 @@ work already done and is waiting on a single human step.
| 2 | **IBM Agent Connect catalog listing** | Email `[email protected]` for the BYOL `APP_ID` | Everything else is built and verified ([submission pack](../../marketing/ibm-partner-plus/agent-connect-listing.md)). One email opens an IBM-backed enterprise channel. |
| 3 | **AWS Marketplace** | Create the product in the AWS Marketplace Management Portal | The SaaS integration is built, deployed, and conformant. The listing was simply never created, so an enterprise procurement channel we already paid the engineering cost for returns nothing. |
| 4 | **NVIDIA NGC Catalog** | One container build plus the partner legal agreement | The only NVIDIA directory with self-serve intake. The EULA prerequisite is already closed. |
-| 5 | **OpenAI Plugin Directory** | Submit | We already meet the gating requirement (public OAuth 2.1 MCP server). |
+| 5 | **OpenAI Plugin Directory** | Submit | We already meet the gating requirement (public OAuth 2.1 MCP server), and the output-quality blocker that held this back is closed: the forge quality gate measured **10/10 verdicts** on production 2026-09-11, up from 0/10 two days earlier. It was closed by fixing the vision failover chain, not by clearing the GCP billing hold. |
| 6 | **Second IBM community event** | Pick a date | A fully costed proposal ([ibm-next-event.md](../ibm-next-event.md)) has been waiting on nothing but a calendar decision. Cheapest unblock on this page. |
---
diff --git a/prompts/store-submissions/_generated/TRACKER.md b/prompts/store-submissions/_generated/TRACKER.md
index f59dd6df3..321ec5c29 100644
--- a/prompts/store-submissions/_generated/TRACKER.md
+++ b/prompts/store-submissions/_generated/TRACKER.md
@@ -87,7 +87,7 @@ There are **six** MCP gates, not four: `audit:mcp`, `audit:mcp-golden`, `audit:m
| **Claude Connectors Directory** | ready-to-submit (pending the human items) | `POST /api/mcp tools/list` unauthenticated returned **200 with 53 tools in 0.10s**; `initialize` likewise. `GET /.well-known/oauth-protected-resource` 200 with 13 scopes. `/legal/privacy`, `/legal/tos`, `/support`, `/docs/mcp` all 200, and privacy still carries the "MCP Connectors, AI Processing & Payments" section. | The 2026-06-28 blocker that discovery was auth-gated is **resolved and no longer true**: the portal can sync tools with no credential. Remaining: `[HUMAN: Team/Enterprise org + Owner role, or use the public form]` and `[HUMAN: generate a real MCP_REVIEW_SECRET and decide which vendor credentials a reviewer gets]`. Note the 147s free-lane latency above before demoing live. |
| **Claude plugin marketplace** | ready-to-submit | `.claude-plugin/marketplace.json` carries 4 plugins (`three-ws-core`, `three-ws-developer`, `three-ws-pump-fun`, `three-ws-3d`). The end-to-end CLI install evidence from 2026-07-08 stands in `_generated/claude-plugin-marketplace-e2e.md` and was not re-driven today. | `[HUMAN: submit via https://platform.claude.com/plugins/submit per marketplace/plugins/three-ws-3d/SUBMISSION.md]` |
| **Claude Agent Skills pack** | ready-to-submit | `node scripts/build-skills-pack.mjs --check` → `skills-pack manifest up to date (42 skills)`; `.agents/skills/` holds 44 entries. | None in code. The live free-lane E2E it wanted is now green but slow (147s, see above). |
-| **OpenAI App Directory** | blocked (B3, infrastructure) plus an unshipped deploy | Whole surface re-verified live 2026-09-09: `initialize` 200 keyless, `tools/list` **11 tools** each with its four `openai/*` annotations and correct `outputTemplate`, `resources/list` **2 widget resources** with `widgetCSP`/`widgetDescription`/`widgetDomain`, `/.well-known/3d-studio-openapi.yaml` (Redocly-clean, free-only, all inner URLs 200) and `/.well-known/ai-plugin.json` both 200, `/legal/privacy` + `/legal/tos` 200, a real keyless `forge_free` returned a 5.40 MB GLB in 137s whose `/viewer?src=` returned 200, `POST/GET /api/3d/studio` polled to a real GLB, `/api/ar` correct per device class, and the widget drove through empty/loading/ready/error in a `window.openai`-less browser. Every one of those payloads scanned clean of crypto, payment and internal ids. | **B3 is narrower than it looked.** The scorer fix IS deployed (revision `three-ws-api-00420-ljh`) and re-measuring it on 40 consecutive production generations gave 4 planar flags, 4/4 escalating. The fallback rung is also **not** dead: a 15:04Z generation scored through the free NVIDIA vision lane with a full verdict, so "the NIM fallback 504s" no longer holds in general. Vertex is still 403 on the billing hold, and the gate fails open, so escalation stays non-deterministic until the hold clears. Four fixes from this pass are in the tree and unshipped (widget CORS routing, honest pending ETA, failover-error reporting, 14 reviewer-visible em-dashes). `[HUMAN: clear the GCP billing hold]`, `[HUMAN: deploy the tree]`, then `[HUMAN: final submit in the partner portal]`. |
+| **OpenAI App Directory** | ready-to-submit (B3 cleared 2026-09-11) | Whole surface re-verified live 2026-09-09: `initialize` 200 keyless, `tools/list` **11 tools** each with its four `openai/*` annotations and correct `outputTemplate`, `resources/list` **2 widget resources** with `widgetCSP`/`widgetDescription`/`widgetDomain`, `/.well-known/3d-studio-openapi.yaml` (Redocly-clean, free-only, all inner URLs 200) and `/.well-known/ai-plugin.json` both 200, `/legal/privacy` + `/legal/tos` 200, a real keyless `forge_free` returned a 5.40 MB GLB in 137s whose `/viewer?src=` returned 200, `POST/GET /api/3d/studio` polled to a real GLB, `/api/ar` correct per device class, and the widget drove through empty/loading/ready/error in a `window.openai`-less browser. Every one of those payloads scanned clean of crypto, payment and internal ids. | **B3 is narrower than it looked.** The scorer fix IS deployed (revision `three-ws-api-00420-ljh`) and re-measuring it on 40 consecutive production generations gave 4 planar flags, 4/4 escalating. The fallback rung is also **not** dead: a 15:04Z generation scored through the free NVIDIA vision lane with a full verdict, so "the NIM fallback 504s" no longer holds in general. **B3 is now closed, and NOT by clearing the billing hold.** Measured 2026-09-11 against revision `three-ws-api-00424-5p4`: ten consecutive authenticated calls to `/api/forge-quality-check` returned **10/10 real verdicts** (`provider: nvidia`, `qa_available: true`), against 3/10 on 2026-09-10 and 0/10 on 2026-09-09. The gate is deterministic again because the vision chain was fixed rather than because Vertex came back: JSON validity became part of the failover test instead of a filter applied after a winner was picked, the per-lane budget stopped being divided equally (which had starved the one healthy rung), a billing-denied Vertex is now parked by a circuit breaker instead of re-probed on every call, and the chain was widened from four providers to ten. Vertex is still denied on the hold; it no longer decides the outcome. The four fixes listed here as unshipped are shipped. Remaining: `[HUMAN: final submit in the partner portal]`. Clearing the GCP billing hold is still worth doing, but it is no longer this row's blocker. |
| **OpenAI GPT Store** | live, with a duplicate to remove | `https://chatgpt.com/g/g-6a563a3b49a88191abf346245491a444-three-ws-3d-studio` returns 200 logged-out. The old draft `g-6a5672fbf3f48191b559e482c7fcbf51` **301s to a 200 page titled "ChatGPT - three.ws 3D Studio"**, so the 2026-09-02 escalation stands: two public GPTs share one name. | `[HUMAN: delete the draft duplicate in My GPTs]` (no API for it) |
| **Official MCP Registry** | ready-to-submit | `node prompts/store-submissions/_generated/build-registry-republish.mjs` against the live registry, after the pagination fix below: **3 servers need a publish (0 stale, 3 new: `herald-mcp`, `knock-mcp`, `home-mcp`), 47 are already current**, including all 7 hosted remotes. Cross-checked with `node scripts/publish-mcp-servers.mjs --dry-run`, which agrees. The batch is staged in `_generated/mcp-registry-republish.sh` and was NOT run. | `[HUMAN: mcp-publisher login github, then review and run the staged batch]` |
| **Smithery** | ready-to-submit | `_generated/mcp-directories/smithery.md` regenerated today from the corrected canonical source; it now covers **50 servers (7 remote + 43 stdio)**. | `[HUMAN: create/claim the Smithery account]` |