Proxy and Scrape.do Mode

Every request in Scrapeman can route through a proxy. You can use any standard HTTP/HTTPS proxy, or flip into Scrape.do native mode to access residential rotation, JS rendering, geo targeting, and automatic ban retry — all from the Settings tab.

Standard Proxy

Configure per-request in the Settings tab of the request builder.

• Protocol — HTTP or HTTPS
• Host and Port
• Auth — username and password for proxy basic authentication

The proxy is applied via undici's ProxyAgent. All fields support {{var}} variable interpolation, so you can store proxy credentials in environment variables.

Scrape.do Native Mode

Flip the Scrape.do toggle in the Settings tab to route the request through Scrape.do's infrastructure instead of sending it directly.

When enabled, the main process rewrites the target URL to api.scrape.do and injects the configured parameters. Your Scrape.do token is stored as a secret environment variable and never appears in history on disk.

Residential Rotation

Automatically rotates the outgoing IP address from Scrape.do's residential pool on every request. No manual proxy list management required.

JS Rendering

Spins up a headless browser on Scrape.do's infrastructure to fully render the target page before returning the response. Useful for SPAs, lazy-loaded content, and anti-bot pages that check for browser fingerprints.

Geo Targeting

Route the request through a specific country by selecting a country code. The outgoing IP will appear to originate from that country.

Ban Retry

When enabled, Scrape.do automatically retries the request if it detects a block or detection response from the target server. Retries are handled server-side and transparent to Scrapeman — you receive the final successful response.