Skip to main content
Look up which driver Nimble recommends for a given domain or agent — including detected antibot systems and whether JavaScript rendering is required. Use the result to set the driver parameter explicitly on Extract or Agent requests.
Nimble selects the optimal driver automatically on every request. Use Domain Knowledge when you want to understand the driver tier before running at scale, or to pin a specific tier for cost predictability.

Quick Start

Example Request

Example Response

Agent lookup response:

How it works

1

Submit a URL or agent name

Pass either a url (domain) or agent name as a query parameter. Exactly one must be provided.
2

Nimble resolves the driver

Nimble queries its domain knowledge database to identify the antibot systems protecting the target and returns the recommended driver.
3

Pin the driver on your Extract or Agent request

Use the returned driver value in the driver parameter of an Extract or Agent request to skip auto-detection and use the resolved tier directly.

Parameters

string
Target domain to resolve the driver for.Example: amazon.comMutually exclusive with agent — provide exactly one.
string
Agent name to resolve the driver for.Example: amazon_pdpMutually exclusive with url — provide exactly one.

Response fields

Using the result with Extract

Pass the resolved driver value directly to an Extract request to skip auto-detection.
If the resolved driver is a wsa-* value, use the equivalent vx driver instead when calling Extract. See the conversion table below.
cURL

Extract

Use the resolved driver in Extract requests via the driver parameter

Templates

Resolve the driver for any template

Pricing

Understand how driver tiers affect request cost