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(nvidia): add the Inception listing-request pack with a verified outreach email
nirholas28f3a2553946
diff --git a/STRUCTURE.md b/STRUCTURE.mdindex 19b839f79..b4f8700a1 100644--- a/STRUCTURE.md+++ b/STRUCTURE.md@@ -78,7 +78,7 @@ bottom.| IRL (agents in the real world) | [pages/irl.html](pages/irl.html) `→ /irl` + [src/irl.js](src/irl.js), WebXR placement [src/ar/webxr.js](src/ar/webxr.js) + pinch [src/ar/pinch-scale.js](src/ar/pinch-scale.js), animated Quick Look bake [src/usdz-animated.js](src/usdz-animated.js) (static fallback [src/usdz-pipeline.js](src/usdz-pipeline.js)), backend [api/irl/](api/irl) | Live | Pin an agent at a real GPS spot; discovery is presence-proof-gated ([docs/irl/THREAT-MODEL.md](docs/irl/THREAT-MODEL.md)). **Place in AR** leads the dock on AR-capable devices: WebXR hit-test anchoring on Android with two-finger pinch resize (25%..400%) persisted to the pin (`anchor_scale`; the pinch lands as a follow-up `PATCH /api/irl/pins {id, scale}` after the placement tap), and ARKit Quick Look on iOS with the idle clip baked into the USDZ so the agent moves instead of standing in a T-pose. Discovered pins are equally alive in the in-page camera view: every mounted humanoid GLB plays the retargeted idle clip via a per-pin mixer ([src/irl/pin-idle.js](src/irl/pin-idle.js), phase-randomized, LOD-bounded), camera-aware gaze composes on top of the running animation, and the scene renders with ACES tone mapping + IBL + soft shadows (e2e: [tests/e2e/irl-pin-idle.spec.js](tests/e2e/irl-pin-idle.spec.js)). Inbound `/irl?avatar=<glb>` is the living-agent handoff from `GET /api/ar?…&kind=avatar` (explicit `?avatar=` wins over a saved session). Money Drops and World Lines: [docs/irl.md](docs/irl.md). SDK: [packages/irl/](packages/irl). **Share** ([src/irl/share-frame.js](src/irl/share-frame.js), [api/irl/share.js](api/irl/share.js), [api/irl/share/[token].js](api/irl/share/%5Btoken%5D.js)) mints a permanent, unfurlable `/irl/s/:token` link from the captured AR photo for the pin you just placed - never a coordinate, owner-gated, falls back to the plain native share sheet with no active pin. **Analytics** ([api/_lib/irl-analytics.js](api/_lib/irl-analytics.js), [api/irl/analytics.js](api/irl/analytics.js)) is the first site-wide usage rollup for the feature - pins placed, nearby reads, placement method, shares, drop claims - aged out by the existing hourly reaper. || Verifiable 3D provenance (content credentials) | Spec [specs/PROVENANCE_3D.md](specs/PROVENANCE_3D.md), pure core [api/_lib/provenance-3d.js](api/_lib/provenance-3d.js), Solana anchor [api/_lib/provenance-anchor.js](api/_lib/provenance-anchor.js), MCP tools [api/_mcp3d/tools/provenance.js](api/_mcp3d/tools/provenance.js) (`verify_provenance` free, `anchor_provenance` paid $0.05), free REST verify [api/provenance.js](api/provenance.js) `→ /api/provenance`, viewer badge [public/viewer.html](public/viewer.html), docs [docs/provenance.md](docs/provenance.md). | Live (verify) · anchor gated on issuer key + devnet funds | C2PA-style signed content credentials for AI 3D: creator, prompt, model/provider, lineage, timestamp, and the GLB's sha256, ed25519-signed by the three.ws issuer with the credential hash anchored on Solana. Free public `verify_provenance` / `GET /api/provenance?src=…` recompute the hash and return `verified | tampered | unknown` (a single changed byte → tampered); the verify path and response are coin-clean (both stores). `anchor_provenance` signs + writes the SPL Memo anchor + stores the credential in R2. Tests: [tests/provenance-3d.test.js](tests/provenance-3d.test.js). Evidence: [prompts/store-submissions/_generated/provenance/](prompts/store-submissions/_generated/provenance/). Store-submission prompt 19. || OpenAI Select Partner (partner surface + announcement pack) | [pages/openai/index.html](pages/openai/index.html) `→ /openai`, badge assets [public/partners/openai/](public/partners/openai), announcement [blog/three-ws-openai-select-partner.html](blog/three-ws-openai-select-partner.html) `→ /blog/three-ws-openai-select-partner`, directory card in [pages/partners.html](pages/partners.html) `→ /partners`, press/social pack [marketing/openai-select-partner/](marketing/openai-select-partner/README.md), original OpenAI-supplied badge files + press-release template [OAI Select Tier Assets/](OAI%20Select%20Tier%20Assets/README.md) | Live | three.ws's OpenAI Partner Network Select-tier surface. `/openai` is the partner landing: the supplied badge (used unmodified, on a white plate), the four live OpenAI surfaces (the free keyless [3D Studio MCP connector](docs/mcp-studio.md) `→ /api/mcp-studio`, the custom-GPT Actions twin `→ /api/3d/studio`, [Spatial MCP](specs/SPATIAL_MCP.md), and [AR in ChatGPT](docs/chatgpt-ar.md)), the connect table, and the nine-tool list. The marketing pack holds badge-usage rules and the press-release draft, which is gated on OpenAI's written approval before publishing (see its README). |-| NVIDIA Inception (membership surface + GPU docs cluster) | Landing page [pages/nvidia/index.html](pages/nvidia/index.html) `→ /nvidia` (vercel route + vite input + dev middleware, same wiring as `/openai`), membership doc [docs/nvidia-inception.md](docs/nvidia-inception.md) `→ /docs/nvidia-inception` + overview deck [docs/nvidia-inception/index.html](docs/nvidia-inception/index.html) `→ /docs/nvidia-inception/index.html`, free hosted-model map [docs/nvidia-models.md](docs/nvidia-models.md) `→ /docs/nvidia-models`, forum write-up [docs/nvidia-nemotron-spotlight.md](docs/nvidia-nemotron-spotlight.md) `→ /docs/nvidia-nemotron-spotlight`, tutorials [docs/tutorials/nvidia-3d-free.md](docs/tutorials/nvidia-3d-free.md) `→ /tutorials/nvidia-3d-free` and [docs/tutorials/nvidia-nim-self-host.md](docs/tutorials/nvidia-nim-self-host.md) `→ /tutorials/nvidia-nim-self-host`, engineering post [blog/image-to-3d-on-nvidia-l4-and-blackwell.html](blog/image-to-3d-on-nvidia-l4-and-blackwell.html) `→ /blog/image-to-3d-on-nvidia-l4-and-blackwell`, member badge [public/marks/nvidia-inception-badge.svg](public/marks/nvidia-inception-badge.svg) in [public/footer.html](public/footer.html), directory card in [pages/partners.html](pages/partners.html) `→ /partners` | Live | Everything NVIDIA on the platform, in two layers. **Free hosted lane:** one `NVIDIA_API_KEY` behind TRELLIS text-to-3D, FLUX.1-schnell, the Llama/Nemotron chat lineup, Nemotron vision, nv-embedqa, the reranker, NemoGuard, and Magpie speech (`nvidia-models`). **Self-hosted GPU fleet:** 12 Cloud Run GPU services, 11 on `nvidia-l4` and one on `nvidia-rtx-pro-6000` (Blackwell), covering text/image-to-3D, texture, remesh, rigging, and motion (see each `workers/model-*/README.md`). Membership was accepted July 2026 and is a startup program, not a partnership or an investment; the badge links to NVIDIA's startup program and must not imply endorsement. |+| NVIDIA Inception (membership surface + GPU docs cluster) | Landing page [pages/nvidia/index.html](pages/nvidia/index.html) `→ /nvidia` (vercel route + vite input + dev middleware, same wiring as `/openai`), membership doc [docs/nvidia-inception.md](docs/nvidia-inception.md) `→ /docs/nvidia-inception` + overview deck [docs/nvidia-inception/index.html](docs/nvidia-inception/index.html) `→ /docs/nvidia-inception/index.html`, free hosted-model map [docs/nvidia-models.md](docs/nvidia-models.md) `→ /docs/nvidia-models`, forum write-up [docs/nvidia-nemotron-spotlight.md](docs/nvidia-nemotron-spotlight.md) `→ /docs/nvidia-nemotron-spotlight`, tutorials [docs/tutorials/nvidia-3d-free.md](docs/tutorials/nvidia-3d-free.md) `→ /tutorials/nvidia-3d-free` and [docs/tutorials/nvidia-nim-self-host.md](docs/tutorials/nvidia-nim-self-host.md) `→ /tutorials/nvidia-nim-self-host`, engineering post [blog/image-to-3d-on-nvidia-l4-and-blackwell.html](blog/image-to-3d-on-nvidia-l4-and-blackwell.html) `→ /blog/image-to-3d-on-nvidia-l4-and-blackwell`, member badge [public/marks/nvidia-inception-badge.svg](public/marks/nvidia-inception-badge.svg) in [public/footer.html](public/footer.html), directory card in [pages/partners.html](pages/partners.html) `→ /partners`, listing-outreach pack [marketing/nvidia-inception/](marketing/nvidia-inception/README.md) | Live | Everything NVIDIA on the platform, in two layers. **Free hosted lane:** one `NVIDIA_API_KEY` behind TRELLIS text-to-3D, FLUX.1-schnell, the Llama/Nemotron chat lineup, Nemotron vision, nv-embedqa, the reranker, NemoGuard, and Magpie speech (`nvidia-models`). **Self-hosted GPU fleet:** 12 Cloud Run GPU services, 11 on `nvidia-l4` and one on `nvidia-rtx-pro-6000` (Blackwell), covering text/image-to-3D, texture, remesh, rigging, and motion (see each `workers/model-*/README.md`). Membership was accepted July 2026 and is a startup program, not a partnership or an investment; the badge links to NVIDIA's startup program and must not imply endorsement. || Press kit (brand marks + media assets) | [pages/press/index.html](pages/press/index.html) `→ /press`, marks [public/brand/](public/brand), layout source [marketing/brand/](marketing/brand/README.md), renderer [scripts/render-brand-assets.mjs](scripts/render-brand-assets.mjs) `npm run build:brand-assets` | Live | The self-serve press surface: transparent-PNG marks (cube, horizontal and stacked lockups for dark and light grounds), the OpenAI announcement graphics, boilerplate at four lengths (one line, short, long, and a full-length bio) with copy buttons, fast facts, and the mark-usage rules. Everything is rendered from source rather than hand-exported, so a copy change re-renders the whole set; the renderer also builds `/brand/three-ws-press-kit.zip` with a README carrying the usage rules so the files cannot travel without them. Announcement cards come from [marketing/openai-select-partner/cards/social-card.html](marketing/openai-select-partner/cards/social-card.html) via `npm run build:openai-cards`. || Sperax partnership + SperaxOS plugin | [pages/sperax.html](pages/sperax.html) `→ /sperax`, plugin [public/sperax/](public/sperax/README.md), manifest `→ /.well-known/sperax-plugin.json`, tools [api/chat-plugin/[tool].js](api/chat-plugin/%5Btool%5D.js) `→ /api/chat-plugin/*`, panel `→ /sperax/iframe/`, bundled SDK component [chat-plugin/](chat-plugin) (`@three-ws/chat-plugin`, for hosts that mount plugins as React components instead of framing the manifest) | In-repo · Live | Partnership landing for the SperaxOS integration: three.ws ships as a standalone `plugin.delivery` plugin that gives a SperaxOS agent an embodied 3D avatar (speak/gesture/emote/render_agent), bound to an ERC-8004 identity, settling over Base x402. Launch offer: free AI credits for three.ws users on [chat.sperax.io](https://chat.sperax.io) — page explains what it is and how to claim. Blog: [/blog/three-ws-speraxusd-integration](blog/three-ws-speraxusd-integration.html) || Agent Monitor (fleet ops board) | [pages/monitor.html](pages/monitor.html) + [src/monitor.js](src/monitor.js) `→ /monitor` | In-repo · Live | HQ-style ops-room dashboard for the whole 3D agent fleet on one screen, every panel a real public feed on its own poll cadence: fleet ranked by real actions ([api/agents/public.js](api/agents/public.js) `sort=live`) with a click-to-load 3D `<agent-3d>` spotlight, live screen casts ([api/agent-screen-active.js](api/agent-screen-active.js)), 24h money pulse + 7d sparkline + agent coin launches ([api/pulse.js](api/pulse.js) `view=stats`), delta-polled on-chain event wire (`/api/pulse` with `head_cursor`), x402 revenue by endpoint ([api/x402-revenue.js](api/x402-revenue.js)), A2A hire volume ([api/agent-economy/volume.js](api/agent-economy/volume.js)), uptime probes ([api/status.js](api/status.js)), a community forge feed ([api/forge-gallery.js](api/forge-gallery.js)), the tip-earner leaderboard, and the crew directory ([api/crews/directory.js](api/crews/directory.js)). Panel controls: fleet search + sort (server `q=`/`sort=`), wire kind filters + pause, x402 period and A2A window toggles, mainnet/devnet switch, spotlight prev/next/fullscreen, and keyboard shortcuts (`f` search, `r` refresh, `[`/`]` cycle spotlight) |diff --git a/marketing/README.md b/marketing/README.mdindex 7b0117291..5a5895df9 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 || --- | --- || [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) | Outreach pack for getting three.ws listed on NVIDIA's surfaces as an Inception member: the ready-to-send email, the map of where a listing can actually happen, and the verification log behind every claim in it. || [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. || [quicknode](quicknode/) | Finished QuickNode announcement graphics, dark and light PNG variants. || [x402-milestone](x402-milestone/README.md) | A 25-second stats film for the x402 economy's first 25 days on Solana mainnet: Veo 3 footage composited with exact overlaid numbers. |diff --git a/marketing/nvidia-inception/README.md b/marketing/nvidia-inception/README.mdnew file mode 100644index 000000000..88a56757e--- /dev/null+++ b/marketing/nvidia-inception/README.md@@ -0,0 +1,67 @@+# marketing/nvidia-inception/++Outreach pack for getting three.ws listed on NVIDIA's surfaces as an Inception+member. The membership itself is already done (accepted July 2026, documented at+[docs/nvidia-inception.md](../../docs/nvidia-inception.md) and rendered at+`/docs/nvidia-inception`). This directory is about the next step: a **product+listing**, which is a separate thing NVIDIA does not grant automatically.++| File | What it is |+| --- | --- |+| [listing-request-email.md](listing-request-email.md) | The ready-to-send email to `[email protected]`, plus a follow-up for the no-reply case and the rules for whoever sends it. |++---++## Where a listing can actually happen++Researched 2026-08-17 against NVIDIA's live pages. There is no public+self-serve "list my product" form on any of these, which is why the route is an+email.++| Surface | What it lists | How you get on it | Fit for three.ws |+| --- | --- | --- | --- |+| **Inception Startup Showcase** (`nvidia.com/en-us/startups/showcase/`) | Member companies and their products, plus feature slots in NVIDIA newsletters, campaigns, and case studies | No public form. The page's only stated contact is `[email protected]` (`[email protected]` for China). Selection reads the member profile in the Inception portal, so that profile is the real prerequisite. | **Primary target.** This is the listing the email asks for. |+| **Inception portal** (`programs.nvidia.com/phoenix/`) | Our own company and product record inside NVIDIA | Log in and complete it. NVIDIA states members must keep product and company details current to stay eligible for benefits. | **Do this regardless of any reply.** It gates the Showcase and costs nothing but an hour. |+| **ACE / digital-human ecosystem pages** | Companies shipping Audio2Face, Riva, and related ACE microservices | No public form found. Ask for the redirect in the same email. | **Strong.** Magpie, Riva, and Audio2Face-3D are all in production, not prototyped. |+| **build.nvidia.com / NGC catalog** | Models, NIM microservices, and containers | Publish an artifact NVIDIA hosts | **Weak today.** We consume NIM, we do not publish a model or container to it. Not worth asking for yet. |+| **Omniverse Exchange** | Omniverse extensions and OpenUSD connectors | Ship an extension, then submit it | **Not yet.** OpenUSD interop is an aspiration in our own membership doc, not shipped code. Do not claim it. |++The honest read: the Showcase is the one real target right now, the portal+profile is the prerequisite nobody has completed, and ACE is the strongest+technical story we have to lead with.++## Facts in the email, and how each was verified++Everything below was checked on 2026-08-17 before the email was written. Recheck+anything that looks stale before sending.++| Claim | Verified how | Result |+| --- | --- | --- |+| 12 GPU deployments, 11 × L4 + 1 × RTX PRO 6000 | `gcloud run services list --project aerial-vehicle-466722-p5 --format="csv[no-heading](metadata.name,region,spec.template.spec.nodeSelector)"`, filtered to rows carrying an `accelerator` node selector | Confirmed. 12 across `us-central1` and `us-east4`. Counting only `us-central1` gives 8, which is the trap: the fleet spans two regions. |+| The NVIDIA-hosted model lanes | [docs/nvidia-models.md](../../docs/nvidia-models.md), one lane per section | Confirmed: TRELLIS, FLUX.1-schnell, Llama/Nemotron chat, Nemotron vision, nv-embedqa-e5-v5, reranker, NemoGuard, Magpie |+| ACE stack in production | [ARCHITECTURE.md](../../ARCHITECTURE.md) endpoint table: `/api/tts/speak` (Magpie), `/api/asr` (Riva), `/api/a2f` (Audio2Face-3D, ARKit 52 blendshapes), `/api/cosmos` | Confirmed |+| Both forum write-ups are live | `curl -o /dev/null -w '%{http_code}'` on each URL | Both 200 |+| Every three.ws link in the email resolves | Same, against `/nvidia`, `/docs/nvidia-inception`, `/docs/nvidia-models`, `/blog/image-to-3d-on-nvidia-l4-and-blackwell`, `/forge` | All 200 |+| Membership timing | [docs/nvidia-inception.md](../../docs/nvidia-inception.md) and the `2026-07-30` changelog entry, "A home for everything three.ws runs on NVIDIA" | July 2026, stated in the email as "since July 2026" rather than a precise day |++Recount the fleet with:++```bash+gcloud run services list --project aerial-vehicle-466722-p5 \+ --format="csv[no-heading](metadata.name,region,spec.template.spec.nodeSelector)" \+ | grep -i accelerator+```++## Status++- [x] Listing routes researched and mapped+- [x] Every claim in the email verified against production+- [x] Email drafted, with a follow-up for the no-reply case+- [ ] **Sent.** Owner-gated: outreach to an external party needs the owner to send it, per the approval rules in [CLAUDE.md](../../CLAUDE.md).+- [ ] Inception portal profile completed at `programs.nvidia.com/phoenix/`. Worth doing before the email goes out, since the Showcase is curated from it.++## Related++- [docs/nvidia-inception.md](../../docs/nvidia-inception.md): the membership itself, and the rule that it is a program and not a partnership+- [docs/nvidia-models.md](../../docs/nvidia-models.md): the free hosted inference layer, model by model+- [marketing/openai-select-partner/](../openai-select-partner/README.md): the same shape of pack for OpenAI, and the precedent this one followsdiff --git a/marketing/nvidia-inception/listing-request-email.md b/marketing/nvidia-inception/listing-request-email.mdnew file mode 100644index 000000000..88df13ede--- /dev/null+++ b/marketing/nvidia-inception/listing-request-email.md@@ -0,0 +1,122 @@+# NVIDIA listing request: the email++Ready to send. Every number and link in the body below was verified against+production and against NVIDIA's live pages on 2026-08-17 (see+[README.md](README.md) for the verification log).++- **To:** `[email protected]`+- **From:** `[email protected]` (Nicholas Resendez, Founder)+- **Cc:** `[email protected]`+- **Subject:** `Inception member three.ws: request to be listed in the Startup Showcase`++Send it as plain text or lightly formatted HTML. Do not attach anything: every+claim in the email is a link NVIDIA can open itself, which is the point.++---++## The body++Hi NVIDIA Inception team,++I am Nicholas Resendez, founder of three.ws, an Inception member since July 2026.+I would like to get three.ws listed in the Inception Startup Showcase, and I want+to check what you need from us to make that happen.++**What three.ws is.** A browser-native platform for 3D AI agents. You type a+prompt, we generate a textured, rigged 3D avatar, you give it an LLM brain and a+voice, and you embed it anywhere with one HTML tag. No plugins, no installs, no+server uploads. The generation tier is free and needs no account, so anyone+evaluating it can go from a text prompt to a downloadable GLB in under a minute+at https://three.ws/forge.++**Why we think it is a fit for the Showcase.** three.ws is not a product that+mentions NVIDIA in a slide. Every compute-bound path in it runs on NVIDIA:++- **A self-hosted GPU fleet on Cloud Run:** 12 GPU service deployments across+ us-central1 and us-east4, 11 on NVIDIA L4 and one on RTX PRO 6000 Blackwell.+ They cover text-to-3D and image-to-3D (TRELLIS, TripoSR, TripoSG,+ Hunyuan3D 2.1), auto-rigging, and text-to-motion.+- **The NVIDIA-hosted model layer**, all behind a single build.nvidia.com key:+ TRELLIS for text-to-3D, FLUX.1-schnell, the Llama and Nemotron chat lineup,+ Nemotron vision, nv-embedqa-e5-v5, the reranker, and NemoGuard. The model by+ model map is public at https://three.ws/docs/nvidia-models.+- **The ACE digital-human stack in production, not in a prototype:** Magpie for+ text-to-speech, Riva for speech recognition, and Audio2Face-3D driving ARKit 52+ blendshapes on live avatars in the browser. Cosmos powers our text-to-world+ video lane.++We also write up what we learn on your forums rather than only on our own blog:++- How Nemotron made our text-to-3D pipeline usable:+ https://forums.developer.nvidia.com/t/how-nemotron-made-three-ws-text-to-3d-pipeline-usable/376445+- How we translate a web app into 100 languages with NVIDIA NIM:+ 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+- The engineering detail on the fleet itself, including memory ceilings, sm_120+ kernels, and regional GPU quota:+ https://three.ws/blog/image-to-3d-on-nvidia-l4-and-blackwell++**What I am asking for.** Three things, in the order that matters to us:++1. **A Showcase listing for three.ws.** If that is curated from our Inception+ portal profile, tell me which fields you read and I will have the profile+ complete the same day. If it needs a separate submission, point me at the form+ or tell me what to send and in what format: description, category, industry,+ logo, screenshots, a demo link, whatever the template wants.+2. **Consideration for the ACE and digital-human ecosystem pages.** We are+ already shipping Audio2Face-3D, Riva, and Magpie to real users in a browser,+ which seems like the exact story those pages exist to tell. If there is a+ different intake for that, I am happy to be redirected.+3. **The right contact for developer-ecosystem or co-marketing work**, if that+ sits with someone other than you. We have the material and we would rather+ route it correctly than send it to the wrong inbox twice.++Everything we run on NVIDIA is collected at https://three.ws/nvidia, and our+membership page is at https://three.ws/docs/nvidia-inception. The platform is+source-available at https://github.com/nirholas/three.ws.++Happy to do a live walkthrough, or to send anything else you need in whatever+format the Showcase template expects.++Thanks,++Nicholas Resendez+Founder, three.ws+https://three.ws++---++## If you get no reply in 10 business days++Send this as a reply on the same thread rather than as a new email, so the+history stays in one place.++Hi again,++Following up on the Showcase listing request below. If the Startup Showcase is+curated rather than open to requests, that is a completely fine answer and I will+stop asking: I would just like to know so I can put the effort into the portal+profile or into the ACE ecosystem route instead.++One line if it is easier than a paragraph: is a Showcase listing something we can+request, and if so, what do you need from us?++Thanks,+Nicholas++---++## Notes for whoever sends this++- **Do not claim a partnership.** Inception is a startup program. The words to+ use are "Inception member" and "member since July 2026". Never "NVIDIA+ partner", never "backed by NVIDIA", never anything implying endorsement or+ investment. This is the same rule the badge already follows in the site footer,+ and getting it wrong in an email to NVIDIA itself is the worst place to get it+ wrong.+- **Keep the token out of it.** Nothing in this thread should mention the coin.+ The ask is a GPU and digital-human product listing, and every sentence should+ earn its place against that ask.+- **The numbers are load-bearing.** If the GPU fleet changes shape before this+ goes out, recount it with the command in [README.md](README.md) and edit the+ body. Sending NVIDIA a stale GPU count is a self-inflicted credibility problem.