Skip to main content
The Agents API is the REST interface to Writesonic Agents. It exposes the same capabilities as the Agents MCP server: read your projects, create and manage tasks, inspect playbooks and grids, search knowledge, and pull content-intelligence reports, all as plain HTTP endpoints you can call from any language.
Agents is in beta. Access is currently limited to selected enterprise and agency accounts. To request it, talk to your account manager or book a demo with our sales team.

​
Base URL

All endpoints are mounted under /api/v1/business. Every request is a JSON POST (a few reads are GET), and every response is JSON.

​
Authentication

Every request requires your Writesonic API key in the X-API-Key header.

​
How to find your API key

1

Log in to Writesonic

Go to app.writesonic.com and sign in.
2

Open the API Dashboard

Hover over your profile picture in the top-right corner and select API Dashboard.
3

Activate the API

Switch the activation toggle on to enable API access.
4

Reveal your API key

Click Reveal API Key and copy it.
Never commit your API key to a public repository or ship it in client-side code. Use environment variables or a secrets manager.

​
Scoping a request

Your API key is scoped to a single workspace. Most endpoints act on a single project within it, which you name with a request header.
GET /whoami is the one call that needs no X-Project-Id. Call it first, it returns your identity, your teams, and the projects in the active workspace. Use a project’s id from that response as the X-Project-Id header on every other call.

​
Your first request

1

Get your projects

Copy the id of the project you want to work with from the projects array.
2

Query that project's tasks

​
Error responses

​
MCP or REST?

The Agents API and the Agents MCP server are two front doors to the same tools.
  • Reach for REST when you’re writing code, a backend job, a script, an integration.
  • Reach for MCP when you want an AI assistant (Claude, ChatGPT) to call these tools for you in natural language.
Each REST endpoint below maps to one MCP tool of the same name, see the tools reference for the mapping.