Jina Reader vs Scrapeless

Jina Reader

One URL prefix, no key needed, Markdown back. No price per token in any currency on the public page.

Scrapeless

Hosted streamable HTTP MCP at api.scrapeless.com/mcp with header auth, plus a stdio package, both in the official MCP registry. llms.txt quotes Deep SerpApi at $0.1 per 1,000 while the plan data charges $1 per 1,000 for Google Search.

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. Send x-no-cache: true when a page may have changed or a blocked response got cached

Scrapeless

1. Use scrape_markdown for reading pages and save the browser_* tools for clicks and logins, since browser time bills by the hour
2. Call browser_close when done so the session and its billing stop
3. Set limit on crawl_start. Unset, it defaults to 10,000 pages
4. Crawls are asynchronous. Call crawl_start, then poll crawl_result with the returned id
5. Set SCRAPELESS_API_KEY for the stdio server. Older guides use SCRAPELESS_KEY, which still works as a fallback