I want our APIs to ship the workflows, not just the endpoints, because most real jobs take more than a single call and I would rather hand consumers a proven path than make them assemble one from scratch. That means providing Arazzo workflows that describe the multi-step sequences our operations support, and using OpenAPI overlays to layer in the context and adjustments a specific workflow needs without forking the underlying contract. When we leave orchestration as an exercise for the reader, every consumer reinvents the same sequence and gets it subtly wrong. For the business this turns hard integrations into reusable, shared paths that get adopted faster, and it is a gift to agents in particular, which thrive when the workflow is spelled out as a definition they can execute rather than infer.
APIs Provide Orchestration Workflows
Policies
Arazzo Workflows Provided
Require that APIs which chain multiple operations to accomplish real work provide Arazzo workflow definitions describing those sequences. I want the multi-step paths a consumer must follow, the ord...
OpenAPI Overlays Used
Require that consistent, cross-cutting changes to OpenAPI definitions be applied through OpenAPI Overlays rather than by hand-editing each specification. I want shared conventions, added examples, ...
Experiences
Integration
Integrating digital resources and capabilities into other systems using HTTP APIs is commonplace in any enterprise. However, the experience, skills, time, and cost required for successful integrati...
Reusability
Reusability is the experience of finding and applying an existing API instead of building the same capability again. It depends on discovery, consistent design, and clear documentation that make an...
Agent Experience
Agent experience is developer experience for machines. As AI agents become first-class consumers of APIs, the experience they have discovering, understanding, authenticating, and calling an API mat...
