Let Auto choose the route under a credit ceiling
Automatic routing, called Auto mode in the API, lets ScrapeDrive decide how to fetch a page. You send auto=true with a max_credits ceiling. ScrapeDrive works through compatible HTTP and browser routes, proxy pools and locations, and charges the configuration that succeeds once.
500 credits after you confirm your email. No card.

What this request asks for
- auto=true
- Hands the route to ScrapeDrive.
- max_credits=20
- The most this request can cost. Auto never charges more.
What it does for a request
- Works through routes in order
- Auto starts with a compatible route for the target and moves to the next one only after an attempt fails.
- Keeps your output requirements
- The result format, screenshots and browser waits stay as you sent them. A screenshot or a wait tells Auto that the result needs a browser.
- Caps the charge
- ScrapeDrive reserves the highest price it can reach under max_credits. You pay once for the configuration that succeeded, never above the ceiling. Failed internal attempts are not charged again.
- Settles failures at zero
- A request that ends without a usable page costs 0 credits.
When to use it
Use it when
- You do not know yet which route a site needs.
- You fetch many different sites and do not want to tune a configuration for each one.
- You would rather not resubmit a request by hand after each failure, and you need a known maximum charge.
Leave it out when
- You already know a configuration that works. A Standard request has one fixed price.
- You need a named country, your own proxy or a sticky session. Auto rejects those fields.
How to set it
auto
true or false
Turns on Auto mode. The default is false.
max_credits
1 or more
Required with auto=true. The final charge never exceeds it.
render_js, proxy_pool, proxy_country, custom_proxy, session_number
not accepted
Sending any of them with auto=true is rejected before the request runs. Rejected requests are not charged.
Limits to plan for
- A low ceiling can rule out the route a page needs. A residential browser request costs 15 credits, so a ceiling of 10 never reaches it.
- Some pages still fail under Auto. When the request ends without a usable page, you pay 0 credits.
- On a sync response,
X-Sdrive-Creditsreports the settled charge. It is not a count of attempts.
Other features
Start with a plain request. Add browser, routing or waiting settings only when the page needs them.
JavaScript rendering
Load the page in a real browser so content that scripts add is in the result.
See the feature, JavaScript renderingProxy routing
Send a Standard request through datacenter or residential proxies, or through your own proxy.
See the feature, Proxy routingGeo targeting
Route a residential Standard request through the country you name with proxy_country.
See the feature, Geo targetingWebpage screenshots
Add an image of the viewport, the full page or one element to a request.
See the feature, Webpage screenshotsOutput formats
Choose HTML, visible text or Markdown with result_type, at the same price.
See the feature, Output formatsAsync requests
Get a job id at once, then poll for the result or receive it at an HTTPS webhook.
See the feature, Async requestsBrowser waits
Hold a browser request for a load event, a CSS selector or a fixed delay.
See the feature, Browser waitsHeaders and sessions
Pass your own headers to the site and keep one proxy session across related requests.
See the feature, Headers and sessionsCost controls
Work out the price from the parameters, cap Auto with max_credits and read the settled charge.
See the feature, Cost controls
Try automatic routing on your page
Paste a page URL into the Playground and see exactly what ScrapeDrive returns.
500 credits after you confirm your email. No card.
