Is the Arazzo Engine the missing piece in agentic workflows?
Agentic systems do real work only when they can call the right tools, in the right order, with the right credentials. The Arazzo Specification standardizes how to describe multi-step API workflows so both humans and software can execute them deterministically. It sits alongside OpenAPI and the Overlay Specification inside the OpenAPI Initiative under the Linux Foundation.
In this AMA, we discuss how Arazzo Engine (Runner + Generator) turns Arazzo documents into reliable workflows that agents can execute. We will cover real examples, what Arazzo adds beyond plain OpenAPI, how Overlays fit into your pipeline, and where the spec is headed. Expect measured claims, working demos, and clear takeaways you can apply to your stack. For context on Arazzo’s goals and structure, see the spec and deep-dive resources.
What you’ll learn
Why Arazzo exists and how it complements OpenAPI for multi-call workflows.
How agent runtimes benefit from standards: fewer brittle prompts, more deterministic tool-calling.
Where Overlays help in real pipelines (persona variants, environment diffs, documentation views).
Live look at Arazzo Engine: running a workflow, single-operation execution, and env mapping for auth.
Adoption playbook: how to pilot Arazzo in an existing service, test it, and socialize it with your team.
Who should attend
Engineers and architects designing APIs and agentic workflows
Platform teams maintaining tooling, credentials, and auditability
DevRel and Documentation teams improving workflow-level DX
Speaker
Vladimír Gorej is a Prague-based software engineer and open-source contributor. Former Principal Software Engineer at Apiary and Technical Team Lead at Oracle. GitHub Star and co-founder of SpecLynx, a toolkit focused on OpenAPI authoring and management. He has written and spoken extensively about OpenAPI tooling and DX.
Host: Jentic is building the integration layer that makes agents dependable at scale. This session references open standards from the OpenAPI Initiative, including Arazzo.
Why Arazzo now
OpenAPI is strong at describing single APIs. Teams also need a standard way to orchestrate sequences across APIs. Arazzo fills that gap with a machine- and human-readable workflow spec in YAML or JSON. This unlocks better documentation, testing, codegen, and more predictable agent execution.