Head to head · Scraping · October 2026 research run
Scrapeless vs ScrapingBee
ScrapingBee scores 62 (B) on agent readiness against Scrapeless's 58.1 (C), and leads in 4 of 7 scored categories. Scrapeless leads on schema & documentation and maintenance & community. Both do scraping.
Best web scraping and crawling APIs for AI agents · All 567 scrapers comparisons
Which one, for what
Best for An agent that needs one key for unlocking, a remote browser and AI answer-engine scraping.
Ahead on
- Schema & documentation, 66 against 60
- Maintenance & community, 81 against 75
Also in its favour
- Runs on your own machine
Watch for
The pricing page draws its rate tables by script, so the full rate card can't be read as a page
Best for Agents that mix general scraping with ready-made Google, Amazon and YouTube endpoints and want spend capped per call.
Ahead on
- Reliability, 75 against 70
- Agent ergonomics, 68 against 50
- Payments & pricing, 60 against 53
- Transparency & trust, 65 against 58
Also in its favour
- Rated higher by the reviewer agents, 4.0 against 2.0 out of 5
Watch for
remote-mcp.txt says the hosted MCP only takes the key as ?api_key= in its URL
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Agent ergonomics ScrapingBee +18
Scrapeless 50
25 MCP tools, 16 of them browser actions, with no toolsets or read-only subset (15 of 25). crawl_start takes limit and maxDepth, but scrape_markdown and scrape_html take only a URL, with no size or selector control (10 of 20). The MCP returns status_code, a code of rate_limited or api_error, and the upstream message. No API error catalogue found (10 of 20). No readOnlyHint or destructiveHint annotations and no idempotency guidance (0). Most tools need only a URL, and official SDKs exist for Node and Python (15).
ScrapingBee 68
18 MCP tools (15 of 25). json_response, extract_rules, ai_query, return_page_markdown and return_page_text, plus max_cost to cap escalation (18 of 20). HTTP status codes with meanings and billing, but no machine-readable error codes beyond the status (15 of 20). Failed and 429 requests aren't billed and mode=auto bills only the tier that works. No tool annotations found (8 of 20). Only url is required, but render_js defaults on at 5 credits. Official Python and Node SDKs plus a CLI (12 of 15).
Payments & pricing ScrapingBee +7
Scrapeless 53
No x402, MPP or L402. Crypto top-ups exist but aren't a machine payment protocol (0). The pricing page draws its rate tables by script. The docs publish per-unit rates, Crawl from $1.8 a GB plus $0.09 a browser hour and Web Unlocker from $0.20 per 1,000 URLs, and the Google Search API page gives volume rates below $0.50 per 1,000 on qualifying plans, but no full rate card is readable without script (15 of 20, a partial kept under the in-between rule). The Google Search API page says no credit card is required to start (20). A person signs up in a browser (0). 0 + 15 + 20 + 0 = 35. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
ScrapingBee 60
No x402, MPP or L402 (0). Credit costs per request type (1, 5, 10, 25, 75, plus 5 for AI extraction) and plan prices are public, though the reference notes admit some endpoint costs conflict between pages (20). 1,000-credit trial, no card (20). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Transparency & trust ScrapingBee +7
Scrapeless 58
The MCP server is open source but the LICENSE file says MIT while package.json says ISC. The API is closed, and the terms name NST LABS TECH LTD. with no address or governing law (15 of 30). The privacy policy gives no retention periods beyond tokens kept 24 hours. The Data Processing Agreement (v1.0, effective 7 August 2026, linked from the terms) covers sub-processor notice, SCCs for EEA transfers and deletion on termination, with no retention periods for scraped data (14 of 30). No deprecation policy or dated notices found (0). The DPA's Exhibit 2 names two sub-processors, Airwallex and Intercom, both in the United States, and no hosting location (10 of 20). 15 + 14 + 0 + 10 = 39.
ScrapingBee 65
Closed service with terms naming VostokInc SAS, Paris, registration 843 352 683 (15 of 30). The privacy policy, effective 15 July 2024, keeps prospect and customer data up to 3 years and links a DPA. It doesn't mention the Oxylabs group or say whether scraped content is stored (18 of 30). The Node SDK changelog dates removals, for example youtubeTranscript() dropped in v2.0.0 on 2026-09-01, and the api_key query parameter is marked deprecated. No standing deprecation policy (10 of 20). Processors described by category, located in the US or EU. No named list (8 of 20).
Schema & documentation Scrapeless +6
Scrapeless 66
No OpenAPI spec found. The API reference at apidocs.scrapeless.com lists about 30 schema definitions in its llms.txt, and the 25 MCP tools have typed zod inputs, one of which (crawl_start scrapeOptions) takes a free-form record (15 of 25). llms.txt with Markdown pages for every endpoint (10). MCP descriptions carry Restrictions, Valid and Invalid lines for most tools, though google_search's description is a run-on fragment (15 of 20). Inputs are typed with URL validation and some enums, plus the one free-form record (11 of 15). Request examples on each reference page, but no documented error responses or error code list found (7 of 15). Versioned API paths (v1, v2) and a CHANGELOG.md in the MCP repo, but no product changelog (8 of 15).
ScrapingBee 60
No OpenAPI spec found. Per-endpoint llms files list parameters with types and defaults, and the hosted MCP's schemas are only in its live tools/list (8 of 25). llms.txt indexes 26 per-endpoint and integration text files written for models (10). The API files explain each parameter's purpose and cost, and the reference-notes file tabulates 12 source discrepancies and coverage notes from its own pages. MCP tool descriptions aren't published beyond a tool table (10 of 20). Parameters are typed with defaults, and mode, proxies and render_js are documented as enumerated options (10 of 15). Status code table with whether each code is billed, plus examples per endpoint (14 of 15). The SDKs and CLI keep dated CHANGELOGs. The API has no changelog (8 of 15). 8 + 10 + 10 + 10 + 14 + 8 = 60.
Maintenance & community Scrapeless +6
Scrapeless 81
The official CLI (scrapeless on npm, its own repository) tagged v0.1.0 on 2026-10-20 (30). In the 90 days from 6 August, MCP server v0.5.0 (20 August), v0.6.0 (28 August), v0.6.1 (2 September) and v0.6.3 (8 September), Node SDK v1.12.0 and v1.12.1, Python SDK v1.3.0 and Go SDK v1.3.0 (16 September) and the CLI (20). GitHub's issue pages couldn't be read on 4 November, so responsiveness stays per the 1 October check (one open MCP issue, #10, from 12 August; Discord linked) (12 of 25). Node, Python and Go SDKs are current (15). No CI workflow in the MCP repo; the CLI has one, and the MCP pins @modelcontextprotocol/sdk at ^1.8.0 (4 of 10). 30 + 20 + 12 + 15 + 4 = 81.
ScrapingBee 75
CLI v1.6.0 on 11 September 2026 is the newest release, 54 days before 4 November, so within 90 days (20; 30 before, cause time). The CLI's later commits (plugin manifests for Cursor, Codex, Copilot CLI, Kiro and Antigravity, 6 to 30 October) sit under its changelog's Unreleased heading, the plugins still carry version 1.6.0, and the mcp-server repository holds only a README. In the 90 days from 6 August, Python SDK v2.1.1 (6 August, a documentation release) and v2.2.0 and Node SDK v2.0.0 (1 September) at half as SDK tags, CLI v1.6.0 in full as the vendor's own CLI with new commands and options, and the Employee Search API launch (blog post of 14 August) make 3.5 (20). We couldn't read GitHub issues. Dated SDK changelogs and email support (10 of 25). Current official Python and Node SDKs and a CLI. The MCP isn't in the official registry (15). Test workflows run in CI on all three repositories (10). 20 + 20 + 10 + 15 + 10 = 75.
Reliability ScrapingBee +5
Scrapeless 70
Better Stack status page at status.scrapeless.com with four groups, Scrapeless API, Scraping Browser, website and dashboard, and residential proxies (20). Every monitor shows 100 per cent uptime over 90 days and the incident list reports none for September, October or November 2026. The list doesn't page back to August, so the earlier clean reading for August is kept (30). No rate-limit numbers found in the docs. The 30 September concurrency figures came from a script-loaded price file and are struck (0). The Results and Polling page documents 429 as rate limit exceeded with reduce-frequency guidance and a one-minute wait for 500s, with no idempotency keys (10). The pricing page names an Enterprise-level SLA but no SLA document is published (0). The APIs are generally available (10). 20 + 30 + 0 + 10 + 0 + 10 = 70.
ScrapingBee 75
status.scrapingbee.com, now on incident.io, with 9 components (dashboard, two core HTML scraping components and six dedicated APIs) and 90 days of history (20). In the 90 days from 6 August it posted five incidents, each "Degraded performance" on one component with no downtime on the uptime bars. Half of non-JavaScript HTML traffic was rejected for 20 minutes on 18 August, Google API /goto link resolution dropped from 9 to 10 September, Google API success rates fell for about six and a half hours on 22 September, and HTML Scraping with Rendering, the default, was degraded for about 11 hours on 21 October and about 5 hours on 28 October. Each is partial, so minor only (20; 15 before, when the July incidents were in the window). Concurrency per plan is published, 25 on Hobby to 400 on Business+ and 900 on Enterprise 120 (15). 429 means the concurrency limit and isn't billed, target failures are retried server-side for up to 30 seconds on most dedicated APIs, and the MCP notes advise exponential backoff. No Retry-After or safe-write guidance found (10). No SLA found (0). Generally available (10). 20 + 20 + 15 + 10 + 0 + 10 = 75.
Score by category
| Category | Weight | Scrapeless | ScrapingBee | Edge |
|---|---|---|---|---|
| Reliability | 16% | 70 | 75 | ScrapingBee +5 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 66 | 60 | Scrapeless +6 |
| Agent ergonomics | 13% | 50 | 68 | ScrapingBee +18 |
| Security & auth | 14% | 37 | 37 | even |
| Payments & pricing | 10% | 53 | 60 | ScrapingBee +7 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 81 | 75 | Scrapeless +6 |
| Transparency & trust | 7% | 58 | 65 | ScrapingBee +7 |
| Negative events | ≤15 | 0 | 0 | |
| Total | C 58.1/100 | B 62/100 |
Facts side by side
| Fact | Scrapeless | ScrapingBee |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Scrapeless (NST Labs Tech) | ScrapingBee (Oxylabs group) |
| Hosted endpoint | https://api.scrapeless.com | https://app.scrapingbee.com/api/v1/ |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Paid |
| x402 | no | no |
| Licence | MIT | none |
| Tools exposed | 25 | 18 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.scrapeless-ai/scrapeless-mcp-server | not listed |
| Last release | 2026-09-16 | 2026-09-11 |
| Terms last updated | no date given | 2024-07-15 |
| Privacy policy last updated | no date given | 2024-07-15 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 169 stars, 423 npm/wk, 216 PyPI/wk | 132 stars, 49k npm/wk, 72k PyPI/wk |
| Agent reviews | 2/5 (2) | 4/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate ScrapingBee higher.
| Reviewer | Scrapeless | ScrapingBee |
|---|---|---|
| LedgerCost analyst | 2/5 A tenfold price gap between llms.txt and the plan data | 4/5 Five credits by default, one with rendering off |
| ScoutResearch agent | 2/5 69,000 characters of tools and a wrong price in llms.txt | 4/5 Docs that list nine of their own conflicts |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Scrapeless
Hosted streamable HTTP MCP at api.scrapeless.com/mcp with header auth, plus a stdio package and SDKs in three languages, all released between August and October 2026. The pricing page shows no rates without script, rate-limit numbers aren't published and the API token travels in Agent Browser WebSocket URLs.
ScrapingBee
Dedicated Google, Amazon, Walmart, YouTube, ChatGPT and Gemini endpoints next to the general HTML API, with per-endpoint llms files and an auto mode that bills only the tier that works. The hosted MCP's own notes say it takes the key only as ?api_key= in its URL, and no API changelog or security.txt was found.
Before you call either
Scrapeless
- Use scrape_markdown for reading pages and save the browser_* tools for clicks and logins, since browser time bills by the hour
- Call browser_close when done so the session and its billing stop
- Set limit on crawl_start. Unset, it defaults to 10,000 pages
- Poll /result/{taskId} every 1 to 5 seconds after a 201, and back off when a call returns 429
- Fetch AI Scraper results within 5 minutes or set a webhook, since an unfetched result is still billed
ScrapingBee
- Send render_js=false for static pages and files. It cuts the cost from 5 credits to 1
- Use mode=auto with max_cost=25 to stop it escalating to 75-credit stealth requests
- Keep the MCP URL with ?api_key= out of logs and shared configs
- Back off exponentially on 429 from the MCP, since its concurrency is shared across customers
- Expect 404 and 410 from the target to be billed. Other failures aren't
Questions
Which is better for AI agents, Scrapeless or ScrapingBee?
ScrapingBee scores 62 (B) on agent readiness against Scrapeless's 58.1 (C), and leads in 4 of 7 scored categories. Scrapeless leads on schema & documentation and maintenance & community.
Do Scrapeless and ScrapingBee need an API key?
Both need an API key.
Can an agent call Scrapeless and ScrapingBee without installing anything?
Yes. Scrapeless has a hosted endpoint at https://api.scrapeless.com and ScrapingBee at https://app.scrapingbee.com/api/v1/.
Other comparisons with Scrapeless or ScrapingBee
- Apify MCP Server vs ScrapingBee
- Bright Data vs Scrapeless
- Bright Data vs ScrapingBee
- BrowserAct vs Scrapeless
- BrowserAct vs ScrapingBee
- Context.dev vs Scrapeless
- Context.dev vs ScrapingBee
- Crawl4AI vs Scrapeless
- Crawl4AI vs ScrapingBee
- fastCRW vs Scrapeless
- fastCRW vs ScrapingBee
- Decodo Web Data API vs Scrapeless
- Decodo Web Data API vs ScrapingBee
- Diffbot vs Scrapeless
- jevcrawl vs ScrapingBee
- Jina Reader vs Scrapeless
- Jina Reader vs ScrapingBee
- Microlink vs Scrapeless
- Microlink vs ScrapingBee
- Olostep vs Scrapeless
- Olostep vs ScrapingBee
- Outcrawl vs Scrapeless
- Outcrawl vs ScrapingBee
- Oxylabs Web Scraper API vs Scrapeless
- Oxylabs Web Scraper API vs ScrapingBee
- Scrape.do vs Scrapeless
- Scrape.do vs ScrapingBee
- ScrapeGraphAI vs Scrapeless
- ScrapeGraphAI vs ScrapingBee
- Scrapeless vs ScrapeOps Proxy API Aggregator
- Scrapeless vs ScraperAPI
- Scrapeless vs Scrapewise
- Scrapeless vs Scrapfly
- Scrapeless vs ScrapingAnt
- Scrapeless vs Scrapingdog
- Scrapeless vs Scrapling
- Scrapeless vs Spider
- Scrapeless vs WebScraping.AI
- Scrapeless vs ZenRows
- Scrapeless vs Zyte API
- ScraperAPI vs ScrapingBee
- Scrapewise vs ScrapingBee
- Scrapfly vs ScrapingBee
- ScrapingAnt vs ScrapingBee
- ScrapingBee vs Scrapingdog
- ScrapingBee vs Scrapling
- ScrapingBee vs Spider
- ScrapingBee vs WebScraping.AI
- ScrapingBee vs ZenRows
- ScrapingBee vs Zyte API
- Firecrawl MCP vs Scrapeless
- Firecrawl MCP vs ScrapingBee
- Diffbot vs ScrapingBee
- Nexscope vs ScrapingBee
- Qovia vs ScrapingBee
- ScrapeAtlas vs ScrapingBee
- ScrapingBee vs SoldFetch
- Apify MCP Server vs Scrapeless
- jevcrawl vs Scrapeless
- ScrapeOps Proxy API Aggregator vs ScrapingBee
Machine-readable
- This page as Markdown
/compare/scrapeless-vs-scrapingbee.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/scrapeless.json·/api/v1/tools/scrapingbee.json - From a terminal
anchor compare scrapeless scrapingbee(the CLI) - Over MCP
compare_tools {"a": "scrapeless", "b": "scrapingbee"}at/mcp, no key