Posted on 08-25-2011
Back in May Googledeprecatedthe free version of the Google Translate API, and pissed off a lot of people along the way. I talked about building your business around Google or any other APIs, and even suggested that Google offer a paid version of the API instead of just shutting down. Today Google introduced a paid version of the Google Translate API that provides a programmatic interface to access Google's machine translation technology, supporting translations in over 50 languages. The paid version of Google Translate API costs $20 per million (M) characters of text translated (or approximately $0.05/page, assuming 500 words/page), and allows up to 50 M chars/month. Google has give a limit of 100K chars / day until 12/1/2011 for developers who had already created projects in the API console that used the Translate API version 2 prior to today. It sounds like Google has decided on a solid business model that will keep the translation API alive, and allow developers to commercially integrate the service into their applications. Google Tranlsate API is now integrated into the Google API Console, and is now one of four Google APIs that have pricing / billing frameworks to support them. Google could have done a better PR job by deprecating the free version of the API at the same time as offering a paid version, but I think Google is trying to figure out how to manage and monetize their APIs just like the rest of us.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Which Building Blocks Should I Use As Part Of My API Support Strategy
- Common Building Blocks of Cloud APIs
- Viewbook Uses Flickr API Design When Designing Their Own
- Expanding An API Designers Horizon Using Apiary
- What Version Of The API Economy Are You Investing In?
- I Am Up To 34 APIs Out Of The Netherlands
- Hello World Product API With Blueprint, RAML And Swagger
- The New Github Developer Program and Integrations Page
- I Have A Valuable API Resource, What Now?
- A Better Understanding Of Government APIs And Their Consumers Before Considering Charging For Use