Skip to content

Auto Mode: Automatic Rendering and Proxy Selection for Web Scraping

A page that blocks a plain request may still open with JavaScript rendering, a premium proxy, or a stealth proxy. Testing those combinations by hand is slow and easy to get wrong. Auto Mode performs the search for you: it starts with the cheapest configuration and escalates only until a response succeeds, then stops. This guide covers what the mode controls, what it leaves alone, how credits are charged, and how to cap the cost of a single request.

What Auto Mode decides — and what it does not

Auto Mode varies exactly three dimensions of a request:

  • whether the page is rendered with JavaScript;
  • whether premium proxies are used;
  • whether stealth proxies are used.

It walks through combinations of those three, beginning with the simplest and cheapest, and returns the first configuration that produces a successful response.

Everything else stays as you sent it. Auto Mode will not add a JavaScript scenario, wait for a particular element, raise the rendering delay, pick a country, or set custom headers and cookies on its own. If the target page needs any of those, include them in the request yourself; Auto Mode preserves them while it searches the rendering and proxy space.

Two constraints apply. Auto Mode currently accepts GET requests only. And four parameters must not be combined with it — render_js, premium_proxy, stealth_proxy, and transparent_status_code — because they conflict with the automatic selection and produce a 400 response.

Turning it on

Set mode to auto in the request parameters. The two parameters that matter in a minimal call are:

  • mode=auto — instructs the API to find a working rendering and proxy configuration.
  • ai_query — describes in plain English the data you want extracted (optional, and billed separately).

With those in place you do not have to decide in advance whether the page needs JavaScript, premium proxies, or stealth proxies. Auto Mode tests the available configurations and returns the first successful result.

Other API parameters remain usable alongside Auto Mode, including cookies, custom headers, country selection, waiting instructions, JavaScript scenarios, and AI extraction. The four conflicting parameters listed above are the exception.

What each configuration costs

Auto Mode may try several configurations behind the scenes, but you are billed only for the one that successfully returns the page. It starts at the cheapest tier and moves up only as needed. The table below lists the credit cost of each possible configuration.

A worked credit example

Suppose the 1-credit and 5-credit configurations both fail and the 10-credit configuration succeeds. You are charged 10 credits, not 16 — the failed attempts are not billed. If none of the available configurations works, the request costs 0 credits.

Add-on features are charged on top. In the Hacker News example, ai_query adds 5 credits. If Auto Mode then succeeds with a 5-credit configuration, the complete request costs 10 credits. The Spb-cost header reports the total request cost; Spb-auto-cost reports only the Auto Mode configuration cost.

Capping spend with max_cost

Left unset, Auto Mode may escalate all the way to the 75-credit stealth proxy tier. The optional max_cost parameter sets a ceiling: Auto Mode will only try configurations whose cost does not exceed the value you pass.

max_cost must be an integer of at least 1. You do not have to match an exact tier value. With max_cost=20, for example, Auto Mode can try the 1-, 5-, and 10-credit configurations; if all fail, the request fails without attempting the 25- or 75-credit tiers. With max_cost=25, regular and premium configurations (with or without JavaScript rendering) remain available while the 75-credit stealth tier is excluded.

The cap applies to the Auto Mode configuration only. Other paid features are added separately: a request that uses a 25-credit Auto Mode configuration plus ai_query at 5 credits costs 30 credits in total.

Quick decision checklist

  • Target page is a simple GET with no known anti-bot protection? Start without max_cost and let Auto Mode find the cheapest working tier.
  • You want predictable per-request spend? Set max_cost to the highest tier you are willing to pay for.
  • You are using ai_query or other paid add-ons? Remember the cap covers only the Auto Mode configuration; add-on credits are billed separately.
  • You need POST? Auto Mode does not support it yet.
  • You already know the page needs render_js, premium_proxy, stealth_proxy, or transparent_status_code? Do not combine those with Auto Mode — you will get a 400 response.
  • You need to audit what was spent? Read Spb-auto-cost for the configuration cost and Spb-cost for the total.
Auto Mode configuration credit costs
ConfigurationCost
Rotating proxy without JavaScript rendering1 credit
Rotating proxy with JavaScript rendering5 credits
Premium proxy without JavaScript rendering10 credits
Premium proxy with JavaScript rendering25 credits
Stealth proxy with JavaScript rendering75 credits

Credit costs reflect the feature description and should be checked against current documentation before relying on them for billing decisions.

Frequently asked questions

What does Auto Mode choose automatically?

It decides three things per request: whether JavaScript rendering is applied, whether premium proxies are used, and whether stealth proxies are used. It works upward from the least expensive combination and halts at the first one that returns a successful response.

Does Auto Mode work with POST requests?

No. Auto Mode currently supports GET requests only.

Do I pay for every configuration Auto Mode tries?

No. Billing applies only to the configuration that actually returns the page; the failed attempts along the way are not charged. When every available configuration fails, the Auto Mode cost is 0 credits.

Can I limit how much Auto Mode spends?

Yes. The max_cost parameter stops Auto Mode from attempting any configuration priced above the credit value you set. That ceiling covers the Auto Mode configuration only — add-ons such as AI extraction are billed on top.

Can I use other API parameters with Auto Mode?

Yes, in most cases. You can still use cookies, custom headers, country selection, waiting instructions, JavaScript scenarios, and AI extraction. However, do not combine Auto Mode with render_js, premium_proxy, stealth_proxy, or transparent_status_code.