I'm always learning from the API pioneers, and trying to understand how they are pushing forward the API conversation. I'm neck deep in profiling AWS APIs, as well as Google APIs. One common pattern I'm seeing across both providers is the support for API access in both Visual Studio and Eclipse IDEs. 

Google is helping developers find APIs within both of the leading IDE platforms. They have long had some Eclipse plugins for their API infrastructure, but I recently noticed they also have a pretty robust solution for Visual Studio developers. The Google APIs .NET library is made available in Visual Studio using the NuGet package manager, opening up access to a significant portion of their API stack.

Amazon also provides Eclipse and Visual Studio tooling as part of their AWS toolbox, opening up access to the AWS API catalog to developers in the IDE they are are using to build their applications and craft their system integrations. I don't know how much time you've spent looking through the AWS catalog, but it can be a timesucker- giving me access to APIs in my native environment makes a lot of sense.

I feel like API innovation in the IDE is right there with API integration into our continuous integration workflows and the usage of Github. You shouldn't have to depend on Google to find your APIs; they should be right at your fingertips in your IDE, no matter whether they are for your applications, or for managing your API operations. All your internal and third party APIs should be baked into your development, and continuous integration environments, allowing you to orchestrate exactly the application experience, and life cycle you desire. This is just one of the fronts I'd like to see API discovery evolve in coming years, reaching developers with new APIs and paths during design and development, as well as across continuous integration stages of our work.