Shifter Review

Shifter dates its business to 2012 and previously operated as Microleaves. Its present range combines residential pool access, dedicated ISP addresses, page fetching and structured search data. The proxy services remain usable independently of the managed APIs; adopting Shifter does not require handing over the entire collection process.

The move away from its older port-based Residential offer is an important change. That unmetered configuration remains available to existing customers, but new accounts receive the traffic-based gateway service. Descriptions of Shifter as an unlimited-bandwidth residential provider therefore belong to a different product generation. Unlimited traffic remains part of the current ISP subscription.

Free-trial availability is inconsistent: Residential pages invite trials while the product FAQ says no free trial is offered. The API FAQs describe a money-back guarantee after purchase. A free evaluation allowance should therefore not be assumed to accompany a standard subscription; the specific paid-purchase guarantees are set out below.

Residential activation supplies gateway credentials and an endpoint builder. Geographic and session choices are encoded in the connection settings, so the application can request different exits without importing replacement address lists.

ISP provisioning produces actual assigned addresses after the country allocation step. These are available in the panel, as a CSV download and through the management API. That delivery format suits software that stores named proxy entries or associates particular addresses with ongoing tasks. It also keeps the assigned inventory accessible outside Shifter's own interface.

Residential monitoring includes remaining allowance, traffic history at minute-level resolution and top destinations. Those views help explain an unexpected increase in consumption: the useful question is which destination or workload generated the bytes, especially when retries can be charged. The management API also exposes geographic options, allowing software to obtain available country, region, city and ASN selectors.

For ISP subscriptions, the API retrieves the assigned list and manages source-IP authorization by membership. These are useful inventory and access controls. Proxy connection credentials and management API keys are separate, so application proxy configuration does not require giving it the key used to administer the account.

Team workspaces add a more substantial administrative feature than shared access to a single login. Workspaces hold separate plans, with Viewer, Billing and Admin roles. A colleague can inspect traffic and invoices without receiving purchasing or cancellation authority; billing access can be granted separately from team and settings management. This is valuable when the people operating collection jobs are not the people responsible for funding them.

The documentation reaches beyond connection strings into session behavior, targeting fallback, billing and troubleshooting. Examples cover tools such as Scrapy, Playwright and Puppeteer, making both HTTP collection and browser-based work recognizable in the guides.

The troubleshooting material also addresses browser, TLS, header and session problems. That is a useful emphasis for modern protected sites, where changing an exit address may leave the actual cause of a challenge untouched. Documentation is less dependable on a few configuration boundaries, including the maximum Residential session duration and the scope of ISP credentials. Those details warrant more care than the basic quickstart examples suggest.

Shifter lists bank cards, USDT and USDC, PayPal in eligible regions, and wire transfers for Enterprise customers. Published plans are denominated in USD. Subscriptions renew monthly; invoices are available in the panel and by email. Cancellation leaves access running to the end of the paid cycle without a prorated refund.

The more consequential billing rule concerns Residential overage. Once the included allowance is exhausted, Extra Traffic automatically draws from the account wallet at the plan's per-GB rate. This continuation cannot be disabled while wallet funds are available. Exhausting a subscription allowance therefore does not necessarily stop a running job or its charges.

Optional card-based wallet top-up can extend that continuation further. It has a trigger balance, refill amount and calendar-month cap, but the cap limits automatic refills only. Existing wallet funds, manual deposits and subscription charges sit outside it. This is a funding control, not a hard limit on total account spending. Shifter's automation favors uninterrupted access; a workload with a strict spending ceiling needs an additional stop condition in the application.

Residential's first-purchase refund requires a request within 72 hours and less than 50% of the allowance consumed. Both conditions apply, so a traffic-heavy evaluation can lose eligibility well before the time window closes. Requests go through panel support with the invoice ID.

ISP has a 3-day first-purchase money-back guarantee. The Residential traffic threshold does not belong to that unmetered service. The managed API FAQs also describe 3-day guarantees, but these should not be treated as identical consumption allowances across every product.

Residential blocks banking, government and adult destinations, as well as SMTP. Some destination restrictions can be reviewed; SMTP is excluded from exceptions. Separately, the Terms prohibit using the scraping services for X/Twitter. These restrictions can rule out a project regardless of whether the selected network or API could technically reach its target.

The contract selects California law and arbitration in San Francisco.

Panel chat and email are the standard channels, with a named manager and Slack offered at Enterprise level. Support is tiered: response targets, coverage conditions and contractual remedies vary with the plan. The broad 24/7 chat message should not be read as a uniform response commitment. Formal service credits belong to Enterprise contractual terms rather than a guarantee attached to every self-service subscription.

Web Scraping API takes a URL and returns page HTML or extracted JSON. Shifter handles fetching, browser rendering, proxy selection, retries and documented CAPTCHA handling. Its session controls can retain cookies, browser state and the upstream IP, which goes beyond the network-level stickiness of a Residential gateway session.

The credit model is a meaningful part of this offer. A successful 2xx response with a nonempty body counts as 1 credit; network failures, timeouts and target 4xx/5xx responses are uncharged. Rendering, extraction, screenshots and internal retries do not add separate credits. This shifts the cost of those failed attempts away from the byte-metering model used by Residential. The billing definition still concerns the returned response, rather than guaranteeing that every requested field is present and correct.

Plan selection affects the fetching environment as well as volume. Starter uses datacenter routing within its supported US/EU scope; higher tiers add broader geography and residential or mobile routing options. An external forward proxy can also be supplied. These choices are useful when the desired output is a rendered page, but the operator still wants control over the network used to fetch it.

SERP API returns parsed JSON for supported engines, including Google, Bing, Yandex and Amazon, with location, language and device controls. Shifter performs retrieval, parsing and retries; only valid parsed responses consume the call allowance. It is the more specialized option for structured search and marketplace results, with monthly quotas and tiered concurrency.

Amazon endpoints share the SERP API key and plan quota. They extend the supported data sources without requiring a separate Amazon subscription. Across both APIs, the useful distinction is the managed work and charging rules; advertised rendering and CAPTCHA handling do not establish a success rate against any particular target.