DocumentationAPI & MCP
Errors and limits
The error codes, what they mean, and how many calls a minute.
An error answers { "error": { "code": "…", "message": "…" } } with its HTTP status. Over MCP, the tool error’s message is CODE: message. Branch on the code, not on the message.
Error codes
| Status | Code | When |
|---|---|---|
400 | INVALID_INPUT | The body or an argument doesn’t match the operation: details lists the fields at fault. |
401 | MISSING_API_KEY, INVALID_API_KEY, EXPIRED_API_KEY, WORKSPACE_DELETED | No key, an unknown or revoked key, an expired key, or its workspace was deleted. |
402 | INSUFFICIENT_TOKENS | A billed operation, and the workspace’s credits can’t pay for it. |
403 | FORBIDDEN | The key’s creator isn’t allowed to do this in the workspace: the same rule as in the app. |
403 | PLAN_LIMIT_EXCEEDED | The workspace’s plan doesn’t include it: on an account that has never paid, a competitor’s backlinks or a hidden competitor’s analysis. |
404 | NOT_FOUND | No such site, conversation, task… in this workspace. |
409 | CONFLICT | Already running, or in a state that forbids it. |
429 | RATE_LIMITED | Too many requests for the workspace: Retry-After says when to retry. |
503 | SERVICE_UNAVAILABLE | A service the operation needs is briefly unavailable: retry later. |
500 | INTERNAL_ERROR | Our fault: retry later. |
402
{
"error": {
"code": "INSUFFICIENT_TOKENS",
"message": "Workspace is out of tokens for this period."
}
}Rate limits
| Per workspace | |
|---|---|
| API | 120 requests a minute |
| MCP | 30 tool calls a minute |
Over the limit, the answer is 429 RATE_LIMITED, with a Retry-After header that says when to retry.
A question this doesn’t answer? Write to us.

