Crawlee vs Lookup.im API

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

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

Crawlee vs Lookup.im API: common questions

Which is more reliable, Crawlee or Lookup.im API?

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

Which is faster, Crawlee or Lookup.im API?

Crawlee has the lower median latency in our checks — Crawlee responds in 480 ms versus Lookup.im API at 1158 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 Lookup.im API need an API key?

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

Can I call Crawlee and Lookup.im API from the browser?

Neither sends browser-friendly CORS headers reliably, so call Crawlee and Lookup.im API 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 Lookup.im API free for commercial use?

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