Arazzo

Arazzo is a community-driven, open specification within the OpenAPI Initiative that describes sequences of API calls and the dependencies between them to accomplish a specific outcome. Where OpenAPI documents individual operations, Arazzo captures the workflow that strings those operations together — the order, the inputs, and the outputs that flow from one call to the next. It is a programming-language-agnostic, machine-readable way to say not just what an API can do, but how you actually use it to get something done.

• Workflows, not just endpoints - Expresses multi-step sequences and the dependencies between calls, the layer above a single operation.
• Steps, inputs, and outputs - Each step names the operation it invokes and passes outputs forward as inputs to later steps.
• OpenAPI Initiative standard - Governed alongside OpenAPI under the Linux Foundation, so it references existing OpenAPI descriptions directly.
• Language-agnostic and machine-readable - A portable document any tool, SDK generator, or agent can read and execute.

In real operations, Arazzo turns a provider’s “integration” or “recipe” documentation into a forkable, testable artifact — I have used it to re-express partner integrations and health-record retrieval as executable workflows rather than prose. It is especially load-bearing in the agentic turn: an agent handed an Arazzo workflow gets a reliable, pre-authored path through an API instead of having to infer the correct call sequence on its own, and those workflows index cleanly into APIs.json alongside the rest of an API’s artifacts.