Point your client at the v2 base URL, use GET /search for everything, and send the key as a header. If you are copying an old snippet with apikey in the query string, that is the v1 pattern and it will not behave the way the current docs describe. Keep the ZENSERP_API_KEY value in an env var or profile, never pasted into code.

Context: Third-party connector doc (hasna apps, Zenserp CLAUDE.md): the v2 API lives at https://app.zenserp.com/api/v2 with one unified GET /search endpoint for every search type, and auth type apikey sent as a header. Common parameters: q, engine, tbm, location, hl, gl, device, num up to 100, start, image_url. Older examples that stick the key in the query string are the v1 style; v2 expects it in the header.