ScrapingBee review

ScrapingBee is a hosted web scraping API, not a scraping library or a self-hosted server. Your application sends a request for public website content; ScrapingBee handles proxy rotation, browser rendering, and anti-bot defenses, then returns page content or extracted data. That puts it between your crawler or data pipeline and the target website.

The HTML API returns raw page content for custom parsing. Other options include browser-rendered pages, Markdown, JSON from extraction rules or natural-language queries, and dedicated APIs for sources such as Amazon, Walmart, search results, YouTube, ChatGPT, and Gemini. You can use the results in analytics, e-commerce monitoring, or AI and retrieval workflows.

This setup removes the need to operate a proxy fleet and browser infrastructure, but it does not remove target-specific failure handling or downstream data validation. You still need to decide what counts as a valid result, handle retries, and monitor whether extracted fields are populated.

ScrapingBee’s integration surface centers on its web scraping API: request page content or use its extraction and dedicated scraper APIs. The homepage also names a CLI for running scraping workflows and connecting with AI coding tools, plus an MCP Server for giving an AI agent access to scraping. It describes HTML API, Markdown, AI extraction, CSS/XPath extraction, JavaScript scenarios, and screenshots.

For workflow automation, the vendor lists Make, n8n, and Zapier integrations. The CLI is presented for use with ChatGPT, Claude, Codex, Cursor, Claude Code, and Gemini. The homepage does not name programming languages or SDKs; confirm language-specific SDK support and current setup instructions in the vendor’s docs before choosing an integration path.

For browser-dependent pages, you can wait for selectors or browser events, run custom interactions, set viewport and headers, and capture screenshots. That gives teams options beyond fetching raw HTML, though you still need application-side checks for the fields your pipeline depends on.

ScrapingBee offers 1,000 free API credits with no credit card required. Paid plans start at $19 per month for Hobby, which includes 75,000 credits and 25 concurrent requests. Freelance is $49 for 250,000 credits and 50 concurrent requests; Startup is $99 for 1,000,000 credits and 100 concurrent requests. Business costs $249 for 3,000,000 credits, while Business + is $599 for 8,000,000 credits.

The listed enterprise plans range from Enterprise 14 at $999 per month for 14,000,000 credits to Enterprise 120 at $5,799 for 120,000,000 credits. Higher plans include more concurrent requests, up to 900 on Enterprise 120. JavaScript rendering costs five credits per successful request. Premium proxies cost 10 or 25 credits per successful request, depending on whether JavaScript rendering is used. Credits expire after one month and do not roll over. Prices exclude VAT; annual rates are not listed. Check the pricing page for the current plan details and ask the vendor about how additional usage is handled.

ScrapingBee is a hosted service accessed through its API and integrations. The vendor doesn’t publish an open-source licence, self-hosting option, or data-export path, so teams should treat it as a hosted dependency and confirm export options with the vendor before committing. The homepage says ScrapingBee uses zero data retention; confirm what that covers for requests, logs, and support workflows if your data handling requirements are strict.

Migration is possible at the application boundary, but not necessarily a drop-in switch. Your code may depend on ScrapingBee-specific request parameters, extraction behavior, dedicated APIs, and credit accounting. Keep your own normalized output schema and parser or validation layer, and store results in your own system. That limits how much downstream code must change if you replace the provider.

Plan around both concurrency and credit consumption. The paid plans list concurrency caps from 25 to 900 requests, while JavaScript rendering and premium proxies increase the credits charged per successful request. Credits expire monthly, so demand spikes or a change in target mix can affect both spend and unused balance. Track successful parsed records and cost per result, not just HTTP status codes.

ScrapingBee says it uses zero data retention, but teams with security or compliance requirements should confirm the scope, traffic-log handling, and applicable terms with the vendor. Set timeouts, retry limits, and fallbacks in your own pipeline, and test representative URLs before expanding volume.

Reddit reports are mixed. One user said they were seeing failures on ScrapingBee targets where another provider worked; another commenter reported a 20-second response in a comparison. These are individual accounts, not controlled tests, but they reinforce the need to measure reliability against your own domains.