Developers
Build on the same core as the web app
Most of what people do in Wavefront is available to code: start drafts, read versions and checks, publish approved work and react to events. The API and MCP are included in every plan.
Start a draft in one request
A generation runs in the background. Poll it or subscribe to its events, answer any questions it asks, and publish once the version is approved.
- API base
https://wavefront.adwave.com/v1- MCP server
https://wavefront.adwave.com/mcp- OpenAPI
https://wavefront.adwave.com/v1/openapi.json
curl -X POST https://wavefront.adwave.com/v1/workspaces/acme/generations \
-H "Authorization: Bearer $WAVEFRONT_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: 7f3c2a" \
-d '{
"kind": "article",
"input": {
"content_type": "guide",
"title": "How long do coffee beans stay fresh?",
"primary_keyword": "how long do coffee beans last"
}
}'
Each kind's inputs are listed by GET /v1/kinds and in the API reference.
Building blocks
What you can build with
People, agents and code work against one contract and see the same workspace, rules and approvals.
REST API
Generations, versions, review, publishing, schedules, strategies, the backlog, documents and search data, with paged lists and idempotency keys on creates.
MCP server
A remote MCP server over Streamable HTTP with OAuth 2.1 and dynamic client registration, or an API key as a bearer token.
Event webhooks
Signed events when a version is ready, approved or published, with retries and redelivery. Verify signatures with the Standard Webhooks scheme.
Keys and scopes
Workspace API keys with only the scopes they need. Billing and team changes are never available to a key, and a key approves only with the opt-in approve scope.
Zapier, Make and n8n
Recipes that trigger workflows from Wavefront events, or start drafts and add backlog ideas from other tools.
Publish to your own stack
A signed webhook destination, GitHub commits for static and framework sites, or exports as HTML, Markdown, JSON and zip.
Guarantees
Designed so automation can't skip review
Keys and agents can do almost everything people can, but a few decisions still need a person.
- Only approved versions can publish, whoever asks
- Approval needs an owner or editor, a key with the opt-in approve scope, or autopilot under an owner's auto-approve rules
- A version with blockers can't be approved by anyone
- Idempotency keys make retried requests safe
- Every version is immutable and records what it read
- Keys are scoped and reach only their own workspace
/v1changes are additive; breaking changes get a new version
Get an API key with your trial
Start a 7-day trial with 300 credits and every feature, no card needed. After that it's $99 a month.