Jina Reader vs Zyte API

Jina Reader

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

Zyte API

One POST endpoint with an OpenAPI 3 contract picks proxies, browser rendering and extraction per site, bills only successful responses, and sends problem+json errors with Retry-After. Prices vary by target site across five tiers, so cost per request isn't known before the site is assigned one, and no dated API changelog was found.

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

Zyte API

1. Send the API key as the Basic auth username with an empty password to https://api.zyte.com/v1/extract. Set only one of httpResponseBody or browserHtml, or one extraction field
2. Ask for httpResponseBody before browserHtml. Browser requests cost about eight to thirteen times more per tier
3. Retry 429, 503 and 520 after the Retry-After seconds, with backoff. They aren't billed. Don't retry 400, 401, 422 or 451
4. Read statusCode in a 200 response. A target site's 404 comes back as a successful, billed Zyte API response
5. Have the owner set a blocking spending limit on the key you use. A 403 /auth/account-suspended means the limit or the trial month ended