Bump.sh

You can now describe workflows for your MCP servers using the Arazzo specification. 🚀 The Bump.sh MCP platform now supports 2 specifications: - Arazzo, the specification pushed by the OpenAPI Initiative - Our own lightweight specification named Flower 🌸 Learn more about it in our last product update 👉 https://lnkd.in/eXGbVGns

With our last search update, your API users are never left without answers: you can now search across your entire API hub without leaving your active API doc. More about it in our last product update 👉 https://lnkd.in/eQd9qV5D

I'm proud to announce the launch of our MCP platform in closed beta 🚀 Make your APIs AI-ready with deterministic, production-ready MCP servers, based on your API workflows and tailored to real-world business use cases. AI tools no longer guess what they have to do (and fail): they share their goal, and your MCP server runs workflows you defined. The best part? We've made it as simple as managing your API docs. Learn more about it in our last product update: https://lnkd.in/ePx_ADaq

Redpanda is becoming the go-to streaming platform for Agentic Data Planes. When their team decided to modernise their #API documentation strategy, they migrated from their existing Rapidoc setup to Bump.sh and saw immediate improvements: a 60% reduction in API documentation issue resolution time and a significantly improved user experience for their growing community. Find out how Redpanda transformed its developer portal and the impact this change has made on its internal teams and external developers. https://lnkd.in/eg_4Uxym

Today, we’re releasing our Arazzo Complete Guide 🎁 Arazzo is the specification from the OpenAPI Initiative designed to describe workflows. In many ways, it’s the natural complement to OpenAPI: where OpenAPI describes APIs, Arazzo describes how those API endpoints are used together. Let me be transparent. I believe Arazzo is still far from perfect. There are several aspects of the specification that could be improved, and I’ll share more thoughts about that in a future post. But despite its imperfections, Arazzo is currently the most promising approach we have to describe workflows in a standardized way, especially for processes that go beyond a single API call. This matters even more with the momentum around MCP and AI agents, where orchestrating multiple API interactions in a reliable and deterministic way is becoming essential. I suspect that most Arazzo files won’t be written by humans. They’ll likely be generated by tooling and LLMs. But in my opinion, understanding the model is still important. You need to know what it represents, how workflows are structured, and how the different concepts fit together. A few weeks ago, we published an Arazzo Cheat Sheet to help people get started. This time, we asked Phil Sturgeon to write a complete guide to the specification. The result is a set of 10 detailed guides covering the core structure, workflow components, common patterns, and practical usage. If you're exploring workflow descriptions, API orchestration, or the future of API-driven automation, this should help you get a clear understanding of where Arazzo fits. 👉 You can read the full guide here: https://lnkd.in/duqM-x3j #OpenAPI #apis #arazzo 

We just released our Arazzo Cheat Sheet! And if you spot a mistake in it, we’ll give you 6 months of free access to the product we’re about to launch 👀 If you’re not familiar with it yet, Arazzo is the go-to spec to describe API workflows. The missing piece that nicely complements OpenAPI when things go beyond single endpoints. A few weeks ago, our friends at Jentic shared their own Arazzo Cheat Sheet, which is great. We chose a slightly different approach: instead of trying to be exhaustive, we focused on real-world usage. On one side: - global structure - resource definitions - user inputs and outputs - steps description On the other: - orchestration - runtime expressions mechanism - validation conditions Honestly, we wish we had this pinned above our desks when we started working on workflows support at Bump.sh. Because let’s be honest: Arazzo isn’t always easy to grasp 😀 Of course, even after multiple reviews, there are probably a few mistakes left. If you find one, post it in the comments. 🎁 The first 5 people to report a not-yet-mentioned error will get priority access + 6 months free to what we’re currently building around Arazzo and MCP. Huge kudos to Yoan for the massive work on this, and thanks to Phil and Paul for their great feedback. #Arazzo #OpenAPI #API #MCP 

We are beginning to offer support for some features introduced by OpenAPI 3.2. Learn more about it here 👉 https://lnkd.in/eBdwQyhN

Thanks to the new Markdown rendering version of your API docs, your users can now ask questions about your APIs directly in their favorite AI chatbots and get relevant, token-efficient answers. More about it in our last product update 👉 https://lnkd.in/ewQcuenN

Who has tried to generate an #MCP server directly from their OpenAPI? Raise your hand ✋ Who had it work well? No one? 😅 Indeed, it doesn’t work, except for very small APIs with basic features: agents (like humans) can’t guess the call sequences needed to perform real-world tasks. They have very limited trial-and-error capacities and are unable to efficiently deal with the bloated responses returned by most APIs. In my opinion, Arazzo could (and should) become the basic layer to create powerful wrappers for your APIs, allowing them to become truly AI-ready: sequence orchestration, API call chaining abstraction, response optimization... I've written a deep dive about how this could work and what we're currently building at Bump.sh → Optimized MCP servers automatically generated from your #OpenAPI + #Arazzo files with zero code, zero maintenance. 👉 Read the full story: https://lnkd.in/eXDrw5bW #ai #apis