{
  "schemaVersion": "1.0",
  "title": "AIP documentation",
  "description": "Use this documentation to choose an AIP integration path, implement it, operate a deployment, and judge the evidence behind the behavior you depend on. It is written primarily for application developers, with focused paths for connector dev",
  "canonical": "https://getaip.org/docs/",
  "route": "/docs",
  "source": "docs/README.md",
  "protocol": "Agent Interoperability Protocol",
  "protocolVersion": "1.0",
  "section": "Start Here",
  "documentType": "Documentation overview",
  "language": "en",
  "revision": {
    "lastReviewedRevision": "97be86e9efedf07ecf1783b03800f683f107fb04",
    "documentationSourceRevision": "9192fef3695ad294994f2712f6d156241e5e92fb",
    "basis": "frontmatter"
  },
  "downloads": {
    "md": "/docs/download/index.md",
    "txt": "/docs/download/index.txt",
    "json": "/docs/download/index.json",
    "pdf": "/docs/download/index.pdf"
  },
  "content": {
    "format": "text/markdown",
    "markdown": "---\ntitle: AIP documentation\ndescription: Choose the right path to learn, integrate, operate, or evaluate AIP 1.0\nkind: index\naudience: developer\nappliesTo: \"1.x\"\nwritingStandard: \"aip-docs/1.0\"\nlastReviewedRevision: \"97be86e9efedf07ecf1783b03800f683f107fb04\"\n---\n\n# AIP documentation\n\nUse this documentation to choose an AIP integration path, implement it, operate\na deployment, and judge the evidence behind the behavior you depend on. It is\nwritten primarily for application developers, with focused paths for connector\ndevelopers, operators, security reviewers, and protocol implementers.\n\nAIP defines signed envelopes, capability discovery, session and action\nlifecycles, approvals, transactions, delegation, streaming, and audit. Existing\nsystems integrate through compatibility profiles and product connectors rather\nthan changing the AIP semantic core.\n\nThese pages cover AIP 1.0. Implementation material applies to version `1.0.0`\nof the Rust workspace at the source revision recorded in page metadata. The\nimplementation is under active qualification. An implemented feature or a\npassing deterministic test does not by itself qualify a particular deployment\nfor production.\n\n## Choose a starting path\n\n| Goal | Start here | Continue with |\n|---|---|---|\n| Understand the protocol before installing anything | [What AIP is](getting-started/what-is-aip.md) | [How AIP works](getting-started/how-aip-works.md) |\n| Install AIP and make a first local call | [Install AIP](getting-started/installation.md) | [Quickstart](getting-started/quickstart.md) |\n| Integrate an application | [Profiles, transports, and connectors](concepts/profiles-and-connectors.md) | [Use native AIP](guides/use-native-aip.md), [use the Rust SDK](guides/use-rust-sdk.md), [use AIP through MCP](guides/use-aip-through-mcp.md), or [use AIP through A2A](guides/use-aip-through-a2a.md) |\n| Connect an external product or service | [Connector index](connectors/README.md) | [Build a connector](guides/build-a-connector.md) |\n| Deploy and operate AIP | [Production deployment](guides/production-deployment.md) | [Observe and recover](guides/observe-and-recover.md) and [operator runbooks](guides/operator-runbooks.md) |\n| Review trust and safety boundaries | [Identity and trust](concepts/identity-and-trust.md) | [Security model](architecture/security-model.md) |\n| Implement or evaluate the protocol | [AIP 1.0 specification](spec/AIP-1.0.md) | [JSON schemas](spec/schemas.md) and [conformance and qualification](reference/conformance.md) |\n\n## Choose an integration surface\n\n| Surface | Use it when | Canonical guidance |\n|---|---|---|\n| Native AIP | The integration needs the complete AIP message and lifecycle model | [Use native AIP](guides/use-native-aip.md) |\n| Rust SDK | A Rust application needs AIP types and APIs directly | [Use the Rust SDK](guides/use-rust-sdk.md) |\n| MCP profile | An existing MCP client needs an AIP-backed tool surface | [Use AIP through MCP](guides/use-aip-through-mcp.md) |\n| A2A profile | An existing A2A client needs AIP-backed task compatibility | [Use AIP through A2A](guides/use-aip-through-a2a.md) |\n| Product connector | The integration maps an existing product API without adding product code to the protocol core | [Connector index](connectors/README.md) |\n\n## Read status claims correctly\n\n| Claim | What it establishes | Where to verify it |\n|---|---|---|\n| Normative | AIP 1.0 requires the behavior | [AIP 1.0 specification](spec/AIP-1.0.md) and [JSON schemas](spec/schemas.md) |\n| Implemented | The selected source revision contains the behavior | [Implementation status](reference/implementation-status.md) |\n| Conformant | The implementation passed a declared protocol test scope | [Conformance and qualification](reference/conformance.md) |\n| Qualified | An exact artifact passed a declared topology and procedure | [Testing and evidence index](testing/README.md) |\n| Live verified | A bounded behavior was observed against an identified external system | [Live product end-to-end evidence](testing/live-product-e2e.md) |\n\nThese claim levels are not interchangeable. In particular, protocol version,\nsource availability, and deterministic test results do not establish the\nproduction readiness of an unqualified deployment.\n\n## Find exact details\n\nUse the navigation menu to browse by task or subject. Use documentation search\nfor exact routes, capability IDs, configuration names, error codes, connector\nnames, and protocol terms. Filter results by section, document type, surface,\nor source class when the result set is broad.\n\nFor an unfamiliar term, start with the [glossary](reference/glossary.md). For\nan operation or deployment failure, use [errors and retry\ndecisions](reference/errors.md) before retrying state-changing work.\n\nWhen two pages appear to disagree, use this source order:\n\n1. the versioned [AIP specification](spec/AIP-1.0.md);\n2. the versioned [JSON schemas](spec/schemas.md) and applicable\n   [compatibility-profile contracts](spec/compatibility-profiles.md);\n3. conformance fixtures for the selected version;\n4. the selected implementation revision and its validation rules;\n5. task guides and examples.\n\nReport a mismatch through the [documentation contribution\nprocess](../CONTRIBUTING.md) as a documentation or conformance defect. Treat\nwire behavior that the protocol does not define as a defect unless a defined\nextension point permits it.\n\n## Recommended first path\n\nIf AIP is new to you, read [What AIP is](getting-started/what-is-aip.md), then\n[install AIP](getting-started/installation.md), complete the\n[quickstart](getting-started/quickstart.md), and finish with\n[How AIP works](getting-started/how-aip-works.md).\n\n## Related pages\n\n- [AIP 1.0 specification](spec/AIP-1.0.md)\n- [Connector index](connectors/README.md)\n- [Implementation status](reference/implementation-status.md)\n- [Glossary](reference/glossary.md)\n",
    "text": "AIP documentation\n\nUse this documentation to choose an AIP integration path, implement it, operate\na deployment, and judge the evidence behind the behavior you depend on. It is\nwritten primarily for application developers, with focused paths for connector\ndevelopers, operators, security reviewers, and protocol implementers.\n\nAIP defines signed envelopes, capability discovery, session and action\nlifecycles, approvals, transactions, delegation, streaming, and audit. Existing\nsystems integrate through compatibility profiles and product connectors rather\nthan changing the AIP semantic core.\n\nThese pages cover AIP 1.0. Implementation material applies to version 1.0.0\nof the Rust workspace at the source revision recorded in page metadata. The\nimplementation is under active qualification. An implemented feature or a\npassing deterministic test does not by itself qualify a particular deployment\nfor production.\n\nChoose a starting path\n\n| Goal | Start here | Continue with |\n\n| Understand the protocol before installing anything | What AIP is (getting-started/what-is-aip.md) | How AIP works (getting-started/how-aip-works.md) |\n| Install AIP and make a first local call | Install AIP (getting-started/installation.md) | Quickstart (getting-started/quickstart.md) |\n| Integrate an application | Profiles, transports, and connectors (concepts/profiles-and-connectors.md) | Use native AIP (guides/use-native-aip.md), use the Rust SDK (guides/use-rust-sdk.md), use AIP through MCP (guides/use-aip-through-mcp.md), or use AIP through A2A (guides/use-aip-through-a2a.md) |\n| Connect an external product or service | Connector index (connectors/README.md) | Build a connector (guides/build-a-connector.md) |\n| Deploy and operate AIP | Production deployment (guides/production-deployment.md) | Observe and recover (guides/observe-and-recover.md) and operator runbooks (guides/operator-runbooks.md) |\n| Review trust and safety boundaries | Identity and trust (concepts/identity-and-trust.md) | Security model (architecture/security-model.md) |\n| Implement or evaluate the protocol | AIP 1.0 specification (spec/AIP-1.0.md) | JSON schemas (spec/schemas.md) and conformance and qualification (reference/conformance.md) |\n\nChoose an integration surface\n\n| Surface | Use it when | Canonical guidance |\n\n| Native AIP | The integration needs the complete AIP message and lifecycle model | Use native AIP (guides/use-native-aip.md) |\n| Rust SDK | A Rust application needs AIP types and APIs directly | Use the Rust SDK (guides/use-rust-sdk.md) |\n| MCP profile | An existing MCP client needs an AIP-backed tool surface | Use AIP through MCP (guides/use-aip-through-mcp.md) |\n| A2A profile | An existing A2A client needs AIP-backed task compatibility | Use AIP through A2A (guides/use-aip-through-a2a.md) |\n| Product connector | The integration maps an existing product API without adding product code to the protocol core | Connector index (connectors/README.md) |\n\nRead status claims correctly\n\n| Claim | What it establishes | Where to verify it |\n\n| Normative | AIP 1.0 requires the behavior | AIP 1.0 specification (spec/AIP-1.0.md) and JSON schemas (spec/schemas.md) |\n| Implemented | The selected source revision contains the behavior | Implementation status (reference/implementation-status.md) |\n| Conformant | The implementation passed a declared protocol test scope | Conformance and qualification (reference/conformance.md) |\n| Qualified | An exact artifact passed a declared topology and procedure | Testing and evidence index (testing/README.md) |\n| Live verified | A bounded behavior was observed against an identified external system | Live product end-to-end evidence (testing/live-product-e2e.md) |\n\nThese claim levels are not interchangeable. In particular, protocol version,\nsource availability, and deterministic test results do not establish the\nproduction readiness of an unqualified deployment.\n\nFind exact details\n\nUse the navigation menu to browse by task or subject. Use documentation search\nfor exact routes, capability IDs, configuration names, error codes, connector\nnames, and protocol terms. Filter results by section, document type, surface,\nor source class when the result set is broad.\n\nFor an unfamiliar term, start with the glossary (reference/glossary.md). For\nan operation or deployment failure, use errors and retry\ndecisions (reference/errors.md) before retrying state-changing work.\n\nWhen two pages appear to disagree, use this source order:\n1. the versioned AIP specification (spec/AIP-1.0.md);\n2. the versioned JSON schemas (spec/schemas.md) and applicable\n   compatibility-profile contracts (spec/compatibility-profiles.md);\n3. conformance fixtures for the selected version;\n4. the selected implementation revision and its validation rules;\n5. task guides and examples.\n\nReport a mismatch through the documentation contribution\nprocess (../CONTRIBUTING.md) as a documentation or conformance defect. Treat\nwire behavior that the protocol does not define as a defect unless a defined\nextension point permits it.\n\nRecommended first path\n\nIf AIP is new to you, read What AIP is (getting-started/what-is-aip.md), then\ninstall AIP (getting-started/installation.md), complete the\nquickstart (getting-started/quickstart.md), and finish with\nHow AIP works (getting-started/how-aip-works.md).\n\nRelated pages\n• AIP 1.0 specification (spec/AIP-1.0.md)\n• Connector index (connectors/README.md)\n• Implementation status (reference/implementation-status.md)\n• Glossary (reference/glossary.md)\n"
  },
  "integrity": {
    "algorithm": "sha256",
    "sourceDigest": "523af9c612cc37f5e5e7184efd4e3cd41a560b212acee22f1e83f2c194339ea7"
  }
}