Error handling

HTTP status codes

| Status | Meaning |

|--------|---------|

| `200` | Analysis succeeded |

| `400` | Invalid request or malformed configuration |

| `401` | Missing, invalid, or revoked API key |

| `403` | API access requires Pro plan or Team entitlement |

| `413` | Configuration exceeds 1 MB limit |

| `429` | Rate limit exceeded |

| `503` | API unavailable (database not configured) |

Common symptoms

| Symptom | Likely cause |

|---------|--------------|

| 401 Missing Authorization | No Bearer header |

| 401 Invalid API key | Wrong key or typo |

| 401 Revoked | Key was revoked |

| 403 Pro plan required | Account is on Individual plan without API access |

| 429 Too many requests | Per-key rate limit exceeded |

| 413 Payload too large | Configuration exceeds 1 MB |

Error responses use safe messages only. API keys, tokens, and configuration secrets are never echoed in error payloads.