I have been playing around with several iterations of what is next for the APIs.io search engine. I have a v2.0 of the search engine and supporting APIs.json index almost reading to replace the current live v1.0. It is all an experiment and work in progress when it comes to API discovery, but a mix of prototypes that eventually I will work to harden based upon usage and interest. Steve and I feel pretty confident that there is a huge need for a public API search engine, and working to fill that need with APIs, but a big part of the need for an API search will depend on what is available locally and on-premise for enterprises to use without any strings attached.

API Evangelist's publication is a resource for developers, architects, and technology leaders seeking to understand the importance of APIs in modern software development. Through articles, case studies, and industry insights, API Evangelist offers insights into API design best practices, API management strategies, and API-driven business models. Readers can learn about RESTful API principles, GraphQL implementations, and microservices architecture to build scalable and interoperable software systems.

API Evangelist

The post discusses the development and features of the v2.0 of the APIs.io search engine, which is a simple Jekyll static site running on GitHub Pages. It highlights the ability to run the search engine locally, the use of APIs.json indexes, and the concept of federated API search.

Localizing the APIs.io Search Engine