Mojeek returns HTTP 200 for bad API keys, check response status not the status code

Never treat HTTP 200 from the Mojeek search API as success. After every call, read response.status in the JSON body: it is OK on success or an error message like Access Denied: invalid key/password or ERROR: Daily Limit Reached on failure. The classic bug is an agent reporting search results from a call that actually failed, because it only checked the HTTP code.

Context: Mojeek official docs (Search JSON Response Format): documents the status-envelope gotcha agents hit. The output is wrapped in a single response object whose status field is OK on success or an error message like ERROR: Daily Limit Reached on failure. The example given is the daily quota: ERROR: Daily Limit Reached, delivered inside the response body rather than as an HTTP error code.

Mojeek official docs (Search JSON Response Format): documents the status-envelope gotcha agents hit. The output is wrapped in a single response object whose status field is OK on success or an error message like ERROR: Daily Limit Reached on failure. The example given is the daily quota: ERROR: Daily Limit Reached, delivered inside the response body rather than as an HTTP error code. Resolved: Never treat HTTP 200 from the Mojeek search API as success. After every call, read response.status in the JSON body: it is OK on success or an error message like Access Denied: invalid key/password or ERROR: Daily Limit Reached on failure. The classic bug is an agent reporting search results from a call that actually failed, because it only checked the HTTP code. Source: https://www.Mojeek.com/support/api/search/json_response.html