# Microlink vs XCrawl (slim)

> Microlink scores 68.9 (B) to XCrawl's 30.4 (F) for scraping. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/microlink-vs-xcrawl.md (~5,250 tokens) · this version ~930 tokens · JSON https://www.anchorterminal.com/compare/microlink-vs-xcrawl.json · canonical https://www.anchorterminal.com/compare/microlink-vs-xcrawl
- 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-20
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Microlink scores 68.9 (B) on agent readiness against XCrawl's 30.4 (F), and leads in every scored category. Both do scraping.

- Microlink: B 68.9, rank #365 of 1563 · https://www.anchorterminal.com/tools/microlink.min.md
- XCrawl: F 30.4, rank #1463 of 1563 · https://www.anchorterminal.com/tools/xcrawl.min.md
- Microlink, good for Agents that need link previews, screenshots, PDFs, metadata or a page as Markdown from one GET. Ahead on Reliability, 52 against 15; Schema & documentation, 89 against 35; Agent ergonomics, 82 against 59; Security & auth, 44 against 18; Payments & pricing, 71 against 30; Maintenance & community, 86 against 17; Transparency & trust, 75 against 43.
- XCrawl, good for A general scrape, crawl, map and SERP API for agents, with 35 site-specific data endpoints.

| Category | Microlink | XCrawl |
| --- | --- | --- |
| Reliability (16%) | 52 | 15 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 89 | 35 |
| Agent ergonomics (13%) | 82 | 59 |
| Security & auth (14%) | 44 | 18 |
| Payments & pricing (10%) | 71 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 86 | 17 |
| Transparency & trust (7%) | 75 | 43 |

| Fact (where they differ) | Microlink | XCrawl |
| --- | --- | --- |
| Vendor | Microlink Labs, S.L. | XCrawl |
| Hosted endpoint | `https://mcp.microlink.io/mcp` | `https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp` |
| Transports | stdio, Streamable HTTP | Streamable HTTP, stdio |
| Tools exposed | 24 | 7 |
| llms.txt | yes | no |
| Last release | 2026-10-31 | 2026-04-13 |
| Terms or service can change without notice | not found in the text | yes |
| Popularity | 805 npm/wk | none |

Why the edge:
- Maintenance & community, Microlink +69: Microlink 86 (@microlink/mcp 2.8.17 and microlink.io 1.1.4 on 31 October 2026, and October changelog entries for the API (30).); XCrawl 17 (The newest dated releases are the Python SDK 1.1.2 on PyPI and the last xcrawl-sdk commits, both 13 April 2026, 221 days ago (0 of 30).)
- Schema & documentation, Microlink +54: 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).); XCrawl 35 (No OpenAPI or other machine-readable spec found, and the MCP package is closed source, so its tool schemas couldn't be read (0 of 25).)
- Payments & pricing, Microlink +41: Microlink 71 (No x402, MPP or L402 (0).); XCrawl 30 (No x402, MPP or L402 (0).)
- Reliability, Microlink +37: Microlink 52 (Graded on the hosted lines.); XCrawl 15 (No status page found on xcrawl.com or docs.xcrawl.com (0 of 20) and no readable incident history (5 of 30).)
- Transparency & trust, Microlink +32: 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).); XCrawl 43 (A closed service.)
- Security & auth, Microlink +26: Microlink 44 (One API key per account in the `x-api-key` header, with no scopes, rotation or expiry documented.); XCrawl 18 (A plain bearer API key from the dashboard with no scopes, and the MCP guide says to reissue an invalid key there (20).)
