Paid version of Google Translate API now open for business
    
    
    
    
    
By Jeff
      Chin, Product ManagerBack in May, we 
announced
      the deprecation of the free 
Translate API
      v1. Today, we’re introducing a paid version of the Google Translate API for
      businesses and commercial software developers. The Google Translate API provides a
      programmatic interface to access Google’s latest machine translation technology. This API
      supports translations between 50+ languages (more than 2500 language pairs) and is made
      possible by Google’s cloud infrastructure and large scale machine learning algorithms.
The paid version of Translate API removes many of the usage restrictions of
      previous versions and can now be used in commercial products. Translation costs $20 per
      million (M) characters of text translated (or approximately $0.05/page, assuming 500
      words/page). You can sign up online via the 
APIs console for usage up to 50 M
      chars/month. 
Developers who created projects in the API Console and
      started using the 
Translate API
      V2 prior to today will continue to receive a courtesy limit of 100K chars/day until
      December 1, 2011 or until they enable billing for their projects. 
For
      academic users, we will continue to offer free access to the Google Translate Research API
      through our 
University Research
      Program for Google Translate. For website translations, we encourage you to use the
      
Google Website Translator
      gadget which will continue to be free for use on all web sites. In addition, 
Google Translate, 
Translator Toolkit, the mobile
      translate apps for 
iPhone
      and 
Android,
      and translation features within 
Chrome,
      
Gmail,
      etc. will continue to be available to all users at no charge.
Jeff Chin is the Product Manager for Google Translate. Whenever he travels,
      Jeff enjoys learning and trying to speak the local language, and finding good local
      restaurants and food to eat.Posted by Scott Knaster,
      Editor