Product & API docs

The whole point of onboarding is to get you to one approved, published article as fast as possible — most people get there in under 10 minutes.

1. 1

   Create an account

   Start free — no credit card. The trial includes a handful of quality-gated articles on the house.

2. 2

   Connect a site

   Point Draftwave at a domain and pick a CMS (WordPress now, Ghost and Webflow next) — or choose Headless API and get a publishable key instantly, the fastest path to value.

3. 3

   Set your brand voice

   A short form (audience, tone, POV, banned phrases) plus a preset. "Test voice" generates a sample paragraph instantly so you feel the tone before generating anything real.

4. 4

   Add topics

   Paste 3–5 seed keywords, import a CSV, or let Draftwave auto-discover and cluster topics from real SERP research — the lowest-effort path.

5. 5

   Generate

   One click runs the full pipeline — research, brief, draft, SEO/AEO structuring, and the quality gate — in a couple of minutes, and shows you the cost.

6. 6

   Review & approve

   Articles land in your review queue as pending_review with a gate scorecard attached. Read it, tweak inline if you like, and approve.

7. 7

   Publish

   Approving ships it — one click to your CMS, or it becomes retrievable from the Content API for headless sites. Set a schedule once you trust the pipeline.

How Draftwave works

One pipeline, six stages, one rule that never bends: nothing publishes without you.

1. 1

   Research

   Real SERP research and keyword clustering — not a guess at what to write.

2. 2

   Brief

   A structured brief (audience, angle, outline, sources) grounded in your Knowledge Base, not generic filler.

3. 3

   Draft

   A cheap, fast model writes the first pass; a stronger model only runs on the final edit pass — cost stays low without cutting corners where it matters.

4. 4

   SEO / AEO structuring

   Schema, FAQ blocks, answer-first headings, internal links, and a GEO score so the piece is built to be cited, not just ranked.

5. 5

   Quality gate

   Deterministic checks plus an LLM-as-judge score against a rubric with hard floors. A draft that fails — especially the non-negotiable 'unique value present' floor — is rejected or auto-revised. It never publishes.

6. 6

   Your review

   Passing the gate means pending_review, not published. You read the scorecard, tweak if you like, and approve. Publishing is a separate, explicit action.

Key features

What a signed-up site actually gets, beyond the core generate-and-publish loop.

Read-only, key-authed, and edge-cached. Only ever returns published content for the key's site — drafts are never exposed. Auth is a pk_live_… publishable key, safe to ship in a browser.

curl "https://cdn.draftwave.io/v1/articles?site=SITE_ID&limit=10" \
  -H "Authorization: Bearer pk_live_xxx"

# → { "data": [ { "slug": "...", "title": "...", "html": "...",
#       "faq": [...], "jsonLd": {...}, "publishedAt": 1719878400000 } ], "nextCursor": null }

Keys come in two kinds: a read-only, origin-lockable publishable key (pk_live_…) for anything that runs in a browser, and a server-side-only secret key (sk_live_…) for scripting generation and management. Draftwave stores only a hash of every key and shows the full key exactly once, at creation. See the full reference for request/response shapes, caching, rate limits, and webhooks.

Publishing destinations

Pick per site — push to a CMS, pull headlessly, or both.

See Auto-publishing & Content API for the full feature-level story on both models.