jevcrawl vs ScrapeGraphAI

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.

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.

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

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