From 955c579658ebdf35eceabdf9e2e7e86bef42ca80 Mon Sep 17 00:00:00 2001 From: kenny Date: Sat, 28 Mar 2026 15:09:29 -0600 Subject: [PATCH] =?UTF-8?q?docs:=20clarify=20proxy=20section=20=E2=80=94?= =?UTF-8?q?=20SerpApi=20handles=20proxies=20by=20default?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add a note explaining that SerpApi handles proxies server-side and this config is only for routing through a corporate or network proxy. Fixes #32 --- README.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 0cb56f2..a7ffff0 100644 --- a/README.md +++ b/README.md @@ -118,9 +118,13 @@ await getJson({ engine: "google", api_key: API_KEY_2, q: "coffee" }); // API_KEY ### Using a Proxy -You can use a proxy by passing `requestOptions` with an `HttpsProxyAgent` -instance. This can be done either globally through the config object or -per-request in the parameters. +> **Note:** SerpApi handles proxies on its end — you do **not** need to supply +> your own proxy to avoid blocks or CAPTCHAs. This option is only for users who +> need to route all outbound requests through a corporate or network proxy. + +You can route requests through your own proxy by passing `requestOptions` with +an `HttpsProxyAgent` instance. This can be done either globally through the +config object or per-request in the parameters. First, install the required package: