What Wavefront is and how it works

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:

1. 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.
2. 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.
3. 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.
4. Waits for a person. Drafts land in Review. An owner or editor approves a version, or asks for changes and a revision.
5. 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.
6. 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

Approval is the center of the product. Only an owner or editor signed in to the web app can approve a version. API keys and AI agents can draft, revise, comment and publish work that is already approved, but they can never approve it.

There is one exception, and it is in an owner’s hands. An owner can turn on auto-approve for autopilot’s own calendar drafts. Even then, only drafts with zero blockers pass, and anything an agent or API key wrote 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

1. Start your trial.
2. Set up your workspace on the welcome screen.
3. Plan with the strategist.
4. Draft your first post, then review and approve it.
5. Publish your first post.