Overview

The Local Proxy Tool is a lightweight bridge designed to convert the Scrapingbypass API logic into a standard proxy interface (HTTP/SOCKS5). This allows you to integrate our anti-bot bypass capabilities into software or frameworks that only support standard proxy configurations.

Note: This tool does not allow the API to access local-only networks. Any proxy_host provided to the tool must be reachable by Scrapingbypass API remote servers.

Getting Started

1. Download: Obtain the latest release for your OS from the official repository: https://github.com/cloudbypass/example/releases.
2. Launch: Execute the binary via your terminal.
3. Connectivity: Once started, the console will output the local proxy address (e.g., 127.0.0.1:8080). You can now route your traffic through this endpoint.

Configuration Methods

The tool requires the same parameters as the API (e.g., API Key, Proxy settings, Fingerprint headers). You can provide these using two methods:

1. Command Line Interface (CLI)

Pre-configure the settings at startup for global use across all requests.

./scrapingbypass-proxy --api-key YOUR_TOKEN --proxy-host YOUR_UPSTREAM_IP

2. Dynamic Headers

If you do not pre-set parameters via CLI, you must include the required Scrapingbypass API parameters in the headers of every request sent to the local proxy, exactly as you would when calling the API directly.

Operational Logic

The local proxy acts as a relay:

1. It receives a standard HTTP request from your application.
2. It wraps the request with the specified Scrapingbypass API logic (JS challenge solving, TLS impersonation).
3. It forwards the request to our backend servers.
4. It returns the "passed" response back to your application.

Important Requirement

Ensure your firewall allows outbound connections to the Scrapingbypass API gateway so the local tool can successfully synchronize session states.