This specification explains what AAP is, what an approval means and how an adapter asks for one. It then describes how the agent waits for the result.
This specification defines version 1 of the Agent Approval Protocol (AAP).
- Overview: what the protocol is for, its design goals and the basic tool call flow.
- Architecture and modes: the agent, adapter and provider, and how synchronous and asynchronous execution differ.
- Identity and authentication: instances, credentials, provisioning and instance management.
- Requests and decisions: what is submitted for approval, the possible outcomes and the lifecycle of a request.
- HTTP API: approval operations, instance management, shared HTTP conventions, errors and retries.
- Synchronous mode: holding a tool call open whilst the adapter polls for a decision.
- Asynchronous mode: delivery configuration, receiver registration, signed webhook notifications and resuming execution.
- Security and conformance: the trust boundaries and the requirements an implementation must meet.
The request and decision model is shared by both modes. The OpenAPI schema defines the objects, field types and HTTP operations. The HTTP API section explains how to use that contract. The mode sections explain how to use it.
Guides, SDK documentation and provider-specific setup belong outside this specification.
When a field or wire format changes, update the OpenAPI schema first and keep the examples aligned with it.
Run make api-lint from the repository root to validate the schema and its examples.