How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

90 days of the enterprise, pro and team plans free, no card needed. See the plans

OpenSmartRoute

marketing-launch-checklist - Prompt - OpenSmartRoute

Promptv1.0.0

marketing-launch-checklist

Name: marketing-launch-checklist
Author: TrevorPLam

Page: [URL/Route]

by TrevorPLam(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Prompt file imported from TrevorPLam/cloud-gallery (.windsurf/workflows/marketing-launch-checklist.md). Copyright stays with the author.

[MARKETING PRE-FLIGHT: Launch Readiness]

Page: [URL/Route]

Technical Marketing Check:

SEO: Title ≤60 chars? Meta description ≤160 chars? Canonical tag set?
Performance: components used? JavaScript <200KB? Fonts preloaded?
Conversion: CTA visible above fold? Form labels correct? Analytics events firing?
Social: OG image 1200x630? Twitter cards configured? Link unfurls correctly?
Mobile: Touch targets ≥44px? No horizontal scroll? Text readable (≥16px)?
Tracking: UTM params captured? Conversion pixel firing? A/B test variant tagged?

If any check fails, do not deploy. Fix and re-audit.

Category: Marketing Pre-Flight Checklist
Purpose: Run before publishing any marketing page
Frequency: Every marketing page launch (mandatory)
Priority: CRITICAL - Business impact hard gate

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

# [MARKETING PRE-FLIGHT: Launch Readiness]

Page: [URL/Route]

Technical Marketing Check:

1. **SEO**: Title ≤60 chars? Meta description ≤160 chars? Canonical tag set?
2. **Performance**: <Image> components used? JavaScript <200KB? Fonts preloaded?
3. **Conversion**: CTA visible above fold? Form labels correct? Analytics events firing?
4. **Social**: OG image 1200x630? Twitter cards configured? Link unfurls correctly?
5. **Mobile**: Touch targets ≥44px? No horizontal scroll? Text readable (≥16px)?
6. **Tracking**: UTM params captured? Conversion pixel firing? A/B test variant tagged?

If any check fails, do not deploy. Fix and re-audit.

---
**Category**: Marketing Pre-Flight Checklist  
**Purpose**: Run before publishing any marketing page  
**Frequency**: Every marketing page launch (mandatory)  
**Priority**: CRITICAL - Business impact hard gate

Installed into a catalogue, chosen by a router

Install marketing-launch-checklist and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

Photo: RDNE Stock project

For the business

What it costs to adopt - in engineering time.

Same client, same code
One base URL
The OpenAI-compatible endpoint answers your existing SDK calls; model=auto lets the router choose.
The SDKs
One URL, every vendor
No vendor lock-in
Point your OpenAI-compatible client at one address; add, swap or retire providers in the catalogue without touching application code.
Every vendor side by side
Next eligible model answers
Failover built in
When a provider is down or over quota the request moves on; the trace says it did.

Manifest

The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.

trevorplam-cloud-gallery-marketing-launch-checklist-workflow.prompt.jsonjson

{
  "prompt": "# [MARKETING PRE-FLIGHT: Launch Readiness]\n\nPage: [URL/Route]\n\nTechnical Marketing Check:\n\n1. **SEO**: Title ≤60 chars? Meta description ≤160 chars? Canonical tag set?\n2. **Performance**: <Image> components used? JavaScript <200KB? Fonts preloaded?\n3. **Conversion**: CTA visible above fold? Form labels correct? Analytics events firing?\n4. **Social**: OG image 1200x630? Twitter cards configured? Link unfurls correctly?\n5. **Mobile**: Touch targets ≥44px? No horizontal scroll? Text readable (≥16px)?\n6. **Tracking**: UTM params captured? Conversion pixel firing? A/B test variant tagged?\n\nIf any check fails, do not deploy. Fix and re-audit.\n\n---\n**Category**: Marketing Pre-Flight Checklist  \n**Purpose**: Run before publishing any marketing page  \n**Frequency**: Every marketing page launch (mandatory)  \n**Priority**: CRITICAL - Business impact hard gate",
  "variables": [],
  "notes": "Page: [URL/Route]",
  "metadata": {
    "source": {
      "provider": "github-windsurf-workflows",
      "repository": "https://github.com/TrevorPLam/cloud-gallery",
      "path": ".windsurf/workflows/marketing-launch-checklist.md",
      "ref": "e3c0f73b44e70418ce58ee579d1d76e4015e13b8",
      "url": "https://github.com/TrevorPLam/cloud-gallery/blob/e3c0f73b44e70418ce58ee579d1d76e4015e13b8/.windsurf/workflows/marketing-launch-checklist.md",
      "key": "TrevorPLam/cloud-gallery/.windsurf/workflows/marketing-launch-checklist.md"
    }
  }
}

Fetch it by URL: GET /api/v1/registry/trevorplam-cloud-gallery-marketing-launch-checklist-workflow/manifest?version=1.0.0

About

[MARKETING PRE-FLIGHT: Launch Readiness]

Use it

Install marketing-launch-checklist and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Manifest

Reviews