shipapis
StarSubmit an APISubmit API

Lookup.im API vs Wikipedia REST

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

APILookup.im APIHEALTHY84Wikipedia RESTHEALTHY99
Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms115898
P95 · ms3581961
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedCC BY-SA 4.0
Free tierFree tier — API key requiredUnlimited within etiquette
Rate limitUnpublished200/sec global courtesy cap
In directory since2026-07-052026-05-09
operationalpartialdownno data

Lookup.im API vs Wikipedia REST: common questions

Which is more reliable, Lookup.im API or Wikipedia REST?

On our scheduled checks, Wikipedia REST leads on measured uptime — Lookup.im API at 99.02% versus Wikipedia REST at 100% 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, Lookup.im API or Wikipedia REST?

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

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

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

Only Wikipedia REST 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 Lookup.im API and Wikipedia REST free for commercial use?

Lookup.im API has unclear commercial terms, and Wikipedia REST allows commercial use on its free tier. 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.