BotsArchive vs Crawlee

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

BotsArchive vs Crawlee: common questions

Which is more reliable, BotsArchive or Crawlee?

On our scheduled checks, Crawlee leads on measured uptime — BotsArchive at —% versus Crawlee at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do BotsArchive and Crawlee need an API key?

Neither needs a paid key — BotsArchive is callable with no signup, and Crawlee is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call BotsArchive and Crawlee from the browser?

Only BotsArchive is browser-friendly — it returns CORS headers over HTTPS. Crawlee needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are BotsArchive and Crawlee free for commercial use?

BotsArchive has unclear commercial terms, and Crawlee has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.