Scrape.do vs Zyte API

Scrape.do

$29 for 250,000 basic credits, and 429s, 502s and most failures aren't billed. Token travels in the query string on the main API.

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.

Scrape.do

1. Start with the default data centre request (1 credit). Add super=true or render=true only after a block, since they cost 10 and 5
2. Pass output=markdown to get LLM-ready text instead of raw HTML
3. Read Scrape.do-Request-Cost from the response headers. Some domains cost 10 to 200 credits whatever you pass
4. Treat a 429 as too many concurrent requests and wait for one to finish
5. Keep URLs with token= out of logs and shared traces

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