max driver sends one request to every Nimble driver at the same time and returns the first successful response. Use it when speed and success rate matter more than cost.
Common uses:
- Latency-sensitive agents: get the page back as fast as any driver can fetch it.
- Hard targets: let stealth and rendering drivers race instead of escalating one at a time.
- Unknown sites: skip driver tuning when the site mix changes from request to request.
max is a premium driver billed at $2.50 per 1K URLs. Only the successful response is charged. Failed requests are free. See Pricing.Quick Start
Example Request
Example Response
How it works
1
You send one request with driver: max
Pass
driver: "max" with the URL. No other driver settings are needed.2
Nimble starts every driver at the same time
The request is sent to all drivers in parallel, from plain HTTP (
vx6) to stealth headful browsers (vx10-pro). Each driver uses its own rendering settings.3
The first successful response wins
As soon as one driver returns a valid page, that response is sent back to you. Slower attempts keep running in the background. They do not delay the response and are not charged.
4
Failures are reported only if every driver fails
If no driver succeeds, the request fails once with the final error. Failed requests are not charged.
Parameters
driver
driver
string
Set to
"max" to run every driver in parallel and return the first successful response.Works with: formats, country, state, city, locale, parse, headers, cookies, and request_timeout.Cannot be combined with: render: "auto" or auto_driver_configuration. Sending either together with driver: "max" returns a 400 error.Rendering: leave render unset. Each driver in the race applies its own rendering configuration, so both non-rendered and rendered results compete.request_timeout
request_timeout
number
Maximum time in milliseconds to wait for the whole request. The timeout caps the race as a whole, not each driver. If no driver succeeds before the deadline, the request fails.
Max vs. auto
Both options let Nimble pick the driver for you. They optimize for different things.
Pick
render: "auto" for high-volume jobs where cost matters. Pick driver: "max" for real-time workloads, agent tool calls, and sites that block cheaper drivers.
Usage
Fetch a protected page as fast as possible
Let stealth and rendering drivers race against plain HTTP. The response comes from whichever gets through first.Cap the wait time
Combinemax with request_timeout to fail fast when no driver gets through.
Related
JS Rendering
Automatic driver selection with
render: "auto"Stealth Mode
Pick a single stealth driver by hand
Advanced Options
Timeouts, sessions, and device emulation
Pricing
Extract pricing, including the max driver