code and a human-readable message.
Error Format
| Field | Type | Description |
|---|---|---|
error.code | string | Machine-readable error code |
error.message | string | Human-readable explanation |
error.details | object | Field-level validation errors (when applicable) |
Error Codes
| Status | Code | Description |
|---|---|---|
| 400 | VALIDATION_ERROR | Invalid request fields. Check details for specifics. |
| 400 | BAD_REQUEST | Malformed request body or invalid parameters. |
| 401 | UNAUTHORIZED | Missing or invalid API key. |
| 404 | NOT_FOUND | The requested resource does not exist or is not accessible. |
| 409 | CONFLICT | The request conflicts with the current state (e.g., starting a run on a deleted benchmark). |
| 429 | RATE_LIMITED | Too many requests. Wait and retry. |
| 500 | INTERNAL_ERROR | An unexpected error occurred on the server. |
Handling Errors
Check thecode field to determine how to respond programmatically:
Rate Limiting
The API enforces rate limits per API key. When you exceed the limit, you receive a429 response with a Retry-After header indicating how many seconds to wait before retrying.
Validation Errors
Validation errors include adetails object that maps field names to arrays of error messages: