Posted on 07-03-2014
I wanted to stop and reflect for a moment on the open source, distributed API search engine, that 3Scale and API Evangelist developed, in support of the APIs.json discovery format. When we conceived the APIs.json API discovery format, we knew that the project would be dead in the water, if there wasn’t a clear incentive for API providers to generate an APIs.json—helping them get their APIs found.
Until 2014, when you said "search for APIs", it meant going to a website (programmableweb.com), and searching for an API in a curated directory of APIs. In the last couple years, we’ve seen an evolution on this directory search model from Mashape, in the form of a hub or marketplace. Managed directories have their place in the world of API discovery, similar to the web directory realm, but as the number of APIs grow, we are desperately needing to go beyond just directory based API discovery, and like with the web, establish a meaningful search layer—we need a Google of API search.
This is why 3Scale and API Evangelist developed APIs.json, and the first open tooling on top of the API discovery format, we called APIs.io. We do not believe APIs.json + APIs.io is the next Google, but we do feel it will jumpstart the conversation around what is needed when it comes to API discovery. How do we find the best of breed APIs, not just on keyword search in the title and description, or driven from tags? We need a way for API providers to describe their APIs, and supporting building blocks, in a machine readable, distributed way, that can be indexed by many API discovery solutions.
When searching for APIs, we will need to find specific API interfaces, with very specialized terms of service, and pricing. We will need API rating solutions like API Rating Agency baked into our API search algorithms. We need an extensible API discovery format, this is APIs.json. We need an open source search engine, that can be deployed as general search engine, or deployed as a specialized, niche, API search engine serving a specific business sector, like government--this is APIs.io.
APIs.io now has 128 APIs in its index, submitted by 91 maintainers. We are just getting started, defining what is next for both APIs.json, and APIs.io, make sure and get involved early on, and help make your mark on this rapidly expanding world of API discovery. You can add your APIs to APIs.io, fork the open source API search engine code (coming soon) and launch your own API search engine, or provide feedback on the next version of APIs.json, the format that will help discover the valuable API resources everyone will be depending on in the API economy.
Disclosure: 3Scale is an API Evangelist partner.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Showcasing Your API Integrations With Other Platforms
- Increasing The Focus On APIs In Higher Education Is Important
- The New StrongLoop API Server Provides A Look At Future Of API Deployment
- Models For API Driven Startups Built Around Public Data
- Will You Add Me To API Evangelist And How To Spot The Cool Kids
- When I Remix APIs Using Swagger How Do I Deal With Authentication Across Multiple APIs
- It Takes A Team Of Evangelists To Raise An API
- Support For Only Two Creative Commons Licenses In The API Commons
- Machine Readable Terms of Service Didn't Read Applied To APIs Via APIs.json
- API Deployment For Non-Developers Using Zapier, Google Docs, and APISpark
- State of Hypermedia Today @ API Craft In Detroit
- Need A Formal API Standard For Your Government Agency? Fork 18Fs, And Make It Your Own!
- CORS Makes Your API Portable And Remix-able
- Chief Data Officer Needs To Make The Department Of Commerce Developer Portal The Center Of API Economy
- An API Definition As The Truth In The API Contract
- Look At Existing APIs In The Space Before Designing Your Own
- Libraries Hacked: UK Library API, Data And Technology Hacks
- Financial Data Aggregator Yodlee Looking For A Director of Developer Evangelism
- AutoDevBot Open Sources Their API Monitor
- Low Hanging Fruit For API Discovery In The Federal Government
- Looking At 77 Federal Government API Developer Portals And 190 APIs
- Applying APIs.json To API Discovery In The Federal Government
- The Power In API Discovery For APIs.json Will Be In The API URL Type
- Fixing The Machine Readability in API Commons
- Evolving How We Approach The API Lifecycle With APIMatic