Diffbot vs jevcrawl

Diffbot

Extract returns typed JSON for articles, products, discussions and other page types with no selectors to write, under a public OpenAPI 3.1 contract and a free plan that needs no card. The API token travels in the URL query string, tokens carry no scopes, and no security page, certification or security.txt was found.

jevcrawl

Three compact, typed MCP tools return verbatim passages with source URLs, cost and stop reasons, and errors arrive as codes with instructions. The project is three days old and alpha, it depends on TypeSafe's paid Jev API, which is in early access with no free tier found, and it does not block crawls of private or local addresses.

Diffbot

1. Call GET https://api.diffbot.com/v3/analyze?url=<encoded URL>&token=<token> when the page type is unknown. Use /v3/article or /v3/product to force one schema
2. Keep the token out of logs and shared URLs. It sits in the query string, so any proxy or log that records the request URL records the token
3. Stay under 5 calls a minute on Free, 5 a second on Startup and 25 a second on Plus. On 429 wait at least one second and back off
4. Check a 200 response for errorCode. The official client raises ExtractionError when a 200 reports a failed extraction
5. Set useProxy=default only when a site blocks the fetch. A proxied page costs 2 credits against 1
6. Install diffbot from PyPI, not diffbot-python, which stopped at 0.3.0

jevcrawl

1. Phrase goal as one specific question and start with max_pages between 10 and 30
2. Check stats.stopped_because and stats.degraded, and read uncertain before reporting that something is missing
3. Use scrape without a goal when you need a whole page, since it makes no paid Jev call and needs no key
4. Handle {"error": code, "message": ...} results, for example auth_error means TYPESAFE_API_KEY is missing or rejected
5. Pages in stats.needs_js_urls were not read. Tell the user rather than guessing their content