Errors
Common HTTP status codes for tool API calls and how to fix them.
Tool API errors
| Status | Cause | Fix |
|---|---|---|
401 | Missing, invalid, or revoked X-Api-Key | Create a new key in the dashboard |
403 | Tool blocked for your plan | Upgrade plan or contact support |
429 | Monthly quota or per-minute rate limit | Check usage in the dashboard or upgrade your plan |
413 | File too large | Reduce upload size per tool limits |
410 | ?delivery=binary no longer supported | Use default JSON downloadUrl response |
500 | Conversion or processing failed | Retry; verify file format and payload |
503 | Service temporarily unavailable | Retry with backoff |
Error body shape
Most errors return JSON:
{
"message": "Human-readable description"
}Quota errors may include extra fields:
{
"message": "Monthly usage limit exceeded for this period",
"type": "monthly_quota",
"current": 500,
"limit": 500
}Need help?
Include the request path, status code, and message when contacting support. Do not share full API keys — use the key prefix only (ty_a1b2).
MCP-specific errors
| Code | Meaning | Fix |
|---|---|---|
tool_not_api_backed | Tool is not API-backed | Use discover_tools for valid tools |
unauthorized | Invalid MCP API key | Set X-Api-Key in MCP client config |
circuit_open | Backend temporarily down | Retry after retryAfterMs |
See MCP quickstart.