Context Voice Logo

We are happy to announce that, as of today, the uberVU API will be called ContextVoice and will live at ContextVoice.com.

For now, apart from the name change, there are no other changes that have been introduced. So you might ask then, why do it?

The reasons are many.

First of all, the uberVU API seems to have taken on a life of its own. Lots of people want to use it for things we never would have imagined. When we tell people what we do, the first question the ask is usually “Do you have an API?”.

Because people want to use it to do very different things than we have originally thought, we’ll have to add things in the API that have no relation the uberVU as a product. What uberVU does right now will, in the future, only be a small part of what ContextVoice will offer. That’s one of the reasons why we felt the API needed to be a product on its own.

Secondly, while uberVU is still in the Private Beta works for the time being, the API is now public and people are willing to pay for it and use it commercially. This subtle difference between where the product and the API is in terms of development and reliability was not apparent from the uberVU site. So it confused a lot of people that wanted to find out about the API and use it within their apps.

For now, you’ll see no change in the API calls made if you’re already using the uberVU API. If you’re thinking of starting to use it, however, we suggest going to the website and start using ContextVoice.

We’ll announce changes made to the API as they happen, making sure it’s not a hassle for you to implement those changes, should that be the case.

As, always, we’re very interested in knowing what you think about this. Shoot your thoughts in the comments, on FriendFeed or Twitter.