Browse documentation
Get startedIntroductionQuickstart
ConceptsArchitectureCore objectsQuery lifecycle
SpecificationOverviewHTTP bindingMCP bindingA2A bindingSecuritySchema reference
CommunityContributingGovernance
Specification

Specification

Agent Query Protocol · 2026-07-30 initial draft.

Status

This is the initial dated AQP specification. It defines the canonical data model and normative behavior shared by all bindings. JSON Schema 2020-12 files are the authoritative machine-readable definitions.

Conformance language

The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL are interpreted according to BCP 14 when they appear in all capitals.

Protocol requirements

  1. Implementations MUST validate canonical objects against the schema for their declared protocol version.
  2. A query MUST identify exactly one subject, declare one response format, and expire.
  3. A respondent MUST apply local consent, privacy, authorization, and destination policy before submission.
  4. A requester's consent preference MUST NOT override local or user policy.
  5. A collector MUST return a structured receipt and make duplicate response submission idempotent.
  6. Query processing MUST NOT delay or fail the interaction that carried it.
  7. Bindings MUST preserve canonical object semantics and document any additional authorization requirements.

Versioning

AQP versions use ISO calendar dates. Implementations declare one exact version per object. A newer implementation may support multiple dated versions, but must not silently reinterpret an object under a different version. Breaking schema or semantic changes require a new date.

Bindings