AIP Documentation
Agent Interoperability Protocol (AIP) gives applications, agents, tools, and workflow systems one governed way to discover capabilities, start work, follow its lifecycle, request human approval, and prove what happened.
This documentation is organized around what a reader needs to accomplish. The normative protocol specification defines interoperable wire behavior.
Choose Your Path
| Goal | Start here |
|---|---|
| Understand what AIP solves | What AIP Is |
| Install the binaries or build from source | Installation |
| Run a local daemon and make a real call | Quickstart |
| Understand the request lifecycle | How AIP Works |
| Decide what a capability may do | Capabilities and Contracts |
| Track long-running work | Actions and Sessions |
| Model users, tenants, and credentials safely | Identity and Trust |
| Add human control to sensitive work | Approvals and Policy |
| Plan, commit, and compensate mutations | Transactions and Compensation |
| Coordinate multiple agents | Delegation |
| Choose between native AIP, a profile, and a connector | Profiles, Transports, and Connectors |
| Send native protocol messages | Use Native AIP |
| Embed AIP in a Rust application | Use the Rust SDK |
| Use AIP from an MCP client | Use AIP through MCP |
| Use AIP from an A2A client | Use AIP through A2A |
| Integrate a product or service | Build a Connector |
| Migrate a connector to the frozen SDK | Upgrade a Connector |
Deploy and operate aipd |
Production Deployment |
| Diagnose and recover work | Observe and Recover |
| Respond to operational incidents | Operator Runbooks |
Configure aipd |
Configuration |
| Configure deployment environment | Environment Variables |
| Look up endpoints, transports, or commands | HTTP API, Transport Bindings, and CLI |
| Deploy a maintained product connector | Connector Index |
| Interpret protocol and transport failures | Errors |
| Qualify an implementation or deployment | Conformance |
| Check what the current Rust release proves | Implementation Status |
| Look up protocol terminology | Glossary |
| Implement the protocol | AIP 1.0 Specification |
Documentation Sets
Learn and build
The getting-started, concepts, and guides sections explain AIP in practical terms. They answer why a feature exists, when to use it, and what a correct workflow looks like.
The complete site reading order is maintained in Documentation Navigation.
Operate
The deployment, recovery, HTTP, CLI, error, and conformance documents are for platform engineers and operators. They distinguish local development from a production trust boundary and identify the evidence needed before a deployment can be called qualified.
Implement
The AIP 1.0 Specification is normative. The JSON Schemas page defines the machine-readable contract and its implementation-owned export process. The specification and schemas take precedence over examples and explanatory guides.
Architecture and evidence
Architecture ownership is indexed under Architecture. Product qualification evidence is indexed under Connectors and Testing.
Source-of-Truth Order
When documents appear to disagree, use this order:
- The versioned normative specification.
- The versioned JSON Schemas and conformance fixtures.
- The Rust semantic model and validation rules.
- Compatibility-profile specifications.
- User guides and examples.
- Architecture decisions, implementation notes, and examples.
Please report a mismatch as a documentation or conformance defect. An implementation must not silently invent wire behavior that is absent from the specification.