What Wavefront is and how it works
Wavefront plans a content strategy for your site, drafts and fact-checks posts, waits for your approval, then publishes to the tools you already use.
Updated
Wavefront plans content for your site, drafts it, checks every claim against its sources, and publishes it once a person on your team approves it. You give it direction once, and it keeps a calendar of posts moving from idea to published page.
What Wavefront does for a workspace
A workspace is one site or business, with its own team, documents, plan and settings. Inside a workspace, Wavefront:
- Plans. The strategist reads your site, searches your topics and competitors, and proposes a brief, a voice, pillars, keywords and a dated calendar. You refine it by chatting, then save it.
- Drafts. Each calendar post becomes a draft: an article, a short piece of copy (a LinkedIn or X post, a newsletter, a meta description) or an image. Drafts read your workspace documents, so they follow your voice and rules.
- Checks. Articles are researched, cited and fact-checked. Claims that no source supports, figures that aren’t in the evidence and copied passages are flagged, and Wavefront fixes what it can before a person sees the draft.
- Waits for a person. Drafts land in Review. An owner or editor approves a version, or asks for changes and a revision.
- Publishes. Approved work goes to a destination such as WordPress, Webflow, Ghost, Shopify, HubSpot, a newsletter tool, LinkedIn or X, now or on a schedule. Publishing a later version updates the same page.
- Learns from search data. With Search Console, Google Analytics or Bing Webmaster Tools connected, Wavefront suggests refreshes, new ideas and fixes based on how your pages perform.
A person approves before anything is published
An owner or editor approves a version in the web app, or asks their connected agent to. An API key can approve only with the approve scope, which an owner adds on purpose. Nobody can approve a version with blockers, and each approval records who approved it and how.
The one exception is auto-approve, which only an owner can turn on, for autopilot’s own calendar drafts. Even then, only drafts with zero blockers pass, and anything written by an agent or API key that isn’t an owner’s never qualifies. See autopilot and auto-approve.
Three ways to use the same workspace
The web app, the REST API and the MCP server share one core. Work started in one shows up in the others, with the same documents, rules, approvals and credits.
| Way in | Who uses it | How it signs in |
|---|---|---|
| Web app | People planning, reviewing, approving and publishing | An emailed code or Google |
| REST API | Scripts, CI, Zapier, Make and n8n | A workspace API key |
| MCP server | AI agents such as ChatGPT, Claude, Grok and Cursor | OAuth, as the person who connects it |
To connect an agent, see connect an AI agent. For scripts, see API keys and webhooks and the developer docs.
What you pay for
Wavefront has one plan that includes every feature. Drafting uses credits from the plan; talking to the strategist and editing a plan don’t. A new account gets a free trial with credits and no card. See your plan and credits and the pricing page.
Where to start
- Start your trial.
- Set up your workspace on the welcome screen.
- Plan with the strategist.
- Draft your first post, then review and approve it.
- Publish your first post.
If this guide didn't cover it, email support@adwave.com with your workspace name and what you were doing.