The Google Custom Search .NET library by Google interacts with the search and customization functionalities of the API. It contains guides to setup with authentication and authorization, simple API example, web applications, and service accounts. Besides this .NET library can access custom search, additional APIs can be also supported with their respective documentation. A complete list: https://developers.google.com/api-client-library/dotnet/apis/
During the past four months we've seen not one but two well known real-time search engines disappear. First there was OneRiot, which in October 2010 decided to focus on advertising. More recently, Collecta closed it's real-time search engine and API to focus on alternative real-time products. Digging further into real-time search offerings you will also discover that crowdeye has also decided to pull its real-time search engine. This now appears to leave Topsy, and of course Google as the main players focusing on building a real-time search destination. Does this trend signal the end for all real-time search engines or just that their focus has been wrong?
What makes a trip to a restaurant a great experience is not just the fact that they serve delicious food and good wine, but it has a lot to do with the atmosphere and overall 'vibe' of the place. Of course, a 'good vibe' means different things to different people (some like it chilled and some like it loud and bustling), so imagine how cool it would be to be able to browse through dining options based on the exact atmosphere you're looking for. That's what Hoppit is all about; finding restaurants by atmosphere. Hoppit's API provides access to this handy functionality.