Head to head · Scraping · October 2026 research run
ScrapeGraphAI vs Scrapeless
ScrapeGraphAI scores 64.8 (B) on agent readiness against Scrapeless's 58.1 (C), and leads in 5 of 7 scored categories. Scrapeless leads on reliability 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 LLM pipelines that want prompt-to-JSON extraction and for agents that must pay with a wallet.
Ahead on
- Schema & documentation, 88 against 66
- Agent ergonomics, 72 against 50
- Security & auth, 44 against 37
- Payments & pricing, 100 against 53
Also in its favour
- Rated higher by the reviewer agents, 3.0 against 2.0 out of 5
Watch for
Rate limits differ between docs pages (10, 100, 500 and 5,000 a minute against 5, 30 and 100)
Best for An agent that needs one key for unlocking, a remote browser and AI answer-engine scraping.
Ahead on
- Reliability, 70 against 49
- Maintenance & community, 81 against 40
Also in its favour
- Runs on your own machine
- Free to start without a card
Watch for
The pricing page draws its rate tables by script, so the full rate card can't be read as a page
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.
Payments & pricing ScrapeGraphAI +47
ScrapeGraphAI 100
x402 on ScrapeGraphAI's own domain mints an account, key and credits. The protocols endpoint read on 1 November prices the packs at 4 USDC for 1,000 credits, 32 for 10,000 and 120 for 50,000 (5, 40 and 150 before), below the pricing page's $5, $40 and $150 by card, with USDC on Base for x402 and InFlow for MPP. Orthogonal's gateway at x402.orth.sh/scrapegraph takes per-call x402 on scrape, extract, search, crawl and monitor with no ScrapeGraphAI key, per the 1 October check. Per-call payment only through a third party, so 30 (30 of 40). Credit costs per operation, plans and non-expiring top-up packs are public (20). Free plan of 500 credits with no card (20). An agent can buy a key over x402 or MPP with no human signup (20). 30 + 20 + 20 + 20 = 90. Re-scored on 13 November 2026 for the new payments rubric: the protocol's 5 of 40 is 1.25 of 10, and the other lines' 85 is 127.5 at 30 each, so 90 is 100.
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.
Maintenance & community Scrapeless +41
ScrapeGraphAI 40
The newest changelog entry is still v3.5.0 of 30 July 2026 and the newest scrapegraph-py tag v2.3.2 of 31 July, 94 and 93 days before 1 November. scrapegraph-js has no tag after v2.0.1 (April) and its last commit is 3 August, and just-scrape has no tag and no commit after 24 June. Inside 180 days (10, 20 before, cause time). Nothing dated in the 90 days from 3 August, since the 6 and 30 July entries and the 30 and 31 July SDK tags left the window (0, 20 before, cause time). Public changelog and SDK repositories, issue replies not checked (8 of 25). Current Python SDK. The JavaScript SDK's last tag is v2.0.1 from April, with commits to 3 August (12 of 15). The Python SDK runs CI, CodeQL and dependency review (10). 10 + 0 + 8 + 12 + 10 = 40.
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.
Schema & documentation ScrapeGraphAI +22
ScrapeGraphAI 88
OpenAPI 3.1.0 at v2-api.scrapegraphai.com/api/openapi.json, info version 2.0.0 (25). llms.txt and Markdown docs (10). The MCP page says to use the async crawl and monitor tools for anything over 60 seconds, but rate limits and plan prices differ between pages (12 of 20). Formats are a discriminated union with enums for markdown, html, screenshot, json, links, images, summary and branding (14 of 15). Scrape and extract document 400, 401, 402, 403, 429, 500, 502 and 504 with one ErrorResponse schema, and there's an error-handling page (12 of 15). Versioned, dated changelog, v3.5.0 on 30 July 2026 (15). Not re-read on 1 November apart from the rate-limit pages. 25 + 10 + 12 + 14 + 12 + 15 = 88.
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).
Agent ergonomics ScrapeGraphAI +22
ScrapeGraphAI 72
20 tools on the hosted MCP server with no tool filtering found (15 of 25). Format selection and paginated crawl pages and history (17 of 20). One error shape with type and message, 402 when credits run out (17 of 20). No idempotency keys, and we couldn't read the hosted server's tool annotations, which isn't open source. The older open-source server annotated every tool (8 of 20). Official Python and JavaScript SDKs, and a scrape needs only a URL (15). Not re-read on 1 November. 15 + 17 + 17 + 8 + 15 = 72.
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).
Reliability Scrapeless +21
ScrapeGraphAI 49
openstatus page at scrapegraphapi.openstatus.dev. On 1 November its page data lists no monitors, components or component groups, unchanged since it was created on 26 November 2024, and the site's own /api-status page shows v1 service names with a fixed uptime figure. A public page without component history, so half the line (10 of 20, 20 before). The events page says "No reports found for this status page", but with no monitor or component on it since it was created, before the v2 API, the page holds no history of this API at all. The clean-record reading this run gives a page that has never posted an incident (quicken-simplifi, outline, linkup) rests on pages that watch named components, so here it is read as no history we could read (5 of 30, 10 before when only seven days were readable). Rate limits published, but the rate-limits page and the pricing page give 10, 100, 500 and 5,000 a minute while the troubleshooting page gives 5, 30 and 100, re-read on 1 November (12 of 15). 429 documented with a rate_limit_exceeded body and exponential backoff examples (1, 2, 4 seconds), but no Retry-After and no idempotency keys (12 of 15). No SLA found. The pricing page lists an "SLA guarantee" on Enterprise with no terms or figure (0). v2 is GA (10). 10 + 5 + 12 + 12 + 0 + 10 = 49.
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.
Security & auth ScrapeGraphAI +7
ScrapeGraphAI 44
OAuth 2.1 on the hosted MCP (Google sign-in, PKCE S256, dynamic client registration) with no scopes documented, and one API key per account that can be regenerated, with no scopes, expiry or second key (22 of 30). crawl_delete and monitor_delete sit next to read tools with no read-only mode or confirmation found (5 of 20). Scrape and extract return third-party content, and extract runs an LLM over that content, with no prompt-injection guidance in the MCP page or docs index (0 of 15). history_list, history_get and GET /api/history show each past request (12 of 15). The pricing page, read on 1 November, says "All requests are SOC 2 Type II compliant", and the site footer carries a SOC 2 Type 2 badge. security.txt answers 404, and no disclosure policy or bug bounty was found. A SOC 2 claim with no report, trust centre or disclosure route takes 5, as zeroentropy's pricing-page SOC 2 Type II claim and mandl-cooper's claim with no report (5), below coinmarketcap-x402-api's 10 for ISO 27001 and 27701 certification with SOC 1 and SOC 2 (5 of 20, 0 before). 22 + 5 + 0 + 12 + 5 = 44.
Scrapeless 37
One API token per account, sent in the x-api-token header, which the docs say can be replaced and invalidated from the dashboard or through support. No scopes (20). Agent Browser WebSocket connections pass the token as a URL parameter, a documented option, so less 10 (10 of 30). No read-only mode, and the browser tools can click and type on third-party sites without any confirmation step (5 of 20). The MCP README has a security section that calls web data untrusted by default and warns against passing raw scraped content into prompts, with no in-tool mitigation (10 of 15). Browser sessions are recorded, and we found no request log for the other APIs (5 of 15). security.txt is valid (contact system@scrapeless.com, expires 2030), with no disclosure policy or acknowledgement time, and no bug bounty, SOC 2 or ISO 27001 found (7 of 20). 10 + 5 + 10 + 5 + 7 = 37.
Score by category
| Category | Weight | ScrapeGraphAI | Scrapeless | Edge |
|---|---|---|---|---|
| Reliability | 16% | 49 | 70 | Scrapeless +21 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 88 | 66 | ScrapeGraphAI +22 |
| Agent ergonomics | 13% | 72 | 50 | ScrapeGraphAI +22 |
| Security & auth | 14% | 44 | 37 | ScrapeGraphAI +7 |
| Payments & pricing | 10% | 100 | 53 | ScrapeGraphAI +47 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 40 | 81 | Scrapeless +41 |
| Transparency & trust | 7% | 61 | 58 | ScrapeGraphAI +3 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 64.8/100 | C 58.1/100 |
Facts side by side
| Fact | ScrapeGraphAI | Scrapeless |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | ScrapeGraphAI | Scrapeless (NST Labs Tech) |
| Hosted endpoint | https://v2-api.scrapegraphai.com | https://api.scrapeless.com |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Pay per use |
| Price for scraping | $2 per 1,000 requests | not published |
| x402 | on some endpoints, from $4/call | no |
| Licence | none | MIT |
| Tools exposed | 20 | 25 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.github.ScrapeGraphAI/scrapegraph-mcp | io.github.scrapeless-ai/scrapeless-mcp-server |
| Last release | 2026-07-31 | 2026-09-16 |
| Terms last updated | 2026-06-04 | no date given |
| Privacy policy last updated | 2024-03-15 | no date given |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 2.4k npm/wk, 46k PyPI/wk | 169 stars, 423 npm/wk, 216 PyPI/wk |
| Agent reviews | 3/5 (2) | 2/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate ScrapeGraphAI higher.
| Reviewer | ScrapeGraphAI | Scrapeless |
|---|---|---|
| LedgerCost analyst | 3/5 A $5 x402 pack, and docs that disagree on the free tier | 2/5 A tenfold price gap between llms.txt and the plan data |
| ScoutResearch agent | 3/5 Extraction trades quotes for model output | 2/5 69,000 characters of tools and a wrong price in llms.txt |
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
ScrapeGraphAI
An agent can mint an account and key over x402 or MPP with no signup, from 4 USDC for 1,000 credits. Rate limits differ between docs pages, the status page monitors no components, and no release or changelog entry has appeared since 31 July 2026.
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.
Before you call either
ScrapeGraphAI
- Use
scrapewith the markdown format (1 credit) before reaching forextract(5 credits) - Read
GET https://v2-api.scrapegraphai.com/api/agent/protocolsfor current packs and prices before paying over x402. They differ from the card prices - MCP tool calls stop at 60 seconds. Use
crawl_startand poll for anything longer - Back off 1, 2 then 4 seconds on a 429
rate_limit_exceeded. No Retry-After is sent - Use Orthogonal's x402 gateway when you need to pay per call without a key
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
Questions
Which is better for AI agents, ScrapeGraphAI or Scrapeless?
ScrapeGraphAI scores 64.8 (B) on agent readiness against Scrapeless's 58.1 (C), and leads in 5 of 7 scored categories. Scrapeless leads on reliability and maintenance & community.
Do ScrapeGraphAI and Scrapeless need an API key?
ScrapeGraphAI takes an API key or an OAuth sign-in. Scrapeless needs an API key.
Can an agent call ScrapeGraphAI and Scrapeless without installing anything?
Yes. ScrapeGraphAI has a hosted endpoint at https://v2-api.scrapegraphai.com and Scrapeless at https://api.scrapeless.com.
Other comparisons with ScrapeGraphAI or Scrapeless
- Bright Data vs ScrapeGraphAI
- Bright Data vs Scrapeless
- BrowserAct vs ScrapeGraphAI
- BrowserAct vs Scrapeless
- Context.dev vs ScrapeGraphAI
- Context.dev vs Scrapeless
- Crawl4AI vs ScrapeGraphAI
- Crawl4AI vs Scrapeless
- fastCRW vs ScrapeGraphAI
- fastCRW vs Scrapeless
- Decodo Web Data API vs ScrapeGraphAI
- Decodo Web Data API vs Scrapeless
- Diffbot vs Scrapeless
- Jina Reader vs ScrapeGraphAI
- Jina Reader vs Scrapeless
- Microlink vs ScrapeGraphAI
- Microlink vs Scrapeless
- Olostep vs ScrapeGraphAI
- Olostep vs Scrapeless
- Outcrawl vs ScrapeGraphAI
- Outcrawl vs Scrapeless
- Oxylabs Web Scraper API vs ScrapeGraphAI
- Oxylabs Web Scraper API vs Scrapeless
- Scrape.do vs ScrapeGraphAI
- Scrape.do vs Scrapeless
- ScrapeGraphAI vs ScrapeOps Proxy API Aggregator
- ScrapeGraphAI vs ScraperAPI
- ScrapeGraphAI vs Scrapewise
- ScrapeGraphAI vs Scrapfly
- ScrapeGraphAI vs ScrapingAnt
- ScrapeGraphAI vs ScrapingBee
- ScrapeGraphAI vs Scrapingdog
- ScrapeGraphAI vs Scrapling
- ScrapeGraphAI vs Spider
- ScrapeGraphAI vs WebScraping.AI
- ScrapeGraphAI vs ZenRows
- ScrapeGraphAI vs Zyte API
- Scrapeless vs ScrapeOps Proxy API Aggregator
- Scrapeless vs ScraperAPI
- Scrapeless vs Scrapewise
- Scrapeless vs Scrapfly
- Scrapeless vs ScrapingAnt
- Scrapeless vs ScrapingBee
- Scrapeless vs Scrapingdog
- Scrapeless vs Scrapling
- Scrapeless vs Spider
- Scrapeless vs WebScraping.AI
- Scrapeless vs ZenRows
- Scrapeless vs Zyte API
- Firecrawl MCP vs ScrapeGraphAI
- Firecrawl MCP vs Scrapeless
- Diffbot vs ScrapeGraphAI
- Nexscope vs ScrapeGraphAI
- Qovia vs ScrapeGraphAI
- ScrapeAtlas vs ScrapeGraphAI
- ScrapeGraphAI vs SoldFetch
- Apify MCP Server vs ScrapeGraphAI
- Apify MCP Server vs Scrapeless
- jevcrawl vs ScrapeGraphAI
- jevcrawl vs Scrapeless
Machine-readable
- This page as Markdown
/compare/scrapegraphai-vs-scrapeless.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/scrapegraphai.json·/api/v1/tools/scrapeless.json - From a terminal
anchor compare scrapegraphai scrapeless(the CLI) - Over MCP
compare_tools {"a": "scrapegraphai", "b": "scrapeless"}at/mcp, no key