Choosing a product

Pick the product that matches what you’re building:

• Residential Proxies — you need traffic to look like real residential users, from many different IPs. Scraping, monitoring, ad verification, market research, SERP collection, anti-bot bypass.
• ISP Proxies — you need the same IP assigned to you for days or weeks. Social and e-commerce account management, long checkout/login sessions, whitelisted-IP integrations.
• Web Scraping API — you don’t want to run headless Chrome yourself. JavaScript rendering, CAPTCHA solving, and extraction in one REST call.
• SERP API — you need parsed search-engine results as JSON. Google, Bing, Yandex, Amazon.

The rest of this page goes deeper on what each one is best at, so you can self-select with confidence.

Residential Proxies

Fresh residential IP on every request through one gateway (p.shifter.io:443). 195+ countries with region, city, and ASN targeting. Sticky sessions when you need the same IP for a few seconds to a few minutes via sid + ttl.

Pick this when:

• You’re scraping, monitoring prices, verifying ads, or collecting SERPs at scale
• You need traffic to blend in with real residential users to bypass anti-bot
• You need geo coverage broader than a fixed pool of pinned IPs
• You can pay per GB of bandwidth

ISP Proxies

Pinned IPs from real ISPs, assigned to your account 24/7. Each IP shares the same port (1337) and credentials. Unlimited bandwidth, concurrency limited per IP.

Pick this when:

• You manage 10s or 100s of social or e-commerce accounts that expect a stable IP per account
• Your workflow has long checkout or login sessions that break on IP change
• A partner has whitelisted your IP and expects all traffic from that address

If you only need a few minutes of IP stickiness, Residential Proxies with sid + ttl is the right call instead.

Web Scraping API

One REST endpoint that returns fully-rendered HTML (or structured JSON via extraction rules). Headless Chrome, proxies, CAPTCHA solving, retries, and JS rendering all handled server-side.

Pick this when:

• Your target is JavaScript-heavy and you don’t want to run a browser farm
• You’re facing aggressive bot protection and don’t want to manage stealth fingerprints
• You want HTML out of one endpoint without standing up infrastructure

If your target is plain HTML, or your scraper already runs Puppeteer/Playwright, raw Residential Proxies are cheaper and more flexible.

SERP API

JSON in, JSON out for Google, Bing, Yandex, and Amazon. Pre-parsed results — no proxies, no HTML parsing, no rotation logic on your side.

Pick this when:

• You’re tracking SEO rankings or keyword positions at scale
• You’re building a search-result feed (news, products, places)
• You want SERP data as a structured payload instead of HTML

For anything outside those search engines, use the Web Scraping API or raw proxies.

Side-by-side

Use case	Product	Why
General scraping, monitoring, ad verification	Residential Proxies	Fresh IP per request, country/city/ASN targeting
Market research by country	Residential Proxies	Region and city-level targeting on every request
Manage 50 social or e-commerce accounts	ISP Proxies	One pinned IP per account, never rotates
Long checkout / login sessions	ISP Proxies	Stable IP for the entire session
Scrape JS-heavy sites without running Chrome	Web Scraping API	Headless Chrome + CAPTCHA solving as one call
SEO rank tracking	SERP API	Pre-parsed Google / Bing / Yandex / Amazon

Products

Residential Proxies Fresh residential IP per request. 195+ countries.

ISP Proxies Pinned ISP IPs. Unlimited bandwidth.

Web Scraping API Render + extract via one endpoint.

SERP API Google, Bing, Yandex, Amazon.