Kaggle vs Lookup.im API

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Kaggle vs Lookup.im API: common questions

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

On our scheduled checks, Lookup.im API leads on measured uptime — Kaggle at —% versus Lookup.im API 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 Kaggle and Lookup.im API need an API key?

Both ask you to authenticate — Kaggle uses an API key and Lookup.im API uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

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

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

Are Kaggle and Lookup.im API free for commercial use?

Kaggle 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.