Send a URL.
Get the real page back.

One call returns the fully rendered page from real Chrome.
No browser to run, no pipeline to babysit.

Try API for free Read the docs

Trusted by Devs at

How it works

One call in. The
real page out.

Send a URL. Driver loads it in real Chrome and sends back the HTML.

Send a URL
One POST with the page you want, from any language that speaks HTTP.
We render it
Real Chrome on real hardware loads the page and runs its scripts.
Get the HTML back
The rendered page comes back in the response body.

Send a URL
One POST with the page you want, from any language that speaks HTTP.
We render it
Real Chrome on real hardware loads the page and runs its scripts.
Get the HTML back
The rendered page comes back in the response body.

Why render

A fetch getsthe shell.
We get the page.

Most pages are built by JavaScript. A plain request never runs it. Driver does, in real Chrome.

Plain HTTP request

Empty shell

GET

store.example.com/p/summit-bottle

200 · 2.1 KB

1<!doctype html>

2<html lang="en">

3 <head>

4 <script src="/app.3f9a.js"></script>

5 </head>

6 <body>

7 <div id="root"></div>

8 </body>

9</html>

Nothing to extract. The page is built later by JavaScript.

JavaScript: Not run
Product data: Missing
Bot checks: Often blocked

Web Data API

Full page

POST

store.example.com/p/summit-bottle

200 · 184 KB · 1.8s

1<main class="product">

2 <h1>Summit Bottle</h1>

3 <span class="price">$34.00</span>

4 <div class="rating" data-count="412">

5 <ul class="options">

6 <li>500 ml</li><li>750 ml</li>

7 </ul>

8 <button>Add to cart</button>

9 <section class="reviews"> …

+ 2,140 more lines

JavaScript: Executed in real Chrome
Product data: Title, price, reviews
Bot checks: Real device, passes

Features

Clean pages, ready
for your agents.

Rendered HTML in one response. We handle the waiting, the rendering and the scale.

Rendered HTML back

The full page after its JavaScript runs, in the response body.

Waits until it settles

We return the page after its scripts and requests finish.

curl api.driver.dev/v2/extract \  -H "Authorization: $KEY" \  -d url=https://example.com

One HTTP call

cURL, Python, Node or anything that can send a request.

Pay per result

No servers or browser hours to pay for. You pay for pages returned.

Scale on demand

From 5 concurrent requests to thousands, without running a fleet.

Pricing

Start free.Pay
$3 per 1k results.

Your plan price comes back as credits. The API uses them at $3 per 1,000 results.

Credits work for
Browsers and the API

Mix browser traffic and API results however your month goes.

Web Data API$3 / 1k results
Browsers$5 / GB

START
$0/mo
$5 in credits to start
Start free
GROW
$49/mo
$49 in credits monthly
Start growing
SCALE
Most value
$129/mo
$129 in credits monthly
Start scaling
CUSTOM
Custom
Volume pricing
Talk to us

Compare plans	START$0/mo	GROW$49/mo	SCALE$129/mo	CUSTOMCustom
Web Data APIRendered pages from one API call
Price	$3 / 1k results	$3 / 1k results	$3 / 1k results	Custom
Results included	1,667	16,333	43,000	Custom
Concurrent requests	5	30	100	Custom
Rendered HTML
BrowsersReal Chrome on physical machines
Price	$5 / GB	$5 / GB	$5 / GB	Custom
Traffic included	1 GB	10 GB	26 GB	Custom
Concurrent browsers	5	30	100	Custom
Live view, recordings and profiles
Hardware	Real devices	Real devices	Real devices	Real devices
Platform
Support	Community	Email	Priority	Dedicated
Audit logs
MSA, DPA and SLA	—	—	—

Send a URL.Get the real page back.

One call in. The real page out.

Send a URL

We render it

Get the HTML back

Send a URL

We render it

Get the HTML back

A fetch getsthe shell.We get the page.

Plain HTTP request

Web Data API

Clean pages, ready for your agents.

Rendered HTML back

Waits until it settles

One HTTP call

Pay per result

Scale on demand

Start free.Pay$3 per 1k results.

START

GROW

SCALE

CUSTOM

Send a URL.
Get the real page back.

One call in. The
real page out.

A fetch getsthe shell.
We get the page.

Clean pages, ready
for your agents.

Start free.Pay
$3 per 1k results.