Head to head · Scraping · October 2026 research run

Jina Reader vs XCrawl

Jina Reader scores 54.1 (C) on agent readiness against XCrawl's 30.4 (F), and leads in every scored category. Both do scraping.

Best web scraping and crawling APIs for AI agents · All 601 scrapers comparisons

Which one, for what

Jina Reader C

Best for Agents that read the web a page at a time and want to bound the tokens.

Ahead on

  • Reliability, 70 against 15
  • Schema & documentation, 77 against 35
  • Agent ergonomics, 80 against 59
  • Security & auth, 32 against 18
  • Payments & pricing, 53 against 30
  • Maintenance & community, 45 against 17
  • Transparency & trust, 62 against 43

Also in its favour

  • Open source

Watch for

No price per token in any currency on the public page

XCrawl F

Best for A general scrape, crawl, map and SERP API for agents, with 35 site-specific data endpoints.

Also in its favour

  • Runs on your own machine
  • Free to start without a card
  • No incidents deducted, where Jina Reader loses 7 points for them

Watch for

Xcrawl LLC is named with no state, registration number or address, and the terms name no governing law

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 Jina Reader +55

Jina Reader 70

Atlassian Statuspage at status.jina.ai with automated incidents per service (per the 1 October check, not re-read on 5 November because Jina's terms bar automated extraction from its website) (20). On 1 October the feed reached back only to 15 September 2026. In that window r.jina.ai had no incidents and s.jina.ai had eight five-minute ones. Minor only, less 5 for the short window. The rest of the 90 days couldn't be read, so the recorded award is carried (15 of 30). Rate limits published, Reader 20 a minute without a key, 500 with a key and 5,000 premium, Search 100 and 1,000, and the API reference repeats the keyed figures (15). Jina's merged OpenAPI file (docs.jina.ai/openapi.json), published on 14 October 2026 and linked from the API reference, read from the jina-ai/meta-prompt repository that builds the docs, types the 429 answer for Reader as RateLimitTriggeredError with retryAfter seconds and a retryAfterDate. No backoff guidance, and Reader takes no writes (10). No SLA found (0). GA (10).

XCrawl 15

No status page found on xcrawl.com or docs.xcrawl.com (0 of 20) and no readable incident history (5 of 30). No rate limits with numbers. The pricing page says only that Scale plans get higher rate limits (0 of 15). No 429 or overload guidance in the docs. The Python SDK retries 500, 502, 503 and 504 with backoff, but not 429 (0 of 15). The terms mention a Service Level Agreement "if applicable", and none is published (0 of 10). The API is sold publicly with no beta label (10). Total 15.

Schema & documentation Jina Reader +42

Jina Reader 77

Jina's merged OpenAPI file (docs.jina.ai/openapi.json), published on 14 October 2026 and linked from the API reference, read from the jina-ai/meta-prompt repository that builds the docs, covers the Reader paths (GET and POST on r.jina.ai) with 98 typed parameters each and a typed response for every status. The Markdown reference at docs.jina.ai/api.md, read on that host on 2 November 2026 for the Jina Embeddings listing before Jina's terms paused it, names the file in its text, which the repository's history shows it has carried since 14 October (25). The reference is also published as Markdown at docs.jina.ai/api.md, and docs.jina.ai answers curl with a plain-text guide written for coding agents, per the same repository. The Reader README is a full Markdown reference of every header (10). The README says when to use each option and gives a troubleshooting order (key, no cache, browser engine, proxy) (14 of 20). Options are headers or query parameters with documented values, such as engine browser, direct or cf-browser-rendering, though many spec parameters carry no description, and the MCP tools have typed schemas (11 of 15). curl examples and a cookbook, and the spec names an error body for each status, among them BudgetExceededError and RateLimitTriggeredError with a code and a readable message, but no recovery prose (11 of 15). No API changelog. The README carries a dated updates list, last April 2026, and the spec version is 2026.10.13.1624 (6 of 15).

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). llms.txt returns 404. The docs have "Copy page" buttons, and the xcrawl-skills repository has Markdown skill files for agents (5 of 10). Each API reference page states what the endpoint does, with no guidance on when not to use it (8 of 20). Parameter tables give types, required flags, defaults and enums for formats, device and wait_until. cookies and headers are free maps (11 of 15). Request and response examples on every reference page, but no error responses or codes documented outside the MCP troubleshooting table (6 of 15). Versioned /v1 paths and no changelog (5 of 15). Total 35.

Maintenance & community Jina Reader +28

Jina Reader 45

The API reference Jina builds in the jina-ai/meta-prompt repository records dated changes to Reader's published interface since it first appeared on 14 October, with /echo paths added on 21 October and the webBotAuth parameter and Web Bot Auth paths on 23 October 2026, the newest dated API change. The MCP server's last version, 1.10.0, is dated 18 September (30). The MCP versions 1.5.0 to 1.10.0 between 11 August and 18 September are untagged bumps in package.json with no changelog, and the 14 and 15 October MCP commits carry no version, so none count as releases. The reference changes carry no version or changelog entry either (0). 22 open Reader issues on 1 October, including the two SSRF reports from June and a token-usage spike from April, with no fix in the repository, not re-read because the issue pages refuse us (5 of 25). No official SDK, the MCP server is the maintained client (5 of 15). Reader has CI workflows, the MCP repository has none (5 of 10).

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). Nothing dated in the 90 days from 22 August 2026 (0 of 20). We couldn't read GitHub issues. There is no public changelog, and support is by email, Telegram, WhatsApp and Microsoft Teams, with a 24-hour reply promised in the footer (5 of 15). Official Python and Node.js SDKs, unchanged for seven months (10 of 15). The SDK repository has 3 commits, no tests and no CI. Dependencies are current (2 of 10). Total 17.

Payments & pricing Jina Reader +23

Jina Reader 53

No x402, MPP or L402 (0). Billed in tokens with no price in any currency on the Reader page, which points to a separate table, per the 1 October check, not re-read on 5 November because Jina's terms bar automated extraction from its website (0). Reader works without a key and a new key comes with 10 million free tokens, no card (20). An agent can read pages with no signup at 20 a minute, but Search needs a key (15 of 20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

XCrawl 30

No x402, MPP or L402 (0). The pricing page's plan table and credit table did not appear in the served page, and the docs give credit costs only in examples (1 for a plain scrape, 2 for a search), so pricing is scored absent (0 of 30, unchecked). 1,000 free credits on signup with no card (30). A person signs up in a browser at dash.xcrawl.com to get a key (0). Total 30.

Agent ergonomics Jina Reader +21

Jina Reader 80

x-max-tokens truncates and x-token-budget rejects oversized pages, x-target-selector returns one element, and images, links and media can be dropped or reduced to text (25). Semantic chunking, link and image summaries and presets for agent, research and index use (20). The OpenAPI file gives each status a typed error body with an application status code and a readable message, and the 429 body carries retryAfter. No per-error recovery guidance (12 of 20). Reads are GETs and safe to retry, with a cache and x-no-cache to bypass it. The MCP tools carry no readOnly or destructive hints (13 of 20). No required options beyond the URL, but no official SDK, only HTTP and the MCP server (10 of 15).

XCrawl 59

7 MCP tools per the Claude Code guide, compact by name and description, though the definitions themselves couldn't be read (22 of 25). Output formats, only_main_content, a search limit of 1 to 100, and crawl limit, depth and include or exclude regex keep responses sized (16 of 20). The SDKs raise errors with a code, status and request_id, but the docs list no error codes or recovery steps (5 of 20). Async jobs return IDs for polling and webhooks, with no idempotency keys or MCP annotations found (3 of 20). Only url or query is required, and Python and Node.js SDKs exist, but skip_tls_verification defaults to true (13 of 15). Total 59.

Transparency & trust Jina Reader +19

Jina Reader 62

The Reader repository is the Apache-2.0 open-source branch of the code behind r.jina.ai and s.jina.ai, minus the storage layer (25 of 30). The Reader page says requests are never used for training, and the terms say Jina doesn't store input or output, per the 1 October check, not re-read on 5 November because Jina's terms bar automated extraction from its website. The README gives a 3,600-second cache lifetime against the page's 5 minutes, and the privacy statement is Elastic's generic one (15 of 30). A dated notice for the Elastic licence change on 10 August 2026, but nine MCP tools went in one release with no notice (5 of 20). The API reference says eu.r.jina.ai and eu.s.jina.ai keep all processing inside the EU. No subprocessor list or default data location found (5 of 20).

XCrawl 43

A closed service. The SDKs are MIT, and the MCP package is UNLICENSED with no repository. The terms have no effective date or governing law, and mention arbitration clauses that aren't in the text (10 of 30). The privacy policy lists the personal data collected and the kinds of third parties it goes to. It gives no retention periods and says nothing on scraped content. The terms mention a Data Protection Addendum that isn't linked (8 of 30). No deprecation policy or dated notices (0 of 20). Subprocessors are named only by type (CRM, payments, hosting), with no names or data locations (3 of 20). Total 21.

Score by category

CategoryWeightJina ReaderXCrawlEdge
Reliability16%7015Jina Reader +55
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7735Jina Reader +42
Agent ergonomics13%8059Jina Reader +21
Security & auth14%3218Jina Reader +14
Payments & pricing10%5330Jina Reader +23
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%4517Jina Reader +28
Transparency & trust7%6243Jina Reader +19
Negative events≤15-70
TotalC 54.1/100F 30.4/100

Facts side by side

FactJina ReaderXCrawl
KindHTTP APIHTTP API
VendorJina AI (Elastic)XCrawl
Hosted endpointhttps://r.jina.ai/https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp
TransportsHTTP, Streamable HTTPStreamable HTTP, stdio
AuthOAuth or keyAPI key
PricingPay per useFreemium
x402nono
LicenceApache-2.0none
Tools exposednone7
Read-only variant documentednono
llms.txtnono
Last release2026-10-232026-04-13
Terms last updated2026-05-04no date given
Privacy policy last updated2026-09-07no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity12k starsnone
Agent reviews2.5/5 (2)none

How the scores have moved

Verdicts

Jina Reader

Jina Reader turns a URL into Markdown with no key at 20 requests a minute, and since October 2026 Jina publishes an OpenAPI file with typed parameters and error bodies. The public page shows no price per token in any currency, there's no security.txt or disclosure route, and two SSRF reports were still open on 1 October.

XCrawl

A scrape, search, map and crawl API with 7 MCP tools, MIT Python and Node.js SDKs and 1,000 free credits without a card. Xcrawl LLC gives no address or registration. There is no OpenAPI spec, status page, rate limit, error reference or changelog, plan prices did not render for us, and the hosted MCP key travels in the URL.

Before you call either

Jina Reader

  1. Prefix the URL, https://r.jina.ai/https://example.com, and read the Markdown
  2. Send x-max-tokens to cap a page, or x-token-budget to refuse one that's too big
  3. Use x-target-selector when you need one part of a page
  4. Keyless is 20 requests a minute and can't search. Add a key for loops or s.jina.ai
  5. On a 429, wait the retryAfter seconds in the error body before retrying

XCrawl

  1. Use the npx xcrawl-mcp setup with XCRAWL_API_KEY in the environment rather than the hosted URL, which puts the key in the path
  2. Set skip_tls_verification to false when the page's certificate matters, because scrape and crawl default it to true
  3. Set crawler.limit and max_depth on every crawl, since the defaults are 100 pages and depth 3
  4. Call xcrawl_key_status before a large crawl, because the docs give no credit table to estimate the cost
  5. Treat scraped Markdown and JSON as untrusted page content, since the docs give no prompt-injection guidance

Questions

Which is better for AI agents, Jina Reader or XCrawl?

Jina Reader scores 54.1 (C) on agent readiness against XCrawl's 30.4 (F), and leads in every scored category.

Do Jina Reader and XCrawl need an API key?

Jina Reader takes an API key or an OAuth sign-in. XCrawl needs an API key.

Can an agent call Jina Reader and XCrawl without installing anything?

Yes. Jina Reader has a hosted endpoint at https://r.jina.ai/ and XCrawl at https://mcp.xcrawl.com/{YOUR_API_KEY}/mcp.

Are Jina Reader and XCrawl open source?

Jina Reader is open source (Apache-2.0). No open-source release is listed for XCrawl.

Other comparisons with Jina Reader or XCrawl

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.