Skip to content
Log In Sign up

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 each identity to stay in the same city and on the same ISP (ASN) for the whole billing period. Social and e-commerce account management, long checkout/login sessions, ad checks from a specific city and ISP.
  • 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.

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 set number of IPs placed on chosen cities and ISPs
  • You can pay per GB of bandwidth

Real ISP IPs in 120 countries, 1,800+ cities and 900+ ISPs (ASNs). You choose the city and ISP for every IP, and each proxy keeps that city and ISP for the whole billing period. The IP address behind a proxy can refresh over time, like a real home connection, which looks more natural to sites than a static IP. Every proxy connects through isp.shifter.io:443 over HTTP(S) or SOCKS5, with one username per IP and one password per plan. Unlimited bandwidth, priced per IP.

Pick this when:

  • You manage 10s or 100s of social or e-commerce accounts that expect a consistent location and network per account
  • Your workflow has long checkout or login sessions that need the same city and ISP throughout
  • You need to check ads or content from a specific city on a specific ISP

Not a fit when a partner has whitelisted one IP address and expects every request from it: ISP Proxies do not guarantee a fixed address and do not support IP whitelisting.

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

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.

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.

Use caseProductWhy
General scraping, monitoring, ad verificationResidential ProxiesFresh IP per request, country/city/ASN targeting
Market research by countryResidential ProxiesRegion and city-level targeting on every request
Manage 50 social or e-commerce accountsISP ProxiesOne proxy per account, same city and ISP for the whole billing period
Long checkout / login sessionsISP ProxiesSame city and ISP for the whole billing period
Scrape JS-heavy sites without running ChromeWeb Scraping APIHeadless Chrome + CAPTCHA solving as one call
SEO rank trackingSERP APIPre-parsed Google / Bing / Yandex / Amazon