Pricing and credits
What each call costs, when you are charged, and when you are refunded.
DataFuel bills in credits. A credit is deducted per task when it is queued and refunded when the task fails. Buy credits and see your balance in the DataFuel dashboard, or call GET /users/@me/balance. Every charge and refund is listed by GET /users/@me/transactions; see Build a usage dashboard.
Unlocker (pages)
The cost of a page depends on the proxy plan (proxy_type) and on whether it is fetched with a plain request or rendered in a browser (js_rendering: true).
| Basic | Premium | |
|---|---|---|
Request (js_rendering off) | 1 credit | 10 credits |
Browser (js_rendering on) | 5 credits | 20 credits |
A task, one URL of a job and one page of a crawl all cost the same.
Map and crawl
| Basic | Premium | |
|---|---|---|
| Map (per call, any number of links) | 1 credit | 10 credits |
Crawl, request (per page, charged when queued, capped by max_pages) | 1 credit | 10 credits |
Crawl, browser (js_rendering on) | 5 credits | 20 credits |
LLM scraping and SERP
| Cost | |
|---|---|
| LLM scraping, any engine, per request | 100 credits |
| SERP, per query | 50 credits |
The proxy plan does not change these prices.
When you are charged
- Tasks and jobs: each target is charged when it is queued.
- Crawls: each page is charged when it is queued, so
max_pagesbounds the cost. - Map: one flat charge per call.
When you are refunded
- A task that fails is refunded.
credits_usedis 0 on a failed task. - A blocked page (target answered 403, 429 or 503, or an anti-bot wall) is a failed page on both engines and is refunded.
- A page that completes with a 404 or another non-2xx status is not refunded. The fetch succeeded; the site chose the answer.
- A call rejected with
503 MODULE_UNAVAILABLEorENGINE_UNAVAILABLEcharges nothing.
A crawl’s total_cost is the sum charged at queue time and does not subtract refunds. Sum credits_used over the crawl results for the net figure.
Limits
GET /users/@me returns your concurrency limit and monthly credit limit. A request beyond your concurrency limit answers 429 CONCURRENCY_LIMIT_REACHED and charges nothing. Contact us through the dashboard to raise the limits.