Credits and Limits
Calculate job cost and understand account throughput
Credit cost
Standard Jobs use a fixed credit price calculated before execution. The
selected proxy network, JavaScript rendering, and screenshots determine that
price. Auto Jobs use a required max_credits ceiling.
Components
| Component | Cost |
|---|---|
| Base job | 5 credits |
| Residential proxy | +5 credits |
| JavaScript rendering | +5 credits |
| Any screenshot option | +5 credits |
Examples
| Request | Credits |
|---|---|
| Datacenter without JavaScript | 5 |
| Datacenter with JavaScript | 10 |
| Residential without JavaScript | 10 |
| Residential with JavaScript | 15 |
| Residential with JavaScript and screenshot | 20 |
Screenshots require a browser-compatible result, so their total includes the
browser component even when an Auto request omits render_js.
When credits are reserved
For a Standard Job, the fixed price is reserved before the scrape starts. For
an Auto Job, ScrapeDrive reserves the highest compatible configuration price it
can reach without exceeding max_credits.
The Standard price is based on the original request and does not change if ScrapeDrive needs another compatible attempt to deliver it.
Auto follows the compatible acquisition order selected for the target and
advances only after failure. The successful result configuration is charged
once; internal failed attempts are not charged again. The final charge never
exceeds max_credits.
Requests rejected for validation, rate limit, backlog limit, or insufficient
credits are not charged. A job that ends without a usable target response
settles at zero credits; the Sync response carries X-Sdrive-Credits: 0 and
the polled Async job shows credits: 0.
A delivered page is charged even when the target answered 404 or 410, and
an accepted Standard Job can consume its fixed price even when the target page
does not produce the result you expected. In Auto mode, the Playground shows a
maximum rather than a quoted final charge; the actual successful configuration
can cost less.
Account limits
Three per-account limits control throughput:
| Limit | Meaning |
|---|---|
| Active jobs | Maximum jobs running at the same time. Async jobs may wait; excess Sync requests return 429. |
| Requests per minute | Maximum submissions per minute; requests over it return 429. |
| Async backlog | Maximum queued Async jobs waiting for a running slot; requests over it return 429. |
When a request is rejected because a public limit was reached, no credits are charged.
Current plan defaults
| Plan | Credits | Active jobs | Async backlog |
|---|---|---|---|
| Trial | 500 total | 1 | 10 |
| Developer | 50,000/month | 5 | 250 |
| Startup | 150,000/month | 25 | 1,000 |
| Business | 350,000/month | 100 | 5,000 |
These are the default limits for the current public plans. Your account can have an explicit limit override, so the values shown in your dashboard are the ones that apply to your API key.
A per-account submission throttle also protects the API from accidental floods.
It is an operational safeguard rather than a marketed plan allowance. Requests
over that threshold return 429 without consuming credits.
See Pricing for current subscription prices and included plan features.