A location based product, for example, would aim to pull in information like checkins from Foursquare, reviews from Lonely Planet, concerts from LastFM and social connections from Facebook, and display all that along one place’s description. To do that, one would need to identify this particular place in all the APIs – identify the place’s ‘doppelgangers’, if you will. Uberblic does exactly that, mapping doppelgangers across APIs, as a web service. It’s like a dictionary for IDs, the Rosetta Stone of APIs. And geolocation is just the beginning.

Uberblic’s doppelganger engine links data across a variety of data APIs. By matching equivalent records, the engine connects an entity graph that spans APIs and data services. This entity graph provides rich contextual data for product developers, and Uberblic’s APIs serve as a switchboard and broker between data sources.

How does it work? Here’s an example:
1. Query the Uberblic Doppelganger API with a Facebook Places ID.
2. You’ll get back matching IDs of that place from a set of both free and premium Web APIs, like Foursquare, LastFM, and Lonely Planet.
3. Use these IDs to query the data provider’s API directly and pull the data you need into your product.
4. That’s it. Simple.

Since Uberblic integrates and maps a large set of APIs, the service can even recommend APIs that would plug nicely into the ones you already use within your product. Sign up for an API key at http://uberblic.com, and read the API documentation to see how things work.