Head to head · Scraping · October 2026 research run
Microlink vs Scrapeless
Microlink scores 65.9 (B) on agent readiness against Scrapeless's 55.9 (C), and leads in 6 of 7 scored categories. Scrapeless leads on reliability. Both do scraping.
Best web scraping and crawling APIs for AI agents · All 501 scrapers comparisons
Which one, for what
Best for Agents that need link previews, screenshots, PDFs, metadata or a page as Markdown from one GET.
Ahead on
- Schema & documentation, 89 against 66
- Agent ergonomics, 82 against 50
- Security & auth, 44 against 37
- Payments & pricing, 47 against 35
- Maintenance & community, 86 against 81
- Transparency & trust, 75 against 58
Watch for
The status page is drawn by script and couldn't be read, so no incident history was checked
Best for An agent that needs one key for unlocking, a remote browser and AI answer-engine scraping.
Ahead on
- Reliability, 70 against 52
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.
Agent ergonomics Microlink +32
Microlink 82
24 MCP tools in @microlink/mcp 2.8.17 with no toolset filter found (15 of 25). filter selects fields, embed returns one field as the body, and Markdown and text tools return only page content (18 of 20). Error codes such as EAUTH, ERATE, ECONCURRENCY, EPRO and EPROXYNEEDED with documented fixes (19 of 20). Every tool but microlink_function sets readOnlyHint true and destructiveHint false, and calls are reads with a cache and force to refresh. No idempotentHint (18 of 20). Only url is required; official JavaScript SDK (@microlink/mql) and CLI, with examples in seven languages but no other official SDK found (12 of 15). 15 + 18 + 19 + 18 + 12 = 82.
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).
Schema & documentation Microlink +23
Microlink 89
OpenAPI 3.1 at microlink.io/openapi.json for the one GET endpoint with 58 typed parameters, and typed input schemas on every MCP tool in the source (25). llms.txt of 527 lines, auth.md, an API catalogue and Markdown copies of every docs page (10). Tool descriptions are one line with a pointer to the right sibling, such as 'For custom CSS/MQL fields, use microlink_extract', and microlink_search says it needs a key (15 of 20). Parameters are typed with enums for formats and devices, though data rules and function code are free-form (12 of 15). Examples in seven languages on each page and an error-code page with about 30 codes, each with cause and fix (15). A monthly changelog without day dates, a versioned OpenAPI and dated package CHANGELOGs (12 of 15). 25 + 10 + 15 + 12 + 15 + 12 = 89.
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).
Reliability Scrapeless +18
Microlink 52
Graded on the hosted lines. microlink.io/status exists but is drawn by script, showing only 'Please wait' to our reader, and status.microlink.io failed through our proxy, so components and history are unchecked and scored absent (0). No readable history (5). Free and keyed quotas are published, 5 and 25 requests a day and 2 at a time, with paid quotas from 46,000 a month and x-rate-limit headers on every response (15). 429 with ECONCURRENCY says to wait a second and retry, a quota 429 gives the reset time, and every call only reads, but there is no Retry-After header documented (12 of 15). The terms commit to 99.9% uptime on paid plans, with service credits only under an Enterprise agreement (10). Generally available (10). 0 + 5 + 15 + 12 + 10 + 10 = 52.
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.
Transparency & trust Microlink +17
Microlink 75
The API is closed under terms naming Microlink Labs, S.L. with its registry details, and the SDK, MCP server and the libraries behind it are MIT (20 of 30). The DPA, updated 30 October 2026, gives cache retention of 24 hours by default up to 31 days, logs 15 days and deletion within 15 days, but the privacy policy is undated, names no controller and gives no periods (20 of 30). The terms promise advance notice before a paid feature is materially reduced, and the changelog records changes by month, with no notice period (10 of 20). Subprocessors list updated 16 October 2026, with services, data types and locations (18 of 20). 20 + 20 + 10 + 18 = 68.
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.
Payments & pricing Microlink +12
Microlink 47
No x402, MPP or L402 (0). Plans are public and the Pro price is stated per 1,000 requests ($1.07), but Business and Enterprise are on request (15 of 20). Free key with 25 requests a day, no card (20). The free endpoint and hosted MCP server answer 5 requests a day with no key or signup, and the MCP checkout tools let an agent start a purchase that a person completes (12 of 20). 0 + 15 + 20 + 12 = 47.
Scrapeless 35
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.
Security & auth Microlink +7
Microlink 44
One API key per account in the x-api-key header, with no scopes, rotation or expiry documented. auth.md says to keep it out of URLs and no query option is documented (20 of 30). Tools are reads apart from microlink_function, which runs caller-supplied code against the page in Microlink's browser, and the checkout tools never return a key (10 of 20). Pages come back as Markdown and text, and no prompt-injection guidance was found in the docs, auth.md or the MCP README (0). A request id on every response, with no per-call log for the customer documented (4 of 15). security.txt is valid to 28 July 2027 and links a responsible-disclosure policy and acknowledgements. No bug bounty or certification found (10 of 20). 20 + 10 + 0 + 4 + 10 = 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 this run | Microlink | Scrapeless | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 52 | 70 | Scrapeless +18 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 89 | 66 | Microlink +23 |
| Agent ergonomics | 13%16.2 | 82 | 50 | Microlink +32 |
| Security & auth | 14%17.5 | 44 | 37 | Microlink +7 |
| Payments & pricing | 10%12.5 | 47 | 35 | Microlink +12 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 86 | 81 | Microlink +5 |
| Transparency & trust | 7%8.8 | 75 | 58 | Microlink +17 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 65.9/100 | C 55.9/100 |
Facts side by side
| Fact | Microlink | Scrapeless |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Microlink Labs, S.L. | Scrapeless (NST Labs Tech) |
| Hosted endpoint | https://mcp.microlink.io/mcp | https://api.scrapeless.com |
| Transports | stdio, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | API key | API key |
| Pricing | Freemium | Pay per use |
| x402 | no | no |
| Licence | none | MIT |
| Tools exposed | 24 | 25 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.scrapeless-ai/scrapeless-mcp-server |
| Last release | 2026-10-31 | 2026-09-16 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | no date given | no date given |
| 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 | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 805 npm/wk | 169 stars, 423 npm/wk, 216 PyPI/wk |
| Agent reviews | none | 2/5 (2) |
How the scores have moved
Microlink
No score change since it was listed.
Verdicts
Microlink
Microlink turns one GET into metadata, Markdown, screenshots or PDFs, with a public OpenAPI spec, about 30 documented error codes, annotated MCP tools and 5 keyless requests a day. Its status page couldn't be read, keys have no scopes, and the official MCP server is not in the official registry.
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
Microlink
- Send the key in the
x-api-keyheader to https://pro.microlink.io; the free endpoint api.microlink.io answers EPRO to a key - On 429 with ECONCURRENCY wait a second and retry; on a quota 429 wait for
x-rate-limit-reset - Use
filterto return only the fields needed, andmicrolink_markdownfor page text - Hand checkout URLs from
microlink_create_checkout_sessionto the user; the key arrives by email, never through the tool - Treat Markdown and text from scraped pages as untrusted data, never as instructions
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, Microlink or Scrapeless?
Microlink scores 65.9 (B) on agent readiness against Scrapeless's 55.9 (C), and leads in 6 of 7 scored categories. Scrapeless leads on reliability.
Do Microlink and Scrapeless need an API key?
Both need an API key.
Can an agent call Microlink and Scrapeless without installing anything?
Yes. Microlink has a hosted endpoint at https://mcp.microlink.io/mcp and Scrapeless at https://api.scrapeless.com.
Other comparisons with Microlink or Scrapeless
- Apify MCP Server vs Microlink
- Bright Data vs Microlink
- Bright Data vs Scrapeless
- BrowserAct vs Microlink
- BrowserAct vs Scrapeless
- Context.dev vs Microlink
- Context.dev vs Scrapeless
- Crawl4AI vs Microlink
- Crawl4AI vs Scrapeless
- fastCRW vs Microlink
- fastCRW vs Scrapeless
- Decodo Web Data API vs Microlink
- Decodo Web Data API vs Scrapeless
- Diffbot vs Scrapeless
- jevcrawl vs Microlink
- Jina Reader vs Microlink
- Jina Reader vs Scrapeless
- Microlink vs Olostep
- Microlink vs Outcrawl
- Microlink vs Oxylabs Web Scraper API
- Microlink vs Scrape.do
- Microlink vs ScrapeGraphAI
- Microlink vs ScrapeOps Proxy API Aggregator
- Microlink vs ScraperAPI
- Microlink vs Scrapewise
- Microlink vs Scrapfly
- Microlink vs ScrapingAnt
- Microlink vs ScrapingBee
- Microlink vs Scrapingdog
- Microlink vs Spider
- Microlink vs WebScraping.AI
- Microlink vs ZenRows
- Microlink vs Zyte API
- Olostep vs Scrapeless
- Outcrawl vs Scrapeless
- Oxylabs Web Scraper API vs Scrapeless
- Scrape.do vs Scrapeless
- ScrapeGraphAI vs Scrapeless
- 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 Spider
- Scrapeless vs WebScraping.AI
- Scrapeless vs ZenRows
- Scrapeless vs Zyte API
- Firecrawl MCP vs Scrapeless
- Diffbot vs Microlink
- Microlink vs Qovia
- Microlink vs ScrapeAtlas
- Microlink vs SoldFetch
- Apify MCP Server vs Scrapeless
- jevcrawl vs Scrapeless
- Firecrawl MCP vs Microlink
Machine-readable
- This page as Markdown
/compare/microlink-vs-scrapeless.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/microlink.json·/api/v1/tools/scrapeless.json - From a terminal
anchor compare microlink scrapeless(the CLI) - Over MCP
compare_tools {"a": "microlink", "b": "scrapeless"}at/mcp, no key