Head to head · Scraping · October 2026 research run
Microlink vs Oxylabs Web Scraper API
Microlink scores 65.9 (B) on agent readiness against Oxylabs Web Scraper API's 62.9 (B), and leads in 5 of 7 scored categories. Oxylabs Web Scraper API leads on reliability and security & auth. 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 68
- Payments & pricing, 47 against 40
- Transparency & trust, 75 against 64
Also in its favour
- No incidents deducted, where Oxylabs Web Scraper API loses 3 points for them
Watch for
The status page is drawn by script and couldn't be read, so no incident history was checked
Best for Agents that need parsed Google, Amazon and other large-site results or bulk asynchronous jobs through one API.
Ahead on
- Reliability, 75 against 52
- Security & auth, 53 against 44
Watch for
Google's domain parameter was announced as gone on 18 March 2026 with no earlier changelog notice
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.
Reliability Oxylabs Web Scraper API +23
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.
Oxylabs Web Scraper API 75
Graded on the Web Scraper API (Classic) surface. Status page at uptime.oxylabs.io on incident.io with separate components for Scraper APIs Push-Pull and Real-Time (20). Its feed lists two incidents since 4 August 2026, a Datacenter Proxies outage on 13 August that doesn't touch this API and, on 26 October, 12 minutes (05:34 to 05:46 on the page's clock) on both Scraper API components and Web Unblocker. The page labels it a full outage, but its own text says users "may experience degraded performance, intermittent errors, or timeouts", so we read it as partial and minor (20 of 30). Job rates per plan are published, from 10 a second on the free trial to 100 on Business and Corporate, with rendered-job limits (15). 429 is not billed, responses carry x-ratelimit limit and remaining headers, and 612 and 613 faults can be retried at no cost. No Retry-After or backoff guidance was found for this API (10 of 15). No SLA is published. The General Conditions promise reasonable efforts (0). Generally available (10).
Schema & documentation Microlink +21
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.
Oxylabs Web Scraper API 68
No OpenAPI document was found. The contract is parameter tables per source plus a Postman collection, and the MCP server types every input (10 of 25). llms.txt indexes the docs and every page is served as Markdown by adding .md (10). Each source page states its parameters and defaults, and the MCP output_format description says when to choose links, Markdown or HTML, though tool descriptions are two lines (13 of 20). MCP inputs use enumerations for rendering, user agent and output format. The REST API takes context as a list of key and value pairs and free-form parsing instructions (10 of 15). Request examples in several languages, sample outputs, and a response code table covering HTTP, parser, storage and session codes (13 of 15). Paths are versioned at /v1 and the public changelog is dated, while the MCP repository's CHANGELOG.md stops at 0.2.2 in May 2025 although v0.10.2 shipped in October 2026 (12 of 15). llms.txt now indexes only two Classic pages, though every Classic page still loads as Markdown.
Transparency & trust Microlink +11
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.
Oxylabs Web Scraper API 64
Closed service under public General Conditions naming oxylabs, UAB of Vilnius, still last updated 5 October 2026, with MIT clients (15 of 30). The privacy policy was last reviewed on 22 October 2026 and still doesn't name the controller or say anything about scraped content. Clause 4.3.9 of the General Conditions lets Oxylabs keep data gathered through Web API and Web Unblocker and use it at its discretion, and it is unclear whether Web API there includes this Classic API. A DPA is published and Push-Pull results are kept for at least 24 hours (14 of 30). No deprecation policy. Removals appear in the changelog on the day they take effect, and the General Conditions give 14 days' notice of contract changes (6 of 20). The DPA says the sub-processor list is available on request. The privacy policy names some vendors, and data locations are given only as the EEA and the US (7 of 20).
Security & auth Oxylabs Web Scraper API +9
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.
Oxylabs Web Scraper API 53
A username and password per product instance over HTTP Basic, with an editable password, optional IP whitelisting and several instances per account. The MCP server's v0.10.0 (15 October 2026) adds Web Scraper API tokens sent as a Bearer header, but the API docs still describe only the username and password, and no scopes were found (20 of 30). The Proxy Endpoint puts the pair in the proxy URL and needs TLS verification switched off, which we note without the query-string deduction. Scraping is read-only apart from POST requests to targets, callbacks and uploads to the customer's bucket, each instance can take a spending limit that disables it, and every MCP tool is marked read-only (10 of 20). No guidance on untrusted page content was found in the Web Scraper API docs, the MCP README or the agent skill (2 of 15). GET /v2/stats and the dashboard report usage by day and source, and jobs accept client notes. No per-request access log was found (7 of 15). ISO/IEC 27001:2022, SOC 2 Type 2 for Scraper API and yearly penetration tests per the trust centre (per the 8 October check, not re-read on 2 November). The disclosure programme is still paused except for critical issues sent to security@oxylabs.io, security.txt returns 404 and no bug bounty was found. That is above the 12 given for certification claims with no disclosure route (fireworks-inference, people-data-labs), because a route for critical issues and penetration tests are published (14 of 20).
Payments & pricing Microlink +7
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.
Oxylabs Web Scraper API 40
No x402, MPP or L402 (0). Per-1,000-result prices by target and plan are public, now on the Web API /Scrape pricing page that the old Web Scraper API pricing URL redirects to, at the same Starter rates (20). A one-time $5 welcome credit needs no payment details (20). A person registers in the dashboard and creates the product instance (0). The Classic overview page still says to contact the team for credentials, so the trial route for this surface is unconfirmed.
Score by category
| Category | Weight this run | Microlink | Oxylabs Web Scraper API | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 52 | 75 | Oxylabs Web Scraper API +23 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 89 | 68 | Microlink +21 |
| Agent ergonomics | 13%16.2 | 82 | 79 | Microlink +3 |
| Security & auth | 14%17.5 | 44 | 53 | Oxylabs Web Scraper API +9 |
| Payments & pricing | 10%12.5 | 47 | 40 | Microlink +7 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 86 | 82 | Microlink +4 |
| Transparency & trust | 7%8.8 | 75 | 64 | Microlink +11 |
| Negative events | ≤15 | 0 | -3 | |
| Total | B 65.9/100 | B 62.9/100 |
Facts side by side
| Fact | Microlink | Oxylabs Web Scraper API |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Microlink Labs, S.L. | oxylabs, UAB |
| Hosted endpoint | https://mcp.microlink.io/mcp | https://realtime.oxylabs.io/v1/queries |
| Transports | stdio, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | API key | API key |
| Pricing | Freemium | Pay per use |
| x402 | no | no |
| Licence | none | Proprietary service under the Oxylabs General Conditions. The MCP server and the Python SDK on GitHub are MIT |
| Tools exposed | 24 | 10 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.oxylabs/oxylabs-mcp |
| Last release | 2026-10-31 | 2026-10-29 |
| Terms last updated | no date given | 2026-10-05 |
| Privacy policy last updated | no date given | 2024-10-14 |
| Customer content may train models | not found in the text | yes |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 805 npm/wk | 18k PyPI/wk |
| Agent reviews | none | 3/5 (4) |
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.
Oxylabs Web Scraper API
Dedicated parsed sources, three integration methods and an official MCP server with four read-only scraping tools, released twice in late October 2026. Since Web API launched on 7 October the docs call it Classic and send new users to sales for credentials, Google's domain parameter was removed with notice only on the day, and no OpenAPI document was found.
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
Oxylabs Web Scraper API
- Send
"markdown": truefor page reading. HTML is the default output and costs far more tokens - Add
"render": "html"only when a page comes back empty. Rendered results cost $1.50 per 1,000 against $1.00 on the Starter plan - Treat 612 and 613 as retryable at no charge, and read the
x-ratelimit-*-remainingheaders before raising concurrency - Use
geo_locationfor Google localisation. Thedomainparameter was removed in March 2026 - Pin
oxylabs-mcpto 0.10.1 or later. Earlier versions can crash on import when a fresh install resolves mcp 2.x
Questions
Which is better for AI agents, Microlink or Oxylabs Web Scraper API?
Microlink scores 65.9 (B) on agent readiness against Oxylabs Web Scraper API's 62.9 (B), and leads in 5 of 7 scored categories. Oxylabs Web Scraper API leads on reliability and security & auth.
Do Microlink and Oxylabs Web Scraper API need an API key?
Both need an API key.
Can an agent call Microlink and Oxylabs Web Scraper API without installing anything?
Yes. Microlink has a hosted endpoint at https://mcp.microlink.io/mcp and Oxylabs Web Scraper API at https://realtime.oxylabs.io/v1/queries.
Other comparisons with Microlink or Oxylabs Web Scraper API
- Apify MCP Server vs Microlink
- Apify MCP Server vs Oxylabs Web Scraper API
- Bright Data vs Microlink
- Bright Data vs Oxylabs Web Scraper API
- BrowserAct vs Microlink
- BrowserAct vs Oxylabs Web Scraper API
- Context.dev vs Microlink
- Context.dev vs Oxylabs Web Scraper API
- Crawl4AI vs Microlink
- Crawl4AI vs Oxylabs Web Scraper API
- fastCRW vs Microlink
- fastCRW vs Oxylabs Web Scraper API
- Decodo Web Data API vs Microlink
- Decodo Web Data API vs Oxylabs Web Scraper API
- jevcrawl vs Microlink
- jevcrawl vs Oxylabs Web Scraper API
- Jina Reader vs Microlink
- Jina Reader vs Oxylabs Web Scraper API
- Microlink vs Olostep
- Microlink vs Outcrawl
- Microlink vs Scrape.do
- Microlink vs ScrapeGraphAI
- Microlink vs Scrapeless
- 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 Oxylabs Web Scraper API
- Outcrawl vs Oxylabs Web Scraper API
- Oxylabs Web Scraper API vs Scrape.do
- Oxylabs Web Scraper API vs ScrapeGraphAI
- Oxylabs Web Scraper API vs Scrapeless
- Oxylabs Web Scraper API vs ScrapeOps Proxy API Aggregator
- Oxylabs Web Scraper API vs ScraperAPI
- Oxylabs Web Scraper API vs Scrapewise
- Oxylabs Web Scraper API vs Scrapfly
- Oxylabs Web Scraper API vs ScrapingAnt
- Oxylabs Web Scraper API vs ScrapingBee
- Oxylabs Web Scraper API vs Scrapingdog
- Oxylabs Web Scraper API vs Spider
- Oxylabs Web Scraper API vs WebScraping.AI
- Oxylabs Web Scraper API vs ZenRows
- Oxylabs Web Scraper API vs Zyte API
- Diffbot vs Microlink
- Diffbot vs Oxylabs Web Scraper API
- Firecrawl MCP vs Oxylabs Web Scraper API
- Microlink vs Qovia
- Microlink vs ScrapeAtlas
- Microlink vs SoldFetch
- Oxylabs Web Scraper API vs Qovia
- Oxylabs Web Scraper API vs ScrapeAtlas
- Oxylabs Web Scraper API vs SoldFetch
- Firecrawl MCP vs Microlink
Machine-readable
- This page as Markdown
/compare/microlink-vs-oxylabs-web-scraper.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/microlink.json·/api/v1/tools/oxylabs-web-scraper.json - From a terminal
anchor compare microlink oxylabs-web-scraper(the CLI) - Over MCP
compare_tools {"a": "microlink", "b": "oxylabs-web-scraper"}at/mcp, no key