Crawlee vs Currents

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms480586
P95 · ms12931165
AuthnoneapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Crawlee vs Currents: common questions

Which is more reliable, Crawlee or Currents?

Both are neck-and-neck — Crawlee and Currents each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Crawlee or Currents?

Crawlee has the lower median latency in our checks — Crawlee responds in 480 ms versus Currents at 586 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Crawlee and Currents need an API key?

Crawlee needs no key, while Currents requires a free API key. If you want to start calling without signup, reach for Crawlee first.

Can I call Crawlee and Currents from the browser?

Neither sends browser-friendly CORS headers reliably, so call Crawlee and Currents from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Crawlee and Currents free for commercial use?

Crawlee has unclear commercial terms, and Currents 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.