Skip to main content

Requests

Every endpoint lives at:
  • GET endpoints take parameters in the query string. List parameters repeat, as in ?ids[]=1&ids[]=2.
  • POST endpoints take a JSON body. Send Content-Type: application/json.
  • File uploads (a param of type file, such as image on Google Lens upload) are sent as multipart/form-data, for example curl -F image=@photo.jpg. Files can be up to 10 MB and are deleted after the search.
  • Unknown parameters are ignored. Invalid ones are rejected with 422 invalid_parameters before anything is charged.
  • Some sources are slower than others. Allow up to 60 seconds per call; after that the call fails with 504 timeout, free.
Each endpoint’s page in the API reference lists its parameters, which are required, and their limits.

Responses

Successful calls return the data as JSON with no wrapper. Metadata travels in headers, and the credit and rate-limit headers are on errors too. When the data is a JSON object, the same call facts are in its meta object too, next to any metadata the source returns:
credits_charged matches X-Credits-Used and credits_remaining matches X-Credits-Remaining. A JSON array, CSV or file has no meta; read the headers. Errors have their own shape. See Errors.
Last modified on November 18, 2026