Reference

Errors and troubleshooting

Handle request failures, answer failures, uploads, and long-running discoveries safely.

HTTP errors

400Bad Request

Missing query, invalid area or continuation, or an invalid limit.

401Unauthorized

Missing or invalid bearer token.

413Payload Too Large

Uploaded spatial files exceed configured size limits.

500Server Error

Discovery failed and no useful result response could be produced.

HTTP errors return a JSON object with a safe public error string.

Invalid limit

{
  "error": "limit must be an integer from 1 to 2000."
}

If retrieval succeeds but answer generation fails, the API returns HTTP 200 with answer.status set to failed. Keep and use the GeoJSON results.

For long-running requests, increase the SDK, CLI, or MCP timeout. Set answer to false when you only need GeoJSON.