Archive.org vs Lookup.im API

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (rights vary per item)Unverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Archive.org vs Lookup.im API: common questions

Which is more reliable, Archive.org or Lookup.im API?

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

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

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

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

Archive.org 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.