Open-source project shortlisting

Access and scope

Set CRAWLORA_API_KEY to your Crawlora key. Prefer the listed Crawlora MCP tools when connected; otherwise use the bundled scripts/crawlora.sh, which sends x-api-key to https://api.crawlora.net/api/v1. Read reference/endpoints.md for exact methods and parameters. Check application code as well as HTTP status; payloads are inside data. Stop on authentication errors, back off on 429, and retry a transient upstream failure once. Bound calls/pages by the requested scope and credit budget. Retain source IDs, URLs, source dates, and observation/crawl times separately.

Create a requirements-based shortlist of public projects for a specific workflow. Establish runtime/platform, must-have features, deployment constraints, maturity needs, and license requirements. Use supplied candidates first and distinguish hard requirements from preferences before choosing a comparison rubric.

Discover projects and verify their advertised capabilities