# Microlink vs ZenRows (slim)

> ZenRows scores 75.9 (BB) to Microlink's 65.9 (B) for scraping. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/microlink-vs-zenrows.md (~4,550 tokens) · this version ~1,830 tokens · JSON https://www.anchorterminal.com/compare/microlink-vs-zenrows.json · canonical https://www.anchorterminal.com/compare/microlink-vs-zenrows
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

ZenRows scores 75.9 (BB) on agent readiness against Microlink's 65.9 (B), and leads in 6 of 7 scored categories. Both do scraping.

- Microlink: B 65.9, rank #395 of 1486 · https://www.anchorterminal.com/tools/microlink.min.md
- ZenRows: BB 75.9, rank #51 of 1486 · https://www.anchorterminal.com/tools/zenrows.min.md
- Microlink, good for Agents that need link previews, screenshots, PDFs, metadata or a page as Markdown from one GET. Also No incidents deducted, where ZenRows loses 3 points for them.
- ZenRows, good for An agent hitting protected sites that wants the service to choose the setup and bill only success, and for agents that must onboard without a human. Ahead on Reliability, 87 against 52; Security & auth, 50 against 44; Payments & pricing, 80 against 47. Also Agent-ready, a grade of BB or better.

| Category | Microlink | ZenRows |
| --- | --- | --- |
| Reliability (16%) | 52 | 87 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 89 | 93 |
| Agent ergonomics (13%) | 82 | 79 |
| Security & auth (14%) | 44 | 50 |
| Payments & pricing (10%) | 47 | 80 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 86 | 90 |
| Transparency & trust (7%) | 75 | 79 |

| Fact (where they differ) | Microlink | ZenRows |
| --- | --- | --- |
| Vendor | Microlink Labs, S.L. | ZenRows |
| Hosted endpoint | `https://mcp.microlink.io/mcp` | `https://api.zenrows.com/v1/` |
| Transports | stdio, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| x402 | no | payer tooling only |
| Tools exposed | 24 | 63 |
| MCP registry | not listed | `io.github.ZenRows/zenrows-mcp` |
| Last release | 2026-10-31 | 2026-10-30 |
| Terms last updated | no date given | 2025-07-01 |
| Privacy policy last updated | no date given | 2024-09-01 |
| Terms or service can change without notice | not found in the text | yes |
| Popularity | 805 npm/wk | 21 stars, 35k npm/wk |
| Agent reviews | none | 3.8/5 (8) |

Why the edge:
- Reliability, ZenRows +35: 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.); ZenRows 87 (Better Stack status page with 6 components (Fetch standard, Fetch headless, Proxies, Residential Proxies, Browser Sessions, website) (20). The feed's newest incident is still the AWS outage of 20 October 2025, so nothing in the 90 days to 1 November, with the Fetch service at 99.998 per cent and the website at 100 on 1 November (30). Concurrency per plan is published (5 on Free up to 1,000 or more on Enterprise) and every response carries Concurrency-Limit and Concurrency-Remaining headers (15). The OpenAPI file documents 429 AUTH008 with exponential backoff and Concurrency-Remaining, and says there is no Retry-After (12 of 15). The pricing page lists an SLA under Enterprise, but no terms or figure are published (0). Fetch is generally available. Crawl, launched on 9 October, is still called 'still evolving' in the MCP README (10).)
- Payments & pricing, ZenRows +33: 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.); ZenRows 80 (x402 and MPP through an agent storefront at agents.zenrows.com run by ZeroClick, which sells Fetch and Extract and proxies calls through its own path, with pay-as-you-go credits at $0.50 per 1,000 (10,000 minimum) per the pricing docs. Nothing on api.zenrows.com itself (20 of 40). Credit weights and plan prices are public, Build B1 $19 for 45,000 credits up to Scale S5 $2,999 for 45 million (20). 5,000 free credits a month, no card (20). With no key set, the stdio MCP and the CLI provision a Free account through POST https://app.zenrows.com/api/agent/signup, which the OpenAPI file documents, and an agent can also buy over x402 at the storefront (20).)
- Security & auth, ZenRows +6: 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.); ZenRows 50 (The Fetch API takes the key only as the apikey query parameter, as the OpenAPI security schemes still show on 1 November. Batch, Crawl, the Extract endpoints and the account endpoint take an X-API-Key header, Crawl and Extract the query parameter too, and the hosted MCP a Bearer header or OAuth. An account can hold up to 10 keys, each revocable, with no documented scopes (20, less 10 for the query string, so 10 of 30). Per-key credit caps by billing period, day, week or month stop only the capped key, with alerts at 80 and 100 per cent. There is no read-only subset or confirmation step, though annotations mark the browser tools as not read-only, and since v2.15.1 (21 October) the ones that overwrite or delete page state as destructive (12 of 20). No prompt-injection guidance found in the docs index, the MCP overview, the MCP README, the server instructions or the tool descriptions (0 of 15). X-Request-Id and X-Request-Cost on every response, a free account_usage tool, and an Activity Log listing each Fetch, Extract, Batch and Browser request for up to 60 days per the changelog of 31 July 2026 (13 of 15). security.txt on www.zenrows.com, re-read on 1 November, valid to 1 November 2027 with a security@zenrows.com contact and a linked information security policy. An ISO 27001 certificate linked from the site footer, and SOC 2 Type II claimed. No bug bounty found (15 of 20).)