Cloudflare and DataDome share the same API integration logic and request code. Support for a specific target still depends on the site and challenge type. Test compatibility first; a shared plan does not guarantee access to every target.
Cloudflare and DataDome share one API credit balance, consumption rules and pricing. Choose a plan based on your usage; proxy traffic is billed separately. View pricing
Billing Overview
When using the Scrapingbypass SDK, credit consumption is calculated based on the total volume of network activity generated to complete your request. SDK requests follow the same successful-request and successful-challenge credit rules as direct API calls.
Consumption Breakdown
- Request Base Fee: 1 credit per successful request.
- Each successful HTTP request consumes 1 credit.
- Redirects: Requests in a redirect chain follow the same rules: 1 credit per successful request, plus 2 credits for each successful V2 challenge.
- Challenge Resolution Fee: 2 credits per challenge.
- When the SDK detects a Cloudflare JS Challenge, Turnstile, or WAF barrier, it automatically triggers the solving engine.
- Each successful solve incurs a flat fee of 2 credits, independent of the base request fee.
Calculation Logic Example
| Action Sequence | Credit Cost | Total |
|---|---|---|
| Initial request triggers a JS Challenge | 1 (Request) + 2 (Challenge) | 3 |
| Target site redirects to a login page | 1 (Redirect) | 1 |
| Total Session Cost | 4 Credits |
Key Considerations
- Successful Execution Only: An unsuccessful request does not consume the base request credit. However, the 2 challenge credits are deducted as soon as verification succeeds and are not refunded if the subsequent response fails.
- Granular Billing: SDK requests use the same credit rules as direct API requests.
- Session Reuse: To minimize costs, maintain persistent sessions within the SDK to reduce the frequency of re-triggering challenges.
Technical Note on Redirects
If your target URL involves multiple redirects (e.g., a tracking link leading to a landing page), ensure your credit balance is sufficient to cover the total number of hops in the chain.