ScrapeGraphAI vs Zyte API

ScrapeGraphAI

An agent can mint an account and key over x402 or MPP with no signup. Rate limits and plan prices differ between docs pages.

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.

ScrapeGraphAI

1. Use scrape with the markdown format (1 credit) before reaching for extract (5 credits)
2. Read GET https://v2-api.scrapegraphai.com/api/agent/protocols for current packs and prices before paying over x402
3. MCP tool calls stop at 60 seconds. Use crawl_start and poll for anything longer
4. Back off 1, 2 then 4 seconds on a 429 rate_limit_exceeded. No Retry-After is sent
5. Use Orthogonal's x402 gateway when you need to pay per call without a key

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