Announcing Arazzo Editor: Build, Edit, and Export API Workfl

Announcing Arazzo Editor: Build, Edit, and Export API Workfl

Frank Kilcommins

Frank Kilcommins

Estimated read time: 4 min

Last updated: March 23, 2026

Announcing Arazzo Editor: Build, Edit, and Export API Workflows

When I was co-authoring the Arazzo Specification, the intent was straightforward: give teams a standard way to describe multi-step API workflows, the kind of orchestration logic that exists everywhere but lives nowhere consistently. What we don't solve for within the OpenAPI Initiative project is tooling. Writing Arazzo by hand, in raw YAML or JSON, is not the experience the community deserves.

Arazzo Editor is an authoring tool that fills that gap.

What It Does

Arazzo Editor is a browser-based workflow authoring tool built around form-based editing with a live diagram view. You add steps, configure parameters, define success criteria, and set up failure handling, all through structured forms, without touching YAML unless you want to.

As you build, the diagram updates in real-time. Add a step and it appears. Define an onSuccess path and the connection appears. The diagram isn't a separate view — it's a continuous reflection of what you're building.

For situations where forms aren't the right tool — bulk edits, copying step patterns, or just preferring to work directly in YAML or JSON — the code editor is there. Changes sync back to the form immediately. It's bidirectional and deterministic.

Available for free: jentic.com/arazzo-editor

Building a Workflow

Start by defining workflow inputs — whatever data your workflow depends on. Add a step:

  • Select an API operation from your referenced OpenAPI specs
  • Configure parameters using runtime expressions like $inputs.customerId
  • Set success criteria (HTTP Status Code 200, expected response fields)
  • Define failure handling — retry with backoff, max attempts, then route to an error step if exhausted

The diagram updates as you work. The retry loop is shown visually. The failure path is traceable. You're not reconstructing execution flow in your head — it's in front of you.

Evolving existing workflows follows the same pattern. Open a local file or remote URL, the form populates, and you're editing from a complete picture rather than scrolling through hundreds of lines of YAML looking for the right reference.

The Human-AI Bridge

Our CTO, Michael Cordner put it well when we were building this: "Agents will increasingly be the ones building these workflows, but humans still need to review, approve, and understand what's actually being executed."

That's the problem our editor, especially with its document export features, solves. Arazzo Editor exports workflows as markdown or HTML, readable documentation that describes what a workflow does, in plain language, without requiring the reviewer to parse YAML. If an AI agent generates or modifies a workflow, the export is how a human audits it. You shouldn't need to read YAML to understand what your AI is doing.

This felt important enough to build explicitly. It's not a nice-to-have.

Where This Fits

  • Arazzo UI: Visualisation and sharing. Understand existing workflows without editing.
  • Arazzo Editor: Authoring and evolution. Build and modify workflows with form-based editing and live diagrams. This is where workflows are created and maintained.
  • Jentic Platform: Production capability discovery, execution and governance. Runtime agent capability orchestration, policy enforcement, multi-environment configuration, and operational observability.

Start with Arazzo UI to understand, then use Arazzo Editor to build. Move to Jentic Platform when workflows become production-critical infrastructure.

Tooling Is How a Spec Grows Up

A specification is only as strong as its tooling ecosystem. OpenAPI (a.k.a. Swagger) didn't achieve its reach through the quality of the document alone — it reached developers through Swagger UI, Stoplight, code generators, linters, and every tool that made it tangible and approachable. Arazzo is becoming much more accessible as tooling becomes available.

Many are adopting Arazzo as the go-to mechanism to codify use-case orientated workflows towards universal agents, and we're happy to contribute the tooling to make this a reality for everyone. AI agents should not re-invent known workflows, they should execute them!

Predefined workflows like "complete customer onboarding," "process payment with fraud detection" save tokens, protect context, and ensure consistent orchestration.

The emergence of editors, visualisers, and validators matters beyond convenience. Tooling is where spec design decisions get stress-tested against real usage. It's where edge cases surface, where the gap between what was intended and what was written becomes visible. As a co-author, there's no better feedback loop than watching people actually build with the spec — and nothing accelerates that like removing the barrier of raw YAML authoring.

Making Arazzo accessible to practitioners who aren't spending their days in a text editor is how the specification develops further. More people building means more workflows, more patterns, more real-world pressure on the spec to cover what matters. That's how standards evolve well.

Open Standards, No Lock-In

Arazzo Editor is free and built on full Arazzo 1.0.1 specification compliance. Export YAML or JSON with confidence that it's a valid Arazzo document that will run on any compliant orchestrator.

Try It

The editor runs entirely in your browser with no server-side processing — no data leaves your machine. Load local files or reference remote Arazzo documents via URL.

jentic.com/arazzo-editor