Scrapingbypass API and Scrapingbypass Proxy are complementary services designed to handle different layers of web automation and anti-bot mitigation.

Scrapingbypass API

The Scrapingbypass API focuses on bypassing advanced website security, such as Cloudflare 5-second challenges, Turnstile, and WAF protections.

• Billing: Uses a credit-based system (credits are deducted per successful request).
• Core Function: Solves JS challenges and maintains session states.
• Proxy Requirement: * V2 API: Requires a proxy configuration to function.
  • V1 API: Can be enhanced with external proxies.
• Dashboard: Manage API Account

Scrapingbypass Proxy

Scrapingbypass Proxy provides global dynamic IP addresses to mask your scraper's identity and avoid IP-based blocking.

• Billing: Based on bandwidth (traffic) consumption.
• Validity: Traffic packages have no expiration date and remain valid until fully consumed.
• IP Types: Offers both Dynamic Residential IPs and Dynamic Datacenter IPs.
• Dashboard: Manage Proxy Account

Integration and Compatibility

1. Direct Integration: Scrapingbypass Proxy is natively compatible with Scrapingbypass API. It is the recommended upstream for the V2 API to ensure optimal TLS/JA3 fingerprint consistency.
2. Third-Party Flexibility: * API Side: Scrapingbypass API supports integration with third-party proxy providers.
   • Proxy Side: Scrapingbypass Proxies can be used independently of the API. They are compatible with third-party scrapers, crawler scripts, anti-detect browsers, and bulk account registration tools.

Comparison Summary