An open, versioned contract for agentic workflows: what agents do, what they may do, and what they leave behind.
MCP connects agents to tools. A2A connects agents to agents. AWP defines how agents work.
Website · Specification · Validator · Editor · Viewer · Discussions
Agents no longer only answer questions. They open pull requests, change tickets, send messages and deploy software. Whoever runs them has to answer the same questions every time:
- Which agents take part, with which models and which tools?
- In which order do the steps run, and what does each step hand on?
- Which actions are allowed, which need a human approval, and who approves?
- How much may a run cost, how long may it take, which data may it touch?
- What exactly happened in a run, and can it be reproduced?
In most systems the answers are spread over prompts, configuration files, code and the settings of a platform. Nobody can review them in one place, compare two versions, or move a workflow to another runtime without rewriting it.
HTTP APIs had the same problem until OpenAPI turned them into a document that people can review and tools can read. Validators, viewers, code generators, mock servers and contract tests followed from that one decision. AWP takes the same approach for agentic workflows.
A workflow is a manifest: one YAML (or JSON) document that declares agents, tools, steps, triggers, inputs, budgets, permissions, approvals and the audit trail.
- Declarative. The manifest says what may happen; the runtime enforces it before every model call and every action, and denies by default.
- Versioned. Every manifest has a name, a semantic version and a digest over its canonical form. A change is a new version that can be reviewed as a diff, approved and rolled back.
- Schema first. A JSON Schema defines the structure, the specification the semantics. Tools can rely on both, so a manifest is checked in the editor, in CI and in the runtime with the same rules.
- Fail closed. Unknown fields and fields of profiles a runtime does not support are rejected instead of ignored. A governance rule that is silently dropped is worse than an error.
- Extensible. Implementations add
x-fields for what the core does not cover; useful extensions become core fields through AWP Enhancement Proposals. - Vendor-neutral. AWP is a specification, not a platform. Any runtime may implement it.
Secure tooling needs exactly this: a contract that is readable by people and machines, so that approvals, budgets and tool grants are reviewed before an agent runs, not discovered afterwards.
apiVersion: awp.agenticworkflowprotocol.org/v1alpha1
kind: Workflow
metadata:
name: ticket-triage
version: 1.0.0
owner:
team: support-team
classification: internal
spec:
inputs:
- name: ticket
type: string
required: true
budget:
maxCostUsd: 1.00
maxSteps: 10
mcpServers:
- name: tickets
transport: streamable-http
url: https://tickets.example.com/mcp
agents:
- id: triager
model:
provider: example-provider
name: example-model
tools:
- type: mcp
server: tickets
tools: [get_ticket, add_comment]
workflow:
- id: triage
agent: triager
task: "Read ticket ${{ inputs.ticket }} and propose a priority with a short reason."
permissions:
default: deny
tools:
tickets.get_ticket:
allow: true
tickets.add_comment:
allow: true
approval:
requiredFor: [tickets.add_comment]
approvers:
- role: support-lead
timeout: 4hOpen this manifest in the editor to see it as a step graph with its permissions and approvals.
| Repository | What it is | Package |
|---|---|---|
| agenticworkflowprotocol.org | The specification, JSON Schema, conformance suite, enhancement proposals and the website | – |
| awp-validator | Reference validator: awp validate CLI, Node.js and browser library, online validator |
|
| awp-editor | Viewer and editor as Web Components (<awp-viewer>, <awp-editor>), embeddable like Swagger UI; online editor |
npm install @agenticworkflowprotocol/validator # awp validate, Node.js and browser library
npm install @agenticworkflowprotocol/editor # <awp-viewer> and <awp-editor>- Read the specification and the guide for runtime builders.
- Validate manifests with
@agenticworkflowprotocol/validator, passing exactly the conformance profiles your runtime supports (core,governance,audit,security,mcp,a2a). - Run the conformance suite in your CI against your validator and the manifests you export.
- Enforce budgets, permissions and approvals in your control plane, before every model call and every action.
- Document your extension fields and list your prefix in the extension prefix list.
- Publish a conformance statement and open a pull request to be listed as an implementation.
Show manifests to your users with <awp-viewer> and let them edit with <awp-editor>; both come
from @agenticworkflowprotocol/editor.
- Questions and ideas: GitHub Discussions.
- Bugs and small changes: issues and pull requests in the repository concerned.
- Changes to the specification: an AWP Enhancement Proposal. Experience from a real runtime is the best motivation for a proposal.
- Reviews: every proposal needs reviewers who are not its authors – runtime implementers, security, privacy, MCP and schema reviewers. Offer to review in Discussions.
- How decisions are made: governance. Commits are signed off under the DCO; see contributing.
AWP is a draft. The current API version is v1alpha1; fields and semantics may change before
v1beta1. No implementation claims conformance yet.
AWP provides machine-readable governance primitives that can help organizations implement and enforce their own compliance requirements. Compliance depends on the implementation, organizational controls and applicable regulatory requirements.
Contact: info@agenticworkflowprotocol.org · Security reports: private vulnerability reporting in the repository concerned.