Start
Wavefront developer docs
Wavefront plans, writes, fact-checks and publishes content for a workspace: articles, short copy such as social posts and newsletters, images, and the content strategy behind them. These docs cover the REST API and the MCP server, for scripts, integrations and AI agents.
Three ways in
The web app, the REST API and the MCP server work on the same workspaces, with the same documents, rules, approvals and credits. Anything an agent or a script starts shows up in the app, and the other way round.
| Way in | For | Signs in with |
|---|---|---|
| Web app | People: planning, reviewing, approving, publishing, settings and billing | An emailed code or Google |
| REST API | Scripts, CI and integrations such as Zapier, Make and n8n, at https://wavefront.adwave.com/v1 | A workspace API key |
| MCP server | AI agents such as Claude, ChatGPT, Cursor and Grok, at https://wavefront.adwave.com/mcp | OAuth, as the person who connects it |
A person approves before anything publishes
Drafts are reviewed and approved in the web app. API keys and MCP agents can start drafts, answer questions, comment, request revisions, schedule and publish, but they can never approve a version: only an owner or editor signed in to the web app can. Publishing and scheduling accept approved versions only, and the approval is checked again when a scheduled post goes out.
One exception is in the owner's hands: an owner can let autopilot approve its own calendar drafts that pass every check. Only a person in the web app can turn that on, and anything an API key or agent wrote never qualifies.
A few more things stay with people in the web app: withdrawing a published page, posting to social networks, sending newsletters, managing members and API keys, connecting accounts and billing. The full list.
Words used in these docs
| Term | Meaning |
|---|---|
| Workspace | One site or business, with its members, documents and settings. Its slug is in every API path: /v1/workspaces/{ws}/… |
| Documents | The brief, voice, rules and references every draft reads (also called the context). |
| Strategy and plan | A content strategy: pillars, keywords and a calendar of planned posts. The strategist helps write it. |
| Generation | One piece of asynchronous work of a kind: article, copy, image or strategy. |
| Version | What a generation produces. A revision makes the next version of the same content item. |
| Destination and publication | A destination is where content goes (WordPress, Webflow, Ghost, a webhook and more); a publication is one version sent there. |
Credits
Drafting uses credits from the workspace's plan. A generation holds credits while it runs and is charged what it used when it finishes. Talking to the strategist and editing a plan are free. Read the balance with GET /v1/workspaces/{ws}/billing/balance (or the wavefront_get_balance tool), and what each kind typically uses with GET …/billing/estimates. When the balance is too low, creating work returns 402 insufficient_funds; the API and MCP need a plan or the trial, otherwise 402 plan_required. See pricing.
Where to next
- Quickstart: your first generation over the API, from key to published post.
- Connect an agent: add Wavefront to Claude, ChatGPT, Cursor or Grok.
- API reference and the raw OpenAPI document.
- Webhooks, errors and the changelog.