Posted on 06-19-2013
I went to Spain at the beginning of the month to speak at API Days. While there I had the pleasure of connecting with the team from Apicultur. If you are not familiar with Apicultur, they are a platform for linguistic APIs, providing resources ranging from word frequency, synonyms and sentiment analysis to word games.
Apicultur is relevant because language APIs WILL be central to evolution of not just mobile, but also the Internet of Things. Also, Apicultur isn't just trying to build the best linguistics API in the world, they are working to assemble a marketplace of the worlds linguistic API resources.
The value of the API resources Apicultur is developing attracted me to them, but then I learned more about their overall business model, and was really hooked. They want you to hang your valuable linguistics API in their marketplace, side by side with the ones they develop. They truly want to build the most valuable marketplace of API driven, language resources from around the world.
The Apicultur team is in San Francisco this weekend for API Days, if you are a complimentary API I recommend you connecting with them. Also if you have a business that could use the resources they offer, I also recommend reaching out. You can ping them @apicultur or feel free to contact me, and I'll hook you up. Or maybe just head down to API Days at Parisoma.
What Apicultur is doing, reflects the next iteration of APIs from an all the APIs directory like ProgrammableWeb, to niche marketplaces of valuable resources developers will be needing to build the next generation of applications.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Top 5 Most Popular Themes On API Evangelist In 2014
- Query Parameter Determining Which Fields Are Queried For API Call
- Now Our Development Environment Is Now Containerized And Scalable Like Our Production Environment
- Guest Post: Let Our Sponsors Blow A Little Smoke Up Your Ass
- API Discovery Continues Its Move Into The IDE With Eclipse Che
- Evolving Beyond Just Resources Towards A More Experience Based API Design
- Another View of The API vs. Data Download Model
- If You Have A Publicly Available Mobile App You Have a Public API
- Reducing The API Stack Down From 830 to 690
- Gathering My Thoughts Around Common Patterns For Base URLs Across Nearly 700 APIs