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(growth): add AWS Marketplace, ElevenLabs, GCP agent, Hugging Face, and Quicknode campaign kits
nirholasd4838f238e99
diff --git a/marketing/growth/kits/MKT-2026-10-AWS-MARKET.md b/marketing/growth/kits/MKT-2026-10-AWS-MARKET.mdnew file mode 100644index 000000000..8920e6cdb--- /dev/null+++ b/marketing/growth/kits/MKT-2026-10-AWS-MARKET.md@@ -0,0 +1,173 @@+# MKT-2026-10-AWS-MARKET: enterprise procurement in front of agent-native pay-per-call usage++**Kit status:** copy complete and **held**. The AWS Marketplace listing does not exist yet (campaigns.csv+status `awaiting_listing`), and production cannot accept a subscriber: on 2026-09-17+`POST https://three.ws/api/aws-marketplace/subscription` answered `{"error":"not_configured"}`. Every+"is live" sentence below stays unpublished until a buyer can subscribe end to end.++## At a glance++| Field | Value |+|---|---|+| Campaign id | `MKT-2026-10-AWS-MARKET` |+| Publish date | 2026-10-20, or the first business day after AWS reviews the launch copy, whichever is later |+| Summary | three.ws becomes subscribable in AWS Marketplace: a free subscription links an AWS account to a three.ws access key, and agents pay per call over HTTP 402 for what they use |+| Audience | enterprise buyers and cloud builders |+| Primary channel | AWS Marketplace launch (the listing itself) |+| Secondary channels | AWS Builder Center, LinkedIn, X, three.ws news |+| Proof | https://three.ws/aws |+| Tracked links | X `https://three.ws/aws?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-10-aws-market&utm_content=anchor`; LinkedIn `...utm_source=linkedin&utm_medium=social&...&utm_content=post`; Builder Center `...utm_source=aws-builder-center&utm_medium=partner&...&utm_content=launch-note`; AWS repost `...utm_source=aws&utm_medium=partner&...&utm_content=partner-repost` |+| The single CTA | Open the listing or request a demo |+| Partner ask | Review the launch assets and repost the live announcement |+| KPI | listing visits, agreements, and AWS amplification |++`{{LISTING_URL}}` is the public AWS Marketplace product URL, available after Seller Operations publishes+the product (7 to 10 business days per the listing kit). `{{PRODUCT_ID}}` is the product id the+Management Portal assigns.++## Audit: what already exists++| Channel | Existing asset | State | How this kit uses it |+|---|---|---|---|+| The listing (primary) | [docs/aws-marketplace-listing-kit.md](../../../docs/aws-marketplace-listing-kit.md) | Fields drafted; prerequisites unmet | Is the primary channel. Its short description and highlights need an owner rewrite before submission: they name specific third-party crypto projects, which this kit deliberately does not repeat |+| Backend reference | [docs/aws-marketplace.md](../../../docs/aws-marketplace.md) | Current | Source for the env and IAM steps |+| AWS Builder Center long-form | [docs/aws-builder-center.md](../../../docs/aws-builder-center.md) (two published articles), [docs/aws-partner-spotlight.md](../../../docs/aws-partner-spotlight.md) | Published and drafted | Unchanged; this kit adds the short launch note |+| Social launch copy, news, AWS review and repost messages | none | Missing | Written below |++## Blockers, in order++1. From seller account `155407237916`, create the metering IAM key and the EventBridge relay secret+ listed in [docs/aws-marketplace.md](../../../docs/aws-marketplace.md) and set them on `three-ws-api`+ with `gcloud run services update --update-env-vars` (config-only, pre-approved).+2. Rewrite the listing short description and highlights around the 3D agent product, then create the+ product in the AWS Marketplace Management Portal and wait for publication.+3. Send this kit's copy to AWS for review (message 1), then publish.++## X++**Media:** capture the live `{{LISTING_URL}}` product page at 1600x900 on launch day. Do not reuse a+`/aws` capture: that page's hero names a specific payment token, which this kit keeps out.+**Alt text:** The three.ws product page in AWS Marketplace, showing the free subscription option.++**Anchor** (171 weighted characters):++```text+three.ws is live in AWS Marketplace. A free subscription links your AWS account to an access key; agents then pay per call over HTTP 402: https://three.ws/aws?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-10-aws-market&utm_content=anchor @awscloud+```++**Thread (optional):**++2/+```text+Why split it that way: procurement and vendor onboarding happen once, through the AWS account you already manage. Usage is paid per call, so an agent's spend follows the work it actually does.+```++3/+```text+How we put AWS Marketplace metering in front of an HTTP 402 API, written for the AWS Builder Center: https://builder.aws.com/content/3ESpll50BdSp9eiCEIxcfG9pGUN/how-we-metered-a-saas-product-through-aws-marketplace-with-the-aws-sdk-for-javascript-v3+```+++```text+Enterprise teams that want to try AI agents with a visible 3D presence usually stall at the same step: vendor onboarding.++three.ws is now available in AWS Marketplace. Subscribing is free. The subscription links your AWS account to a three.ws account and issues an access key, so procurement, account ownership, and cancellation run through the AWS account your organization already manages. Usage is then paid per call over HTTP 402, so what an agent spends tracks the calls it actually makes rather than a seat count.++What the key unlocks: browser-native 3D AI agents that embed on any page with one tag, and the pay-per-call tools those agents use.++The integration is open source, and we wrote up how the AWS Marketplace side works on the AWS Builder Center.++three.ws is an AWS Partner.++Open the listing: {{LISTING_URL}}+```++(125 words; one link. Tracked alternative if the listing URL does not unfurl:+`https://three.ws/aws?utm_source=linkedin&utm_medium=social&utm_campaign=mkt-2026-10-aws-market&utm_content=post`.)++## AWS Builder Center launch note++**Title:** three.ws is now subscribable in AWS Marketplace++```text+The AWS Marketplace listing for three.ws is live: {{LISTING_URL}}++What subscribing does: the subscription is free. It links your AWS account to a three.ws account through the SaaS fulfillment flow and issues an access key. Usage is then paid per call over HTTP 402, exactly as for any other caller, so AWS Marketplace handles procurement and the account relationship while each call carries its own payment.++If you read our earlier article on putting Marketplace metering in front of an HTTP 402 API, this is that integration in production. One change since it was published: new products use Concurrent Agreements and EventBridge notifications, so buyers are keyed by license rather than by customer identifier.++Questions from builders wiring the same pattern are welcome in the comments.+```++## three.ws news blurb++three.ws is now available in AWS Marketplace. The subscription is free and links an AWS account to a+three.ws access key, and usage is paid per call over HTTP 402, so organizations can adopt three.ws+through AWS procurement they already use. Listing: {{LISTING_URL}}.++## Partner messages++AWS's [seller marketing guidance](https://docs.aws.amazon.com/marketplace/latest/userguide/product-marketing.html)+says AWS reviews blogs, tweets, and other non-press announcements before they go public, asks sellers to+notify AWS when they post and will "do our best to repost", and routes press release review through the+seller's account manager. Address both messages to the AWS Marketplace account manager assigned in the+Management Portal; no name is recorded in the repo.++**1. Review request, as soon as the listing is published:**++```text+Subject: three.ws launch announcement for review ({{PRODUCT_ID}})++Our SaaS product {{PRODUCT_ID}} is published at {{LISTING_URL}}. Per the AWS Marketplace seller marketing guidance, attached for review before anything is posted:++1. X post and thread (text attached)+2. LinkedIn post (text attached)+3. AWS Builder Center launch note (text attached)+4. Product page screenshot and alt text++None of it describes the relationship as a partnership or alliance, and there is no press release. We plan to post on {{PLANNED_POST_DATE}} once you confirm, and will send the live links the same day.+```++**2. Notify and repost request, the day it posts:**++```text+Subject: three.ws AWS Marketplace announcement is live++The reviewed announcement is now posted:+X: {{X_POST_URL}}+LinkedIn: {{LINKEDIN_POST_URL}}+AWS Builder Center: {{BUILDER_CENTER_URL}}++Your guidance mentions AWS may repost seller announcements to increase visibility; we would be grateful for a repost of the X or LinkedIn post.+```++## T+7 result fields++| Field | Source |+|---|---|+| Listing visits | AWS Marketplace Management Portal, listing traffic report |+| Agreements (subscriptions) | Management Portal agreements view; `aws_marketplace` customer rows in production |+| Landing sessions | web analytics, `utm_campaign=mkt-2026-10-aws-market` |+| AWS amplification | repost or comment URL, or "none" |++## Claims check++| Claim | Proof | Verified |+|---|---|---|+| Listing not live; subscription endpoint not configured | `POST /api/aws-marketplace/subscription` returned `not_configured` | 2026-09-17 |+| Subscription is free; links an AWS account and issues an access key; usage paid per call over HTTP 402 | [docs/partners.md](../../../docs/partners.md) AWS section; `/aws` page cards "Free AWS subscription" and "One key, every x402 endpoint" | 2026-09-17 |+| AWS Partner, Software Path | `/aws` badge; [docs/partners.md](../../../docs/partners.md) | 2026-09-17 |+| The Builder Center metering article exists | [docs/aws-builder-center.md](../../../docs/aws-builder-center.md), article 1 | repo |+| Concurrent Agreements and EventBridge, keyed by license | same doc, "Since publication" | repo |+| AWS reviews non-press announcements and may repost; press releases must not say partnership | AWS seller marketing guidance page | 2026-09-17 |+| Integration code is open source | `api/aws-marketplace/` in the Apache-2.0 repo | repo |++Dropped: "bill usage to your AWS invoice" and commitment drawdown (removed from `/aws` on 2026-09-16 as+untrue), VPC deployment and IAM-integrated access from the `/partners` card (not provable from the code),+and every payment token or chain name.++## Owner does++Set the AWS Marketplace env vars on `three-ws-api`, create the product in the Management Portal, and when+it publishes, send review message 1 with this kit's copy.diff --git a/marketing/growth/kits/MKT-2026-10-ELEVEN-BODY.md b/marketing/growth/kits/MKT-2026-10-ELEVEN-BODY.mdnew file mode 100644index 000000000..b10f22407--- /dev/null+++ b/marketing/growth/kits/MKT-2026-10-ELEVEN-BODY.md@@ -0,0 +1,135 @@+# MKT-2026-10-ELEVEN-BODY: a voice agent becomes a speaking, expressive 3D body++**Kit status:** copy complete, verified 2026-09-17. Written to the production reality: **ElevenLabs runs+on three.ws only with a bring-your-own ElevenLabs key.** `GET /api/tts/catalog` reports the ElevenLabs+lane `available: false`, `byok: true`, reason "Add your own ElevenLabs key below", and there is no+platform ElevenLabs account. The grant ask (campaigns.csv status `awaiting_eligibility`) is gated on the+owner confirming headcount under 25.++## At a glance++| Field | Value |+|---|---|+| Campaign id | `MKT-2026-10-ELEVEN-BODY` |+| Publish date | 2026-10-27 |+| Summary | Paste your own ElevenLabs key, give a three.ws agent your voice, and the avatar's mouth moves with the audio on every page it is embedded on |+| Audience | voice AI builders |+| Primary channel | X |+| Secondary channels | LinkedIn, Telegram community, three.ws news |+| Proof | https://three.ws/voice |+| Tracked links | X `https://three.ws/voice?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-10-eleven-body&utm_content=anchor`; LinkedIn `...utm_source=linkedin&utm_medium=social&...&utm_content=post`; Telegram `...utm_source=telegram&utm_medium=community&...&utm_content=announce` |+| The single CTA | Create a voice-enabled agent and share the clip |+| Partner ask | Startup Grant review and Demo Day consideration |+| KPI | voice setup completions and partner response |++## Audit: what already exists++| Channel | Existing asset | State | How this kit uses it |+|---|---|---|---|+| Grant application answers | [marketing/partner-packets/elevenlabs-startup-grants.md](../../partner-packets/elevenlabs-startup-grants.md) | Ready, eligibility unconfirmed | Is the partner message; not duplicated |+| Application core | [templates.md, ElevenLabs Startup Grants application core](../templates.md) | Ready | Superseded by the packet, which corrects it for BYOK |+| Voice Lab doc | [docs/voice-lab.md](../../../docs/voice-lab.md) | Current | Source for BYOK and model claims |+| Media | [partner-packets/images/voice-lab-elevenlabs.png](../../partner-packets/images/voice-lab-elevenlabs.png) | Exists (captured 2026-09-16) | Anchor image |+| X, LinkedIn, Telegram, news | none | Missing | Written below |++## X++**Media:** `marketing/partner-packets/images/voice-lab-elevenlabs.png`; better, a 15-second clip of a+voiced agent speaking on its embed page once recorded.+**Alt text:** The "Use Your Own ElevenLabs Key" section of three.ws Voice Lab, with an API key field and+per-character pricing.++**Anchor** (179 weighted characters):++```text+Bind your ElevenLabs voice to a three.ws agent and every visitor hears it from a 3D body whose mouth moves with the audio. Paste your own key in Voice Lab: https://three.ws/voice?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-10-eleven-body&utm_content=anchor+```++**Thread (optional):**++2/ (155)+```text+The key is used for that one request and never stored. Flash v2.5 is the default model for low latency; Turbo v2.5 and Multilingual v2 are one select away.+```++3/ (144)+```text+Clone your voice from a short recording, bind it to your agent, and the embed speaks to anonymous visitors on your account, rate limited per IP.+```++No ElevenLabs account is tagged: three.ws has no relationship with ElevenLabs (packet wording rule), and+tagging before any response reads as a claim.+++```text+Most voice agents are a waveform in a corner of the screen. We wanted the voice to have a face.++In three.ws Voice Lab you can paste your own ElevenLabs API key, pick a voice or clone your own from a short recording, and bind it to a 3D agent. From then on the agent speaks in that voice wherever it is embedded, and the avatar's mouth moves with the actual audio rather than a looping talk animation. The calls run on your ElevenLabs account, and the key is used per request and never stored.++Flash v2.5 is the default for low latency, with Turbo v2.5 and Multilingual v2 available. The same agent can be put on any web page with one tag, and the platform is open source.++three.ws integrates the ElevenLabs API; it is not affiliated with or endorsed by ElevenLabs.++Give your agent a voice: https://three.ws/voice?utm_source=linkedin&utm_medium=social&utm_campaign=mkt-2026-10-eleven-body&utm_content=post+```++(154 words.)++## Telegram community++```text+Give your three.ws agent your own voice.++Voice Lab takes your own ElevenLabs API key: pick a voice or clone yours from a short recording, bind it to your agent, and the 3D avatar speaks it with its mouth following the audio, on every page the agent is embedded on. Calls run on your ElevenLabs account; the key is never stored.++Share a clip of your agent talking in the community chat.+https://three.ws/voice?utm_source=telegram&utm_medium=community&utm_campaign=mkt-2026-10-eleven-body&utm_content=announce+```++## three.ws news blurb++three.ws Voice Lab lets you bring your own ElevenLabs key, clone or choose a voice, and bind it to a 3D+agent, so the avatar speaks in that voice with lip-sync driven by the real audio wherever it is embedded.+Calls run on your own ElevenLabs account and the key is used per request, never stored.++## Partner message++Submit the application in [marketing/partner-packets/elevenlabs-startup-grants.md](../../partner-packets/elevenlabs-startup-grants.md)+at `https://elevenlabs.io/grants-application` (terms checkbox, then the application), from a three.ws+business address, only after confirming headcount under 25. Two adjustments on submission day:++1. Replace its platform stats line with a fresh read of `https://three.ws/api/platform/stats`.+2. Keep its Demo Day ask pointed at a **future** Demo Day: the 2026 edition on 2026-10-21 is already cast.++This campaign's X post goes out whether or not the grant is decided; do not mention the application in+public copy until ElevenLabs accepts it.++## T+7 result fields++| Field | Source |+|---|---|+| Voice setup completions | production logs for `/api/tts/eleven` requests with `x-tts-billing: byok` or `agent_byok` in the window |+| Clones created | `/api/tts/eleven-clone` success count in logs |+| Landing sessions | web analytics, `utm_campaign=mkt-2026-10-eleven-body` |+| Partner response | grant decision email, or "pending" |++## Claims check++| Claim | Proof | Verified |+|---|---|---|+| ElevenLabs lane is bring-your-own-key only | `GET https://three.ws/api/tts/catalog`: `elevenlabs` `available: false`, `byok: true` | 2026-09-17 |+| Key used per request, never stored | [docs/voice-lab.md](../../../docs/voice-lab.md), BYOK section; `x-eleven-key` handling in `api/tts/eleven.js` | 2026-09-17 |+| Agent bound voice speaks to anonymous visitors, rate limited per IP, on the owner's account | `agent_byok` lane in the `api/tts/eleven.js` header comment | 2026-09-17 |+| Clone from a short recording | `api/tts/eleven-clone.js`; [docs/voice-lab.md](../../../docs/voice-lab.md) "Clone" | repo |+| Flash v2.5 default; Turbo v2.5 and Multilingual v2 selectable | `DEFAULT_TTS_MODEL` in `api/_lib/elevenlabs.js`; [docs/voice-lab.md](../../../docs/voice-lab.md) | 2026-09-17 |+| Mouth driven by the real audio | `connectLipSync` in `src/agent-avatar.js` ("viseme morphs are driven from real audio frequency data") | 2026-09-17 |+| No relationship with ElevenLabs | packet "Approved relationship wording" | repo |+| `/voice` is live | HTTP 200 | 2026-09-17 |++Dropped: per-character and per-clone platform prices (they apply to a platform lane that cannot run+today), voice counts, and any usage volume (not measured; BYOK calls bill the user's account).++## Owner does++Publish the X anchor with the Voice Lab image, and confirm headcount so the grant application can go in.diff --git a/marketing/growth/kits/MKT-2026-11-GCP-AGENT.md b/marketing/growth/kits/MKT-2026-11-GCP-AGENT.mdnew file mode 100644index 000000000..db27ee625--- /dev/null+++ b/marketing/growth/kits/MKT-2026-11-GCP-AGENT.md@@ -0,0 +1,137 @@+# MKT-2026-11-GCP-AGENT: a production A2A agent with a browser-native 3D interface++**Kit status:** copy complete and **held behind three blockers.** Nothing announcing a Google Cloud+listing may post until the listing exists; this kit also carries a fallback post that is true today.++## Blockers (verified 2026-09-17)++1. **Vertex AI is billing-denied on the production project.** Cloud Run logs for `three-ws-api` at+ 2026-09-17T03:12Z read `vertex imagen failed, falling back: Lightning dunning decision is deny for+ project: projects/93741856042`. Google's AI agent listing requirements ask an A2A agent to use a Model+ Garden model as its default; production cannot today. Clear the billing hold first.+2. **The Agent Card is not yet a valid Marketplace Agent Card.** `https://three.ws/.well-known/agent-card.json`+ (version 1.5.1, 10 skills) has no `protocolVersion`, no `preferredTransport`, no+ `securitySchemes`/`security` (it uses the older `authentication` key), and its `url` is the website+ `https://three.ws/`, not the A2A endpoint. Full gap table:+ [marketing/partner-packets/google-cloud-ai-agents.md](../../partner-packets/google-cloud-ai-agents.md).+3. **No Partner Network enrollment.** three.ws is a member of Google Cloud for Web3 Startups, not a Google+ Cloud Partner, and has no Marketplace listing (campaigns.csv status `awaiting_enrollment`).++## At a glance++| Field | Value |+|---|---|+| Campaign id | `MKT-2026-11-GCP-AGENT` |+| Publish date | 2026-11-10 (slides until the listing is live) |+| Summary | Enterprise agent builders can discover a three.ws A2A agent in Google Cloud Marketplace that turns a prompt into a rigged, embeddable 3D character, running on the same Cloud Run stack as three.ws |+| Audience | enterprise agent builders |+| Primary channel | Google Cloud Marketplace or the AI agent finder |+| Secondary channels | LinkedIn, X, three.ws news |+| Proof | https://three.ws/.well-known/agent-card.json |+| Tracked links | X `https://three.ws/.well-known/agent-card.json?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-11-gcp-agent&utm_content=fallback`; LinkedIn `https://three.ws/forge?utm_source=linkedin&utm_medium=social&utm_campaign=mkt-2026-11-gcp-agent&utm_content=post` |+| The single CTA | Inspect the Agent Card and run the live agent |+| Partner ask | AI Agents validation and finder placement |+| KPI | agent calls, listing visits, and placement |++`{{LISTING_URL}}` is the Google Cloud Marketplace product page, which exists only after Producer Portal+publication.++## Audit: what already exists++| Channel | Existing asset | State | How this kit uses it |+|---|---|---|---|+| Enrollment path, business case, architecture | [marketing/partner-packets/google-cloud-ai-agents.md](../../partner-packets/google-cloud-ai-agents.md) | Ready; records blockers 1 and 2 | Is the partner-facing material |+| Google Cloud Community long-form | [docs/google-cloud-community-post.md](../../../docs/google-cloud-community-post.md) | Draft | Optional companion; not part of this anchor |+| Production facts | [docs/ops/gcp-production.md](../../../docs/ops/gcp-production.md) | Current | Source for Cloud Run claims |+| Media | [partner-packets/images/forge.png](../../partner-packets/images/forge.png) | Exists | Fallback post image |+| X, LinkedIn, news, finder ask | none | Missing | Written below |++## X++**Launch anchor, only after the listing is live** (175 weighted characters measured with a placeholder+Marketplace URL):++```text+three.ws is listed in Google Cloud Marketplace as an A2A agent: a prompt in, a rigged, embeddable 3D character out, served from Cloud Run: {{LISTING_URL}} @googlecloud+```++**Fallback, true today, if the owner wants the campaign slot used before the listing** (177):++```text+Our Agent Card is public JSON: ten declared skills an agent can read before it calls anything, from avatar search to GLB validation. Served by Cloud Run: https://three.ws/.well-known/agent-card.json?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-11-gcp-agent&utm_content=fallback+```++**Media:** a capture of `{{LISTING_URL}}` for the launch anchor; `forge.png` for the fallback.+**Alt text (fallback):** The three.ws Forge page: a prompt box, quality and engine selectors, and a+Generate button.++## LinkedIn (launch day)++```text+Agents built for the enterprise mostly answer in text. Some questions deserve an object.++three.ws is now available in Google Cloud Marketplace as an AI agent that speaks the A2A protocol. Other agents can read its public Agent Card, see its declared skills, and call it to turn a prompt or a photo into a textured, rigged 3D character that can be inspected, placed in a room in AR, or embedded on a page with one tag.++The agent runs on Google Cloud in production: Cloud Run serves the API, a Cloud Run GPU fleet runs 3D generation, rigging, and motion, and Cloud Scheduler runs the background jobs. Procurement goes through the Google Cloud account your organization already uses.++three.ws is a member of Google Cloud for Web3 Startups.++Find it in Marketplace: {{LISTING_URL}}+```++(128 words; tracked alternative link in the table above if the listing does not unfurl.)++## three.ws news blurb++three.ws is available in Google Cloud Marketplace as an A2A agent: other agents can read its Agent Card+and call it to generate rigged, embeddable 3D characters from a prompt or photo. It runs on the same+Cloud Run and GPU stack that serves three.ws. Listing: {{LISTING_URL}}.++## Partner message++Step 1 has no message: enroll at `https://partners.cloud.google.com/enrollment`. After enrollment, and+only after blockers 1 and 2 are closed, send this to the partner manager Google assigns (no contact name+exists in the repo):++```text+Subject: three.ws A2A agent: AI Agents program validation and agent finder placement++three.ws (Partner ID {{PARTNER_ID}}) runs its production stack on Google Cloud: Cloud Run for the API and a Cloud Run GPU fleet for 3D generation, rigging, and motion. Our A2A agent is onboarded in Producer Portal as {{PRODUCER_PORTAL_PRODUCT}}, with the Agent Card uploaded to Cloud Storage and a Model Garden model as the default.++Two asks: route the agent into AI Agents program validation (and Gemini Enterprise validation if it qualifies), and confirm how an approved listing is placed in the AI agent finder at cloud.withgoogle.com/agentfinder.++The forwardable packet, architecture, and business case are attached.+```++Attach the forwardable packet and architecture section from the Google Cloud packet, with its metrics+re-read on the day.++## T+7 result fields++| Field | Source |+|---|---|+| Listing visits | Producer Portal analytics |+| Agent calls | production logs for the A2A handler (`/api/agents/a2a-paid`) in the window |+| Agent Card fetches | production logs for `/.well-known/agent-card.json` |+| Placement | agent finder URL, or "not placed" |++## Claims check++| Claim | Proof | Verified |+|---|---|---|+| Agent Card is public, version 1.5.1, 10 skills | `curl https://three.ws/.well-known/agent-card.json` | 2026-09-17 |+| Card missing `protocolVersion`, `preferredTransport`, `securitySchemes`; `url` is the website | same fetch, key list | 2026-09-17 |+| Vertex AI billing-denied | Cloud Run log line at 2026-09-17T03:12Z | 2026-09-17 |+| Production runs on Cloud Run with a Cloud Run GPU fleet and Cloud Scheduler | [docs/partners.md](../../../docs/partners.md) Google Cloud section; `/api/version` reports service `three-ws-api` | 2026-09-17 |+| Member of Google Cloud for Web3 Startups; not a Google Cloud Partner; no listing | [docs/partners.md](../../../docs/partners.md), packet relationship wording | repo |+| Prompt or photo to textured, rigged 3D character; AR; one-tag embed | live `forge_free` generation returned GLB and AR URLs on 2026-09-17; `<agent-3d>` web component docs | 2026-09-17 |+| Enrollment and agent finder URLs resolve | both returned HTTP 200 | 2026-09-17 |++Dropped: generation totals and uptime percentages (quoted in the packet with 2026-09-16 capture dates;+re-read on sending day rather than frozen into public copy), and "Vertex AI powers the agent" (false while+billing is denied).++## Owner does++Clear the Vertex billing hold and enroll at `partners.cloud.google.com/enrollment`; the Agent Card fixes+are engineering work that needs no approval.diff --git a/marketing/growth/kits/MKT-2026-11-HF-LOOP.md b/marketing/growth/kits/MKT-2026-11-HF-LOOP.mdnew file mode 100644index 000000000..87672e817--- /dev/null+++ b/marketing/growth/kits/MKT-2026-11-HF-LOOP.md@@ -0,0 +1,135 @@+# MKT-2026-11-HF-LOOP: an agent inspects and corrects its own 3D output++**Kit status:** copy complete, verified 2026-09-17. The loop is live, but **not in the Space.** The+`three-ws/avatar-viewer` Space is a static viewer (Hugging Face API: `"sdk":"static"`), so nobody can+"reproduce a correction loop" there today. The loop runs through two keyless three.ws endpoints,+`POST /api/3d/look` and `GET /api/sim-readiness`, and the kit sends people to those. The primary post (the+Hugging Face article) is a finished draft awaiting owner approval.++## At a glance++| Field | Value |+|---|---|+| Campaign id | `MKT-2026-11-HF-LOOP` |+| Publish date | 2026-11-03 |+| Summary | Text-to-3D returns a binary an agent cannot read; rendering it back as images, grading it mechanically, and diffing iterations gives the agent a loop instead of a guess |+| Audience | ML and open-source developers |+| Primary channel | Hugging Face Community (article under the `three-ws` org) |+| Secondary channels | X, GitHub Discussions, three.ws news |+| Proof | https://huggingface.co/three-ws |+| Tracked links | X `https://huggingface.co/three-ws?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-11-hf-loop&utm_content=anchor`; GitHub `...utm_source=github&utm_medium=community&...&utm_content=discussion`; news `...utm_source=three-ws-news&utm_medium=social&...&utm_content=news` |+| The single CTA | Open the Space and reproduce one correction loop (adjusted: open the article and run one look-and-grade call) |+| Partner ask | Community feature or Space GPU grant review |+| KPI | Space sessions, article reads, and partner response |++## Audit: what already exists++| Channel | Existing asset | State | How this kit uses it |+|---|---|---|---|+| Hugging Face article (primary) | [docs/huggingface-agent-feedback-loop.md](../../../docs/huggingface-agent-feedback-loop.md) | Draft; its `/api/3d/look` example was corrected on 2026-09-17 to send `glb_url` | **Is** the primary post, published from `huggingface.co/new-blog` per the [publishing checklist](../../../docs/huggingface.md#publishing-checklist) |+| X thread for the previous article | [marketing/huggingface-article/post.md](../../huggingface-article/post.md) | Posted beat | Pattern and tag rules only (no coin in anything Hugging Face-facing) |+| Media | [kits/images/huggingface-org.png](./images/huggingface-org.png) (captured 2026-09-17) | Exists | Anchor image until the article has its own cover |+| X anchor, GitHub Discussions, news, grant and feature ask | none | Missing | Written below |++**Rule carried from the Hugging Face index:** AI-focused, no coin, exchange, listing, or token content in+the article or in any post that promotes it. This kit has none.++## X++**Media:** `marketing/growth/kits/images/huggingface-org.png`, replaced by a frame of `look_at_model`+output (four angles of one GLB) once captured.+**Alt text:** The three.ws organization page on Hugging Face: two articles, the Avatar Viewer Space, and+the three-ws/avatars model repository.++**Anchor** (167 weighted characters):++```text+A text-to-3D API returns a binary no agent can read. We render the GLB back as images, grade it, diff it, and let the agent retry: https://huggingface.co/three-ws?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-11-hf-loop&utm_content=anchor @huggingface+```++After the article publishes, swap the link for the article URL with the same UTM parameters.++**Thread (optional):**++2/ (127)+```text+Try the look step with no key: POST a public GLB URL to three.ws/api/3d/look and get one rendered frame per angle back as JSON.+```++3/ (159)+```text+The pieces are on npm under Apache-2.0: @three-ws/see renders, @three-ws/glb-diff compares iterations structurally, @three-ws/retarget drives any humanoid rig.+```++## GitHub Discussions (category: Show and tell)++**Title:** Generate, look, grade, iterate: the feedback loop for agentic 3D, now written up on Hugging Face++```text+We published the third three.ws article on Hugging Face: {{ARTICLE_URL}}++The short version: an agent that generates a GLB cannot perceive it, so it cannot iterate. The loop that fixes that is open and keyless:++1. Look: render the model back into images the agent can see.+ curl -s -X POST https://three.ws/api/3d/look -H 'content-type: application/json' -d '{"glb_url":"https://three.ws/avatars/cesium-man.glb"}'+2. Grade: a mechanical physics-readiness verdict.+ curl -s "https://three.ws/api/sim-readiness?glb_url=https://three.ws/avatars/cesium-man.glb"+3. Diff: @three-ws/glb-diff says whether the last change did anything structural.+4. Retarget: @three-ws/retarget drives any humanoid rig without an allowlist.++Run step 1 or 2 on a model of your own and post what the grade got wrong. Disagreements with the verdict are the most useful replies.+```++## three.ws news blurb++Our third Hugging Face article explains how three.ws closes the feedback loop for agentic 3D: the agent+renders its own GLB back into images, gets a mechanical physics-readiness grade, and diffs each iteration+before it tries again. Both the look and grade steps are free, keyless endpoints anyone can call today.+Read it on Hugging Face: {{ARTICLE_URL}}.++## Partner asks++Hugging Face publishes two self-serve routes; no Hugging Face contact name is in the repo, and neither+route needs one.++1. **Community feature:** publish the article under the `three-ws` organization. Community articles are+ the surface Hugging Face features from; there is no separate feature form, so the ask is the article+ itself plus the replies it earns.+2. **Space GPU grant: hold.** Hugging Face's docs say the community GPU grant application sits in the+ Space's settings (hardware section). The current Space is static and needs no GPU, so applying now+ asks for hardware it would not use. Apply only after the Space is upgraded into the look-and-grade+ loop from the opportunity register, with this justification:++```text+The three.ws feedback-loop Space renders a user's GLB from several angles, grades its physics readiness, and shows the diff between two iterations, so anyone can watch an agentic 3D loop run on their own model. Rendering and grading run server-side today; a GPU would let the Space render in-process and stay responsive under load. The code is Apache-2.0 and the article explaining it is {{ARTICLE_URL}}.+```++## T+7 result fields++| Field | Source |+|---|---|+| Article reads and upvotes | the article page on Hugging Face (upvote count; views where shown) |+| Space sessions | Space analytics in the `three-ws` org settings |+| Look and grade calls | production logs for `/api/3d/look` and `/api/sim-readiness` in the window |+| Landing sessions | web analytics, `utm_campaign=mkt-2026-11-hf-loop` |+| Partner response | feature, comment, grant decision, or "none" |++## Claims check++| Claim | Proof | Verified |+|---|---|---|+| `POST /api/3d/look` is keyless and returns a frame per angle | live call with `glb_url` returned `views[]` each with `image_url` | 2026-09-17 |+| `/api/sim-readiness` is keyless and returns a verdict | live call returned `verdict: "simulation_ready"` with mass, scale, collision fields | 2026-09-17 |+| `@three-ws/see`, `@three-ws/glb-diff`, `@three-ws/retarget` are on npm | `npm view` returned 0.1.0, 0.1.0, 0.1.2 | 2026-09-17 |+| Apache-2.0 | `gh repo view nirholas/three.ws` | 2026-09-17 |+| The org has two articles, one Space, one model | https://huggingface.co/three-ws (capture) and HF API | 2026-09-17 |+| The Space is static | `https://huggingface.co/api/spaces/three-ws/avatar-viewer`: `"sdk":"static"` | 2026-09-17 |+| GPU grant is applied for from Space settings | https://huggingface.co/docs/hub/spaces-gpus, "Community GPU Grants" | 2026-09-17 |++Dropped: "reproduce a correction loop in the Space" (not possible in a static Space) and any follower or+like counts (move daily).++## Owner does++Publish `docs/huggingface-agent-feedback-loop.md` from `huggingface.co/new-blog` under the `three-ws`+organization, then post the X anchor with the article URL.diff --git a/marketing/growth/kits/MKT-2026-11-QUICKNODE.md b/marketing/growth/kits/MKT-2026-11-QUICKNODE.mdnew file mode 100644index 000000000..73d5a2d34--- /dev/null+++ b/marketing/growth/kits/MKT-2026-11-QUICKNODE.md@@ -0,0 +1,140 @@+# MKT-2026-11-QUICKNODE: how the production RPC path fails over without losing the user++**Kit status:** copy complete, verified 2026-09-17. Not blocked on engineering. campaigns.csv status+`awaiting_outreach`: the spotlight email and field note are ready and unsent, and the program contact's+name is not recorded in the repo.++## At a glance++| Field | Value |+|---|---|+| Campaign id | `MKT-2026-11-QUICKNODE` |+| Publish date | 2026-11-17 |+| Summary | A candid field note: how a metered Quicknode reserve silently became the Solana RPC primary, and the four rules that now keep a multi-provider failover chain honest |+| Audience | Solana developers |+| Primary channel | Quicknode community or blog (Feature Friday or founder spotlight) |+| Secondary channels | X, GitHub Discussions, three.ws news |+| Proof | https://three.ws/docs/solana |+| Tracked links | X `https://three.ws/docs/solana?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-11-quicknode&utm_content=anchor`; GitHub `...utm_source=github&utm_medium=community&...&utm_content=discussion`; partner email `...utm_source=quicknode&utm_medium=email&...&utm_content=field-note` |+| The single CTA | Read the field note and test the open implementation |+| Partner ask | Founder spotlight or co-authored technical post |+| KPI | doc reads, repo visits, and partner placement |++## Audit: what already exists++| Channel | Existing asset | State | How this kit uses it |+|---|---|---|---|+| Partner ask (primary route) | [marketing/partner-packets/quicknode-spotlight-ask.md](../../partner-packets/quicknode-spotlight-ask.md) | Ready | Is the partner message, with one refresh below |+| Field note | [marketing/partner-packets/quicknode-rpc-failover-field-note.md](../../partner-packets/quicknode-rpc-failover-field-note.md) | Ready; one sentence now stale (below) | Attachment and the source for every post |+| Program membership graphics | [marketing/quicknode/](../../quicknode/) | Exist | Not used; this is a technical beat, not a membership beat |+| Media | [partner-packets/images/docs-solana-failover.png](../../partner-packets/images/docs-solana-failover.png) | Exists | Anchor image |+| X, GitHub Discussions, news | none | Missing | Written below |++**Stale sentence to fix before sending the field note:** it says the recovery-probe change from commit+`ac1ba86ad` is "not yet deployed". On 2026-09-17 that commit is an ancestor of the live commit+`477eb6f8c` from `/api/version`, so it has shipped. Change the sentence to "deployed" with the date of the+deploy that carried it.++## X++**Media:** `marketing/partner-packets/images/docs-solana-failover.png`.+**Alt text:** three.ws Solana docs explaining never to name the same endpoint as both primary and reserve,+followed by the cooldown table for failing RPC endpoints.++**Anchor** (170 weighted characters):++```text+We once set our metered @Quicknode reserve as the Solana RPC primary too. The chain keeps the first copy of a URL, so the reserve took every call: https://three.ws/docs/solana?utm_source=x&utm_medium=social&utm_campaign=mkt-2026-11-quicknode&utm_content=anchor+```++This is a correction lead (voice contract pattern 3). The tag is defensible: the Quicknode endpoint is a+real rung in the production chain. The post does not blame Quicknode; the misconfiguration was ours.++**Thread (optional):**++2/ (210)+```text+The fix was a rule, not code: a reserve URL appears in the reserve list and nowhere else. Then we sized the bench to the failure: 6h on quota, 30m on a bad key, 10m on a 429, 2m on a 5xx, 30s on a network blip.+```++3/ (192)+```text+A 403 is not always a bad key. Some providers refuse one call shape and serve the rest, so now only that method is demoted on that endpoint, for 15 minutes, instead of benching the whole lane.+```++4/+```text+When every lane fails, the last good answer for the same read is served with an x-solana-rpc-stale header carrying its age, instead of an error. The code: https://github.com/nirholas/three.ws/blob/main/api/_lib/solana/connection.js+```++## GitHub Discussions (category: Show and tell)++**Title:** Field note: running a Solana RPC failover chain in production++```text+We wrote up what running a multi-provider Solana RPC failover chain in production taught us, including the day our metered reserve quietly became the primary.++Four rules we now hold:+1. Dedupe order is policy. The chain keeps the first copy of a URL, so a reserve must appear in the reserve list and nowhere else.+2. Size the bench to the failure: 6 hours on quota exhaustion, 30 minutes on a bad key, 10 minutes on a 429, 2 minutes on a provider 5xx, 30 seconds on a network error.+3. A 403 can be one method, not the lane: demote that method on that endpoint for 15 minutes.+4. Breakers are fleet-wide, so a new instance inherits "this lane is out of quota" instead of paying to learn it.++Docs: https://three.ws/docs/solana?utm_source=github&utm_medium=community&utm_campaign=mkt-2026-11-quicknode&utm_content=discussion+Code: api/_lib/solana/connection.js++If you run more than one RPC provider, what cooldowns do you use, and what did you get wrong first?+```++## three.ws news blurb++We published a field note on how three.ws keeps Solana RPC calls alive across several providers, starting+with the misconfiguration that turned our metered reserve into the primary. It covers dedupe order,+cooldowns sized to each failure class, per-method demotion for call-shape errors, and fleet-wide breakers,+with links to the open code. Read it in the Solana docs: https://three.ws/docs/solana.++## Partner message++Send the email in [marketing/partner-packets/quicknode-spotlight-ask.md](../../partner-packets/quicknode-spotlight-ask.md)+as a reply in the existing Quicknode Startup Program thread, with the field note attached. Refresh before+sending:++1. Fill `[program contact first name]` and `[Owner name]` from the real thread; neither is in the repo.+2. Its two proposed Fridays (2026-10-16, 2026-10-23) precede this campaign's date. Replace them with two+ Fridays after sending, for example 2026-11-20 and 2026-12-04, and confirm both are free.+3. Fix the stale "not yet deployed" sentence in the field note (above).+4. Swap the docs link in the email for the tracked+ `https://three.ws/docs/solana?utm_source=quicknode&utm_medium=email&utm_campaign=mkt-2026-11-quicknode&utm_content=field-note`.++If no thread exists in the owner's inbox, the packet names the public routes:+`https://www.quicknode.com/contact-us` and the Quicknode Discord.++## T+7 result fields++| Field | Source |+|---|---|+| Doc reads | web analytics, `/docs/solana` sessions with `utm_campaign=mkt-2026-11-quicknode` |+| Repo visits | GitHub Insights traffic for the week |+| Discussion replies | the Show and tell thread |+| Partner placement | Feature Friday slot, blog post URL, or "no response" |++## Claims check++| Claim | Proof | Verified |+|---|---|---|+| Production named the metered reserve as primary until 2026-07-28; `-32003` daily cap | [docs/solana.md](../../../docs/solana.md) line 71 | 2026-09-17 |+| Chain dedupes by URL and keeps the first occurrence | same doc; `solanaRpcEndpoints()` in `api/_lib/solana/connection.js` | 2026-09-17 |+| Cooldowns 6h, 30m, 10m, 2m, 30s | `QUOTA_COOLDOWN_MS`, `AUTH_COOLDOWN_MS`, `RATE_LIMIT_COOLDOWN_MS`, `SERVER_COOLDOWN_MS`, `NETWORK_COOLDOWN_MS` in `connection.js` | 2026-09-17 |+| Per-method demotion for 15 minutes | `METHOD_DEMOTION_MS = 15 * 60_000` in `connection.js` | 2026-09-17 |+| Last good answer served with `x-solana-rpc-stale` | `connection.js` around line 340 | 2026-09-17 |+| Fleet-wide breakers | field note source table; `rpcLaneHealth()` comment in `connection.js` | repo |+| Member of the Quicknode Startup Program; Quicknode is a rung, not the whole chain | [docs/partners.md](../../../docs/partners.md) | repo |+| Recovery-probe commit `ac1ba86ad` is deployed | `git merge-base --is-ancestor ac1ba86ad 477eb6f8c` succeeds; `/api/version` commit `477eb6f8c` | 2026-09-17 |++Dropped: the point-in-time "all lanes cooling" health reading from 2026-09-16 (a snapshot, not a claim to+repeat publicly), and request volume through Quicknode (not measured in the repo).++## Owner does++Reply in the existing Quicknode Startup Program thread with the refreshed email and field note, then post+the X anchor with the docs image.