Scrape.do Review 2026

The verdict

Benchmark data and published specifications — here's where Scrape.do lands.

What we think after testing Scrape.do

Editorial review by Helena Björk · last updated Sep 9, 2026

Live performance

Numbers from available benchmark data — our tests, independent lab reports and published specs.

Figures combine our test data, independent lab reports and published specifications — sourcing documented on our methodology page →

Editorial score breakdown

How Scrape.do scores across the five dimensions our reviewers weigh — pricing, performance, pool quality, support and ethics.

Pricing

From $29.00/GB. Detailed plan breakdown not yet published.

Proxy types offered

2 types available. Pricing varies by type and volume.

Features & integrations

What's included out of the box.

Network & infrastructure

How the pool is built, refreshed and addressed.

SDK, API & integrations

Languages, endpoints and tooling shipped out of the box.

Code examples

Drop-in snippets to start using Scrape.do from your stack. Replace USER, PASS and the gateway with what you get from your dashboard.

# pip install requests
import requests

proxy = "http://USER:[email protected]:7777"
resp = requests.get(
    "https://httpbin.org/ip",
    proxies={"http": proxy, "https": proxy},
    timeout=10,
)
print(resp.json())

// npm install undici
import { fetch, ProxyAgent } from "undici";

const dispatcher = new ProxyAgent("http://USER:[email protected]:7777");
const resp = await fetch("https://httpbin.org/ip", { dispatcher });
console.log(await resp.json());

curl -x http://USER:[email protected]:7777 \
  https://httpbin.org/ip \
  --max-time 10

# scrapy-rotating-proxies works with any provider gateway
# settings.py:
DOWNLOADER_MIDDLEWARES = {
    "scrapy.downloadermiddlewares.httpproxy.HttpProxyMiddleware": 400,
}
HTTP_PROXY = "http://USER:[email protected]:7777"
HTTPS_PROXY = "http://USER:[email protected]:7777"

// npm install playwright
import { chromium } from "playwright";

const browser = await chromium.launch({
  proxy: {
    server: "http://gate.scrapedo.com:7777",
    username: "USER",
    password: "PASS",
  },
});
const page = await browser.newPage();
await page.goto("https://httpbin.org/ip");
console.log(await page.locator("body").innerText());
await browser.close();

Compliance & privacy

Auditable certifications, sourcing and data-handling posture.

Support & account

How they pick up the phone — and who answers.

Company & resources

Who builds and operates this product.

Key markets covered

195+ countries served.

Scrape.do vs alternatives

How Scrape.do stacks up against the closest providers in our directory. Tap any column header to read that review.

How to get started with Scrape.do

A 5-minute walkthrough from sign-up to your first successful request. Total setup time: ~10 minutes.

1. 1

   Create your developer workspace

   Create your Scrape.do account at https://scrape.do. You may need to add a payment method.

2. 2

   Copy your token from the dashboard

   From the dashboard, copy your API key into your environment variables (e.g. SCRAPE.DO_KEY) so it never lands in source control.

3. 3

   Fire a hello-world call

   Hit the documented endpoint with a single GET request. Most teams finish their hello-world call in under 5 minutes.

4. 4

   Plug into your observability stack

   Configure retries on the client side and route Scrape.do responses into your APM (Datadog, New Relic, OpenTelemetry) so you catch ban-rate spikes early.

5. 5

   Ramp concurrency once stable

   Start with 1k requests/hour, monitor success rate, then increase concurrency. At ~$29.00/GB, most teams hit volume targets within a sprint.

Stuck? Check Scrape.do's documentation or email us.

User reviews

No reader reviews yet — be the first below.

FAQ

The questions buyers actually ask.